Workflow Decision Node failing with "no enum constant" ERROR message in RSA Identity Governance & Lifecycle
4 years ago
Originally Published: 2021-12-21
Article Number
000042923
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.2.0, 7.2.1, 7.5.0, 7.5.2
Issue
RSA Identity Governance & Lifecycle Workflow fails at a decision node with an "no enum constant" ERROR message:
  
2021-10-06 13:46:17,271 [Worker_actionq#Normal#jdbc/avdb_111] ERROR com.workpoint.server.script.ScriptEngine  - A script error has occurred. Error occurred in Statement #1 in Script ID 7:WPDS, Script Name = 'SetTrueFalseCompletionCode', Script type = 'Completion Code'. Job ID = 23:WPDS, Process Ref = 'WF_FF_2', Node Name = 'Decision Node'
java.lang.IllegalArgumentException: No enum constant com.aveksa.workflow.ChangeRequestSourceType.
Cause

This is a known issue in the following versions when Oracle Database 19c is used as the datastore:

  • RSA Identity Governance & Lifecycle 7.2.0
  • RSA Identity Governance & Lifecycle 7.2.1
  • RSA Identity Governance & Lifecycle 7.5.0
  • SecurID Governance & Lifecycle 7.5.2

Workflow decision nodes should only branch when there is a value.  For RSA Identity Governance & Lifecycle deployments using Oracle Database 19c, blank values were not being interpreted correctly as null.

Resolution
This issue is resolved in the following versions where the workflow decision node interprets a blank the same as a null.  Note that it is still up to the workflow design to handle the null use case.
  • RSA Identity Governance & Lifecycle 7.2.1 P08
  • RSA Identity Governance & Lifecycle 7.5.0 P05
  • SecurID Governance & Lifecycle 7.5.2 P01

Related Articles

Trending Articles

Don't see what you're looking for?