GRC AC 10.1 - Changes to stage task settings impacts stages in other paths

[Former Member]

Hello

We are experiencing an issue where we update the “modify tasks settings” for a supervisor stage in one path and its impacting supervisor stages with the stage config ID in other paths. We tried to change the stage seq no so they are unique to each path but that didn’t resolve the problem. This is not something I’ve experienced previously where task settings are specific to each stage within a path. The screen shots below show how the task settings for supervisor stage in the lock path were updated which impacted the supervisor stage settings in the supervisor stage of the NEW_MOD_EGRC_AUTO path.

Has anyone come across this before? It seems like a bug but we couldn't find any notes related to it.
path

Screen shot showing the selection of all check boxes on the right hand side of the superviso stage in the lock path.

Screen shot showing the supervisor stage of the NEW_MOD_EGRC_AUTO path is impacted by updates to the supervisor stage in the lock path.

[Former Member · Accepted solution]

You can try to create entirely different approval stage for the different path.  When you re-use the stage, the settings get re-used as well (just guessing, but you could test?)

Instead of using "Z_Supervisor" again, just create a new stage for the new path as "Z_Supervisor_(differentiator)"

-Ken