During migration from RSA Identity Governance and Lifecycle 6.9.1x to 7.0.1 the workflow node loses its configuration
Originally Published: 2017-05-02
Article Number
Applies To
RSA Version/Condition: 7.0.1
Issue
- Queries on SQL Select nodes are empty
- Node images are from an old development tool
- Decision Nodes have no configuration under status or process
Using the Browser Development tool (F12) shows the following stack in the Console option:
app.js:1 Uncaught TypeError: Cannot read property 'symbols' of undefined
at ak.onRecordLoaded (app.js:1)
at ak.notify (app.js:1)
at ak.react (app.js:1)
at ak.notify (app.js:1)
at ak.onTick (app.js:1)
at app.js:1
at app.js:1
During migration a new system node was created as a general node but no System Operating Node (SON) is active. Go to Admin > System > Server Nodes tab and a similar configuration should be displayed.
Cause
This issue may happen on either an in place upgrade or when a database is exported from a system on 6.9.1 or earlier to another system on 7.0.0 or later.
Resolution
- Go to Admin > System > Server Nodes.
- Click on Make next SON button next to the new system name.
- Restart the application
$ acm restart
- On restart, the workflow should be upgraded properly and workflow node display configuration options are as expected.
- The aveksaServer.log should contain the following message:
[com.aveksa.server.workflow.WorkflowServiceProvider] Importing workflow archive ACMWorkflow.zip....
- Once the application is restarted, Go to Admin > System > Server Nodes tab.
- Remove the invalid original node by clicking on the Delete button.
Workaround
