correcting category_value data

We kick off a workunit by making an ags call to wfwk.1. We pass category_value of ITS, CMH,WHL or NONE depending on some business rule. If the value is "NONE" it goes into the inbasket of a user that is responsible for correcting the workunit to one of the other 3 values. We can correct the workunit via process admin tool then the user takes an action...but it gets reset back to the "NONE" on the next step.

See screenshots.

Which tables/forms do we need to change to make the work category value permanently stay for the life of the workunit?

Thanks,

Alex-

0712131256598360.doc

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

Alex,
The category value does not persist through User Action. Here is what I mean:
When you change the value in the flow, it is not updated on the database. When User Action node is executed, it stops the thread. The process thread starts back up when action is taken. At this point the value you changed in the flow is lost. In order to persist it, you will have to update the category value in the workunit using the Landmark Transaction node before executing the user action node.

jreese

Alex,
Are you currently using a custom Design Studio inbasket that allows the user to update the value on the Work Unit Variable?

jacob-jellison

Samar,

I know this is the IPA forum...but we are not using IPA yet we are still on 9.0.1.x Process Flow...does the landmark node still apply?

Jreese,

No we are not using a custom design studio inbasket. We correct the workunit's category_value by going to the /bpm/menu.do and changing the record on the "workunit" screen and "workunit queue" screens. I don't see any other place where the old category_valus is stored in the WF tables.

jreese

We update the Category value on the fly by reassigning the value in the flow but never had tried to change it in the menu.do screen after the flow had started. You may want to check to see if the change is being picked up by the flow by testing the oCatValue value before and after you make the change in the menu.do screen. If it doesn't show the change you may need to create a variable to store the change and then assign that variable to the oCatValue before accessing the UserAction node. I access variables through the SQLNode but you should also be able to access it through the DMEQuery node using the LOGAN PDL.

Copyright © 2025 Infor. All rights reserved.