Using the OotB flow for Role Management with approvals it starts with a reset/synchronize password. That seems to make no sense in role management. What is the reason it is part of the role workflow?
The OOTB workflows are just examples of a basic workflow that would handle a few change items differently. I agree that password resets and syncs are irrelevant to Role changes, so when you create a workflow specifically for Role changes it would be a good idea to remove any extra irrelevant logic from there.
Looks like they have copied it from Delegated approvals with default workflow and shipped with the product.
I am relatively new in RSA/IGL. Re-using part of software, logics etc. in a product is no problem. But to me it feels as though the whole flows section is built out of re-usable blocks. And it is hard to find how they connect/interfere. So you don't know what might happen in another flow when I delete the the password reset/sync in this flow.
Retrieving data ...