When a workflow on a requested item only contains Set Value or Run Script activities, the requested item's active flag stays set as true even when the stage field is 'Complete'. This is due to the 'Set Active Flag' business rule condition failing to be met:

current.stage.changes() && (current.stage=="complete" || current.stage=="Request Cancelled")

The condition does not consider scenarios where a workflow on RITM has no Wait For, Timer, Approval, Catalog Task, Create Task activities. The history of the RITM shows that, when the record is created, the stage initial value is 'Complete', failing to match the business rule condition.

1. Import the attached XML.
2. Order the item 'Completed yet active still true'.
3. Notice the RITM created still has active flag set to true instead of false.
   
   

This issue has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.  After upgrading you will need to enable these business rules:

1. sys_script_3c1faea173002300097f6508caf6a7b9.xml
2. sys_script_8ebfaa6573002300097f6508caf6a7c3.xml

because by default they're active false.

If you are not planning to upgrade to a fixed release, perhaps you may find relief by applying this workaround:

Add the attached business rules which are configured to run after workflows:

• Set Active Flag After Workflows - SetActiveFlagAfterWorkflows_sys_script_3c1faea173002300097f6508caf6a7b9.xml
• Set Closure Fields After Workflows - SetClosureFieldsAfterWorkflows_sys_script_8ebfaa6573002300097f6508caf6a7c3.xml