Skip to main content
S
SteveVinyard1-Visitor
1-Visitor
June 10, 2013
Question

Change Transitions - Cancelling "Under Review"

  • June 10, 2013
  • 5 replies
  • 2362 views
When I setup Change Management, I typically use a change transition to move Resulting Objects on the change task to "Under Review" once the task goes out for Review at the very least once the task is Resolved. This mimics the Promotion Request's "Lock" and protects the data while its out for review and also while the other tasks are being completed (takes a while at times).

5 replies

D
ddemay1-Visitor
1-Visitor
June 10, 2013
Business Rules? Not sure the release were talking here.



I just query the lifecycle history per object and roll backward. Granted it
would be an awesome enhancement request to interact with Oracle in
Transaction POM block to just undo the states and/or at a minimum make it
easier for you, but has to be wide enough of an audience to do that.

Some may want this to record the rollback or movement between states, some
may not. The vehicle has been built for you; just have to command it per se
with some code.



If you do not change state, no reason you cannot invoke the same code (from
a different WF) to place a lock on the object in Oracle as the code in the
promotion workflow already does.








P
pwilliams-313-Aquamarine
13-Aquamarine
June 11, 2013
You could also define the cancel transition for the under review state that mimics the rework transition target state. Then build the proper wf steps to execute the cancel transition.

Thanks,
Patrick Williams

On Jun 10, 2013, at 5:52 PM, "David DeMay" <-<<a style="COLOR:" blue;=" text-decoration:=" underline&quot;=" target="_BLANK" href="mailto:-">>">mailto:->> wrote:

Business Rules? Not sure the release were talking here…

I just query the lifecycle history per object and roll backward. Granted it would be an awesome enhancement request to interact with Oracle in Transaction POM block to just undo the states and/or at a minimum make it easier for you, but has to be wide enough of an audience to do that.
Some may want this to record the rollback or movement between states, some may not. The vehicle has been built for you; just have to command it per se with some code.

If you do not change state, no reason you cannot invoke the same code (from a different WF) to place a lock on the object in Oracle as the code in the promotion workflow already does.



S
SteveVinyard1-VisitorAuthor
1-Visitor
June 11, 2013
Wouldn’t this just put both objects back at whatever state I click for the “cancel” transition though?

[cid:image001.gif@01CE65FE.5A61F1F0]

Steve Vinyard
Senior Solution Architect
P
pwilliams-313-Aquamarine
13-Aquamarine
June 11, 2013
Well that depends on how you implement the cancel transition. You could make the case that Cancel means to put the objects back into an in work state much like you would define for the Refine transition. Or you could say that that Cancel means to put the objects themselves to a Canceled state to record that their Change was not approved but actually canceled.

In short, Yes, the cancel transition would put both objects to the state defined by cancel… After closer analysis of your original question I think I may have spotted your “real” problem. I also faced this problem when analyzing our own change process. Your problem is that you don’t ever know what the state of the objects is before they are move to Under Review by the Review transition. What makes your problem even harder is that you have more than one state under which a user can modify an object. If you have only a single modification state then this greatly simplifies your definitions of the transitions. Basically every transition you define for your “from” states, must also be defined for the Under Review state. See the example below:

[cid:image003.png@01CE662A.03C1B890]


Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image006.jpg@01CE662A.03C1B890]
D
ddemay1-Visitor
1-Visitor
June 11, 2013
- Ideally use a wt.pom.Transaction try/catch block to commit or rollback the steps below



- Add objects to be locked to a WTArrayList



- Create a new wt.fc.collections.RefreshSpec()



- invoke it’s setLock() method (true to lock, false, to unlock)



- CollectionsHelper.manager.refresh(wtarraylistobject, refreshspec_instance);





- Lock should now be applied or removed just like in promotion request.






Terms & ConditionsAccessibility statement