Steps to Reproduce
- Open an instance with the Calgary or Dublin release installed.
- Ensure that the following are true:
- the domain support plugin is enabled
- there are at least 2 domains in the instance
- workflows were configured into separate domains using the same user
- workflows are published
- Upgrade from Calgary or Dublin to Eureka Patch 5.
Post upgrade, workflows are now assigned to an unintended domain.
The correct behavior is that all published workflows should be moved into their respective domains. Also, all published workflows should not have the signature "Eureka to Eureka" printed from the fix_wf_domain_ep5 fix job in the localhost logs. This part of the code is only called when the wf"_workflow_version.sys_domain column no longer exists (dropped before EP5).
There is no fix if the issue occurs. The workflows have to be manually reassigned to correct domains.
Note: Instances with domain separation should NOT be upgraded to any pre-EP6 version.
After the upgrade
- All published workflow versions will be associated with their respective domains through the wf_workflow table.
- For checked out workflow versions only (to be consistent starting with Eureka):
- A new entry will be added into the wf_workflow table along with sys_overrides (if these have been checked out into a different domain than their published counterpart).
- The wf_workflow variables references will be copied over to this new wf_workflow entry.
- If there are workflows referenced in these tables, they must be manually resolved against the domain's workflows:
- Catalog Item
- Content Item
- Hardware Catalog
- Order guide
- Product Catalog Item
- Record Producer
- Software Catalog
- Task Action Workflow
The following steps are highly recommended as a best practice before upgrading an instance.
- Publish all working workflows into their respective domains
- Back up your instance
- Clone your production instance onto at Test instance to validate the upgrade process.
Related Problem: PRB609881