Approval workflows freeze on migrated artifacts in ELM 7.0.3

ALM IBM Engineering Lifecycle Management
, , , , , , , ,
1

We recently migrated our requirements from an older ELM version to 7.0.3, and now artifacts are getting stuck in approval workflows. The migrated requirements show correct attribute values in the UI, but workflow transitions fail silently. When users attempt to approve, the status doesn’t change and no error appears.

We’ve checked workflow state mappings in the migration configuration, and they appear correct. However, I suspect the migrated artifact attributes might not be properly indexed or the workflow engine isn’t recognizing the state transitions.


Artifact ID: REQ-2847
Current State: Pending Approval
Expected Transition: Approved
Actual Result: No state change

This is blocking our release deployment since we can’t move requirements through the approval process. Has anyone encountered this after migration? Do we need to run bulk update scripts or reindex the requirements module?

2

You’ll need to update the workflow state mappings at the database level. The migration process sometimes creates orphaned state references. I recommend creating a bulk update script that queries all migrated artifacts and resets their workflow state based on the current workflow definition. This forces the workflow engine to re-evaluate each artifact’s position in the approval process. Make sure to back up your database before running any bulk updates, and test on a subset of artifacts first to verify the approach works.

3

I worked on a similar migration last quarter. The issue was that migrated artifact attributes weren’t properly synchronized with the workflow state metadata. We had to run a two-step process: first reindex to update search indices, then execute a bulk state synchronization script. The script identified artifacts with mismatched workflow states and corrected them based on the current workflow configuration. After that, approvals worked normally.

4

The root cause is that migrated artifact attributes retain references to old workflow state identifiers that no longer exist in ELM 7.0.3’s workflow definitions. Here’s the comprehensive solution:

Step 1: Verify Workflow State Mapping Review your migration configuration file to confirm state mappings are correctly defined. Each old state ID should map to a valid new state ID in the target workflow.

Step 2: Create Bulk Update Script Develop a script to query migrated artifacts and update their workflow state references:


// Query migrated artifacts with invalid states
SELECT artifact_id, current_state
FROM requirements
WHERE migration_batch = 'BATCH_2025_09'
  AND workflow_state_valid = false;

Step 3: Reindex Requirements Module After running the bulk update, perform a full reindex through Server Administration → Advanced Maintenance → Reindex Requirements. This ensures the workflow engine recognizes the corrected state values.

Step 4: Clear Workflow Cache Restart the application server or clear the workflow state cache to force the engine to reload all workflow definitions and state mappings.

Step 5: Validate Transitions Test approval workflows on a sample of migrated artifacts to confirm transitions work correctly. Monitor the application logs for any remaining state-related errors.

Additional Considerations:

  • If you have thousands of affected artifacts, run the bulk update in batches to avoid database locks
  • Document which artifacts were corrected for audit purposes
  • Update your migration runbook to include these steps for future migrations

This approach addresses all aspects: migrated artifact attributes are corrected, workflow state mapping is validated, bulk update scripts handle the data correction, and reindexing ensures the system recognizes the changes. Your approval workflows should function normally after completing these steps.

5

This sounds like a reindexing issue. After migrating artifacts, the search indices and workflow state cache often need to be rebuilt. Try running a full reindex on the requirements component through the admin console. Go to the server administration page and look for the reindex requirements option under advanced maintenance tasks.