Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Any issues importing a workflow from CQ 5.3 in to AEM 5.6..1

Avatar

Level 3

I believe the underlying structure of how workflows are stored have been changed from CQ 5.5.

We are looking to upgrade a CQ 5.3 instance to 5.6.1. An inplace upgrade would automatically upgrade workflows. But we are having issues getting the inplace upgrade to work and so are looking at migrating to AEM 5.6.1 by packaging up content/apps/etc in 5.3 and importing into 5.6.1

Are there any issues with doing this or do we have to create the workflows from scratch?

Is there any documentation on how the workflow model has changed?

Thank you

1 Accepted Solution

Avatar

Correct answer by
Level 10

Should not be issue unless you have customized OOB workflow.   After migration follow [1] to force upgrade so that you do not have to worry much.

[1] 

* From crx explorer create/set the /var/upgrade/status/upgradesExecutor.forceUpgrades property to true.
* Stop and restart the com.day.cq.cq-upgrades-executor bundle from felix console http://<host>:<port>/system/console/bundles/com.day.cq.cq-upgrades-executor
* The log shows upgrades progress
* When done, delete the upgradesExecutor.forceUpgrades property to prevent the upgrades from running every time the executor bundle is activated.

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

Should not be issue unless you have customized OOB workflow.   After migration follow [1] to force upgrade so that you do not have to worry much.

[1] 

* From crx explorer create/set the /var/upgrade/status/upgradesExecutor.forceUpgrades property to true.
* Stop and restart the com.day.cq.cq-upgrades-executor bundle from felix console http://<host>:<port>/system/console/bundles/com.day.cq.cq-upgrades-executor
* The log shows upgrades progress
* When done, delete the upgradesExecutor.forceUpgrades property to prevent the upgrades from running every time the executor bundle is activated.

Avatar

Level 3

Sham HC wrote...

Should not be issue unless you have customized OOB workflow.   After migration follow [1] to force upgrade so that you do not have to worry much.

[1] 

* From crx explorer create/set the /var/upgrade/status/upgradesExecutor.forceUpgrades property to true.
* Stop and restart the com.day.cq.cq-upgrades-executor bundle from felix console http://<host>:<port>/system/console/bundles/com.day.cq.cq-upgrades-executor
* The log shows upgrades progress
* When done, delete the upgradesExecutor.forceUpgrades property to prevent the upgrades from running every time the executor bundle is activated.

 

Thanks, that's useful to know.