Approval workflow lookup table changes not reflected in data model after deployment

PLM Oracle Agile PLM
, , , , , , , ,
1

We’ve updated approval workflow lookup tables to add new routing options for our expanded organizational structure. The changes were made through Admin Console and saved successfully. However, the updated lookup values aren’t appearing in Data Modeler or in workflow definitions.

We added several new department codes to the ‘Approval_Department’ lookup table that’s referenced in our ECO approval workflow. The new entries show correctly in the Admin Console lookup table editor. But when we try to configure workflow routing rules in Data Modeler that use these new department codes:


Error: Invalid lookup value 'DEPT_ROBOTICS' for list 'Approval_Department'
at WorkflowValidator.validateLookup(WorkflowValidator.java:156)

The lookup table definitely contains ‘DEPT_ROBOTICS’ - we can see it in Admin Console. We’ve tried refreshing the Data Modeler view and even restarting Java Client, but the new lookup values still don’t appear in the dropdown when configuring workflow rules. This is blocking our workflow updates for new departments. How do we force the data model to recognize updated lookup table values?

2

Also verify the lookup values are marked as active in the database. Query the lookup table directly:

SELECT name, enabled FROM list_entry WHERE list_id = (SELECT id FROM list WHERE name = 'Approval_Department')

If enabled is 0 for your new entries, they exist but aren’t active for use in workflows.

3

Check if your workflow definition is referencing the correct lookup table name. Sometimes workflows cache the lookup table structure at creation time. If the workflow was created before the lookup table was modified, it might have a stale reference. Try creating a test workflow from scratch and see if the new values appear there. If they do, your existing workflow needs to be regenerated.

4

Lookup table changes require server-side cache refresh. The Admin Console updates the database, but the application server caches lookup tables for performance. Go to Admin Console > Server Settings > Cache Management and click ‘Clear All Caches’. Then restart your Java Client to pick up the refreshed lookup data.

5

I’ve encountered this before. Sometimes the workflow definition cache is separate from the general server cache. After clearing caches in Admin Console, you also need to explicitly refresh the workflow engine. There’s a workflow cache refresh option in the Admin Console under Workflow Management settings. Try that in addition to the general cache clear.

6

I cleared all caches through Admin Console and restarted Java Client multiple times. The new lookup values still don’t show up in Data Modeler’s workflow configuration interface. Could there be a deployment step we’re missing? Do lookup table changes need to be explicitly deployed to the workflow engine?

7

I’ve dealt with this exact issue multiple times when managing complex approval workflows. The problem involves three interconnected areas that must all be addressed:

Lookup Table Deployment: When you modify lookup tables through Admin Console, the changes are written to the database but not automatically propagated to all system components. The deployment process has specific steps:

  1. Make lookup table changes in Admin Console
  2. Export the lookup table definition (Admin Console > Lookup Tables > Export)
  3. Verify the export XML contains your new entries
  4. Re-import the lookup table (Admin Console > Lookup Tables > Import)
  5. This triggers the deployment workflow that notifies all dependent systems

Skipping the export/import cycle means the changes exist in the database but aren’t fully deployed to the workflow engine and data modeler.

Cache Refresh Procedure: Lookup table data is cached at multiple levels in Agile. A complete refresh requires:


// Pseudocode - Cache refresh sequence:
1. Admin Console > Cache Management > Clear All Caches
2. Admin Console > Workflow Management > Refresh Workflow Cache
3. Restart application server (critical step)
4. Clear Java Client cache on all workstations
5. Restart Data Modeler tool specifically

The application server restart is essential - cache clearing alone doesn’t reload lookup table metadata. The workflow engine initializes its lookup table registry during server startup.

Workflow Definition Validation: Existing workflow definitions may have embedded references to the old lookup table structure. After deploying lookup changes and refreshing caches:

  1. Open each affected workflow in Data Modeler
  2. Navigate to the routing rule that uses the lookup table
  3. Remove and re-add the lookup table reference (don’t just edit it)
  4. This forces the workflow to reload the current lookup table schema
  5. Save and deploy the updated workflow definition

The workflow validator checks lookup values against a cached schema. If the workflow was created before your lookup changes, it’s validating against the old schema even after cache refresh.

Additional validation steps:

  • Verify lookup entries are active in the database (enabled = 1)
  • Check that the lookup table has no pending approval status that blocks use
  • Confirm your user role has permission to view all lookup entries
  • Test with a brand new workflow to isolate whether the issue is workflow-specific or system-wide

Query to verify deployment status:

SELECT le.name, le.enabled, le.deployed_date
FROM list_entry le
JOIN list l ON le.list_id = l.id
WHERE l.name = 'Approval_Department'
AND le.name = 'DEPT_ROBOTICS'

If deployed_date is NULL, the entry exists but hasn’t been deployed through the proper workflow.

One final consideration: if you’re using workflow templates or inherited workflows, the parent workflow definition might be overriding your lookup table configuration. Check the workflow inheritance chain to ensure no parent workflow is enforcing an older lookup table schema.

The complete solution requires proper lookup table deployment through export/import, comprehensive cache refresh including server restart, and explicit workflow definition updates to reload the new lookup schema. This ensures consistency across the Admin Console, Data Modeler, and runtime workflow engine.