Warning

JUser: :_load: Unable to load user with ID: 1005

0
I am setting up orchestration to update Parent Item field from its subtask items.

On a Update transition from subtask item, I am firing event, synchronous, configured as an "After" one.

However it keeps sending the previous value of the field from subtask instead of the new value set during transition.

Any idea?
Responses (3)
  • Accepted Answer

    Thursday, January 09 2014, 12:19 AM - #Permalink
    0
    the value is changed on transition isn't stored in DB until transition is completed. I think you are dealing with a timing issue. I'm not exactly sure on how to tell you how to fix your issue but I'm pretty sure my concept of what is wrong is correct perhaps you knowing your setup and orchestration the idea will help
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 09 2014, 01:34 AM - #Permalink
    0
    Hello again and thank you for you quick answer.

    I have now understood my issue. Since I am actually trying to compute data from all sibling subtasks of the subtasks calling the event, I have created a loop (for each) collecting each subtask items and their data. Here is the issue, as you mentionned, the transition triggering the event has actually not really completed (commit) into db so the very one subtask item calling is returning DB data instead of currrent transition data.

    I managed to work around this issue, by branching in the loop. If the subtask (indexed by the loop) is the current one (same id as the one in the event extension data) then I use the extension data instead of collecting the data from the subtask indexed by the loop.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 09 2014, 01:37 AM - #Permalink
    0
    Great - glad I was able to help
    The reply is currently minimized Show
Your Reply

Recent Tweets