Workflows are inheriting asset owners as LC managers
In v7.5.1.1, workflows are inheriting; "Include asset owners as lifecycle managers" from master lifecycle.
We are not sure why this is being set at the master lifecycle and not at the community level. If the asset owner is a lifecycle manager they can adjust the lifecycle for their asset. They can remove all policies required in the lifecycle to get their asset approved. This setting is not wanted in all communities. Hence this option should not be inherited rather it should be left to community admin to check this option in community lifecycles. Please let us know if there is any option to remove this to be inherted from the master lifecycle. If not, please advise if this can be raised as an enhancement request. Thanks..Payal. |
One answer
A community lifecycle can always add new rules, but can not remove rules that are inherited from its master lifecycle. If the "Include asset owners as lifecycle managers" is unchecked in the master lifecycle, the community administrator may optionally check or leave this option unchecked in the community lifecycle. I believe this is what you want. If the setting is checked in the master lifecycle, it can not be unchecked at the community or asset level as this would be considered removing an inherited rule.
|
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.