If a decision node is used to select between two fulfillment phase nodes the workflow incorrectly chooses both fulfilment phase nodes. Customers may report this simply as the wrong fulfillment process being used.
This issue was caused inadvertently when adding a feature to revert change requests sorted by account.
This issue is resolved in the following versions
RSA Identity Governance & Lifecycle 7.5.2 P04
RSA Identity Governance & Lifecycle 7.5.0 P08
RSA Identity Governance & Lifecycle 7.2.1 P12
The work around for this issue is to avoid having two downstream fulfilment nodes in the workflow. Change one of the nodes to another node such as a subprocess node and then make the second fulfilment node a child of the subprocess workflow.