Workflow Issue

17 views
Skip to first unread message

Komal

unread,
Aug 30, 2010, 6:04:59 PM8/30/10
to RedDot CMS Users
Hello All,

I am facing a strange RedDot Workflow Issue.

I have a workflow(Page Change - Content Workflow) where I have three
stages:-

What should Happen in the workflow:-

Stage 1:- Action by User:- 1. Change the contents of the Page. Save(or
Submit to Workflow) the Page
Job Run by the system:- Publish to the Dev Box

Stage 2:- Action by User:- 1. Release the page
Job run by the system:- Publish to the UAT

Stage 3:- Action by User:- 1. Release the page
Job run by the system:- Publish to the Prod


What is Happening:-

First Round of Testing:--

Suppose I change the content of a standard placeholder of a page to
"Test 1"

Stage 1(dev):- The contents are successfully published to the Dev
Server "Test 1"
Stage 2(uat):- The Contents are not changed
Stage 3(prod):- The Contents are successfullky published to the
production server "Test 1"

Second Round of Testing:-

Suppose I change the content of a standard placeholder of a page to
"Test 2"

Stage 1(dev):- The contents are successfully published to the Dev
Server "Test 2"
Stage 2(uat):- The Contents are changed to "Test 1" which is wrong
Stage 3(prod):- The Contents are successfullky published to the
production server "Test 2"

This behaviour is strange because the contents of the uat are
changing(in second round of testing) according to the contents of the
production or dev(in first round) which is wrong

I hope you are able to understand this problem. Please let me know if
you have a solution or atleast some workarounds for this issue.

If you need any other information. Please let me know.

Thanks in Advance!

Regards,
Komal

Komal

unread,
Sep 4, 2010, 2:44:56 PM9/4/10
to RedDot CMS Users
Hi All,

I got the resolution from "Open Text Support Team" for this problem.

The first 2 publishing jobs that go to Dev and UAT should have their
respective project
variants set up to publish "Unreleased pages". Since until you release
the page for the 3rd and final time, CMS considers the page still
unreleased, which is why you most probably do not see the changes
until
it gets fully released and published to production.

Regards,
Komal
Reply all
Reply to author
Forward
0 new messages