Using an Activity Node in Rule Workflows causes intermittent, unexpected behavior such as:
A Subprocess node may not call a sub-workflow that contains an activity node when expected.
The activity node in a sub-workflow may get auto-completed when not expected.
Tasks details assigned by a sub-workflow activity node may show incorrect or irrelevant information related to the task.
There are two problem causes here depending on whether you are using RSA Identity Governance & Lifecycle 7.0.2.x or 7.1.0.x.
RSA Identity Governance & Lifecycle 7.0.2 and 7.1.0
When editing a rule workflow and adding a Subprocess node, if the Only show workflows similar to the current workflow checkbox is unchecked, workflows that should not be used in a rule workflow are available to be chosen. In this case, request workflows with activity nodes were being called by the Subprocess node of the rule workflow. These activity nodes were specific to access requests and made no sense inside a rule workflow causing unpredictable behavior.
RSA Identity Governance & Lifecycle 7.1.0 only
Prior to RSA Identity Governance & Lifecycle 7.1.0, activity nodes were for access request activities only. An enhancement was made to 7.1.0 where activity nodes specific to rules were added to Rule Escalation workflows. There were a couple of issues with these nodes that led to the same unpredictable behavior as seen with request activity nodes.
Fixed in 7.0.2 P10 and 7.1.0 P04.
The fix for both versions is to prevent the ability to add workflows to Subprocess nodes that do not make sense for the RSA Identity Governance & Lifecyle module being used. An additional fix in 7.1.0 P04 is to 'fix' the new activity nodes for rule workflows to use the appropriate context.