Can default workflows be deleted from the repository?
In v7.5.0.2, is there any option to delete the default worflows from the respository? Can we delete them through RTC Eclipse client as we use to do for custom workflows? This would force community admins to choose only among the custom workflows.
Also what would happen to communities and assets that were already using the default workflows? |
8 answers
Do not delete workflows in RTC. RAM doesn't handle deleted workflows. It will throw exceptions.
In 751 lifecycles have been changed at the community level to be based on master repository level lifecycles, and not based on workflows. The master lifecycle will be based upon workflows. Because of this change a community can only create lifecycles that are based upon master lifecycles that have been made visible (scoped) to that community (by default the masters are visible to all communities). So in 751 to obsolete a workflow you would create a master lifecycle for that workflow, scope it to only one community and it would not be visible to any other community. (We don't have a UI to scope it so that it not visible to any community at all, it is visible to one or more communities only). |
|
Thanks Rich for the clarification. Could you also please clarify if a workflow in 7.5.1 is scoped to one community, can it be scoped to other communities and removed from other communities over time?
Thanks.....Payal. |
|
In v7.5.1, there is the concept of master lifecycles. Is it possible to configure policies, conditions etc. in master lifecycles and then scope the same lifecycles to any communities of our choice?
Also please let us know if there is any documentation available which explains this new feature of master lifecycles. Thanks..Payal. |
|
Notice the difference, we don't say workflow anymore, everything is lifecycle, a lifecycle uses a workflow but assets are based upon lifecycles, not workflows. There can be more than one master lifecycle that use the same workflow.
A master lifecycle can be scoped to any community at any time. When it is scoped it is now available for a community admin to create a community lifecycle that inherits from the master lifecycle. Currently when the master lifecycle's scope is removed from a community and that community already had used that master lifecycle while the community was in scope then that community lifecycle continues to use that master lifecycle. Deleting the master lifecycle is different. When a master lifecycle is deleted then another master lifecycle using the same workflow that is visible to all of the communities that extend the master lifecycle being deleted will be re-mastered to the one of the other master lifecycles (the admin chooses which at the time of deletion). If there is none of the same workflow then it defaults to the implicit master lifecycle as the last choice. This should be all documented in the RAM 7.5.1 help, but the IBM help site is currently down and can't be reached so I can't point it out. Use RAM 7.5.1 help |
|
In a custom workflow, we need to reorder the transitions which appears in drop-down box of the Actions on Asset main page.
Previously we thought that they appear in alphabetical order but it is not so. Even when we added A, B, C, D......etc. as prefix of the transitions, they are not coming in alphabetical order. We created this custom workflow using RTC Eclipse client. Can some one let us know how to reorder the options coming in Actions drop-down. Thanks....Payal. |
|
They are not in any particular order.
|
|
One of our esteemed customer wants the options of Actions drop-down in a particular order for a custom workflow which we created.
Is there any way to reorder them as per our choice while creating the workflow in RTC Eclipse client? |
|
There is no particular order. RAM is not applying any ordering on it. It is a random order. To apply any other order requires code changes.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.