SJEaton Posted February 5, 2019 Share Posted February 5, 2019 Hi, I have this error message coming up in a process (TEST HRA Honorarium Process (NEW) BSO selects HoS) when its supposed to move to human task. I've never seen this before. The User in the h/t is System Administrator so I don't know where its getting specified user 'SYS_BPM_MANAGER' from? Any pointers as to what this might be please? I'm sure i've tested this process before and it didn't error? Thanks Sam Link to comment Share on other sites More sharing options...
Victor Posted February 5, 2019 Share Posted February 5, 2019 @SJEaton how is the human task configured? Link to comment Share on other sites More sharing options...
SJEaton Posted February 5, 2019 Author Share Posted February 5, 2019 Link to comment Share on other sites More sharing options...
Victor Posted February 5, 2019 Share Posted February 5, 2019 @SJEaton Assign to: ownerId ...and did the request have an owner when the human tas was created? Because if it did not have an owner at that time, you will get the error... Link to comment Share on other sites More sharing options...
SJEaton Posted February 5, 2019 Author Share Posted February 5, 2019 Yes its assigns a few nodes back prior to the H/T Link to comment Share on other sites More sharing options...
Victor Posted February 5, 2019 Share Posted February 5, 2019 @SJEaton what's a H/T? Link to comment Share on other sites More sharing options...
Victor Posted February 5, 2019 Share Posted February 5, 2019 ..ah. Human Task. Ok, what's the req reference? Link to comment Share on other sites More sharing options...
SJEaton Posted February 5, 2019 Author Share Posted February 5, 2019 SR00091063 Link to comment Share on other sites More sharing options...
Victor Posted February 5, 2019 Share Posted February 5, 2019 @SJEaton - ok, so, the request did indeed have an owner by the time the human task is created but the process does not actually know about this... In your process, you have a "Get Request Details" node which populates values for flowcode variables such as "ownerId". You have this node in the beginning, and because at that time, the request did not have an owner, the "ownerId" variable did not have a value... and still does not. What you would need to do, is to have another "Get Request Details" node before the task is created, to refresh the values for the flowcode variables. Because the request was since then assigned an owner, refreshing the flowcode variables will ensure the value for "ownerId" variable gets populated with the request owner Id. During a process lifetime, the values for flowcode variables do not refresh automatically. If in your process you have tasks or decisions or anything else using flowcode variables, if there is a chance that the value for any of these variables changed since the last "Get Request Details" node, then put another one of these nodes before it to ensure the flowcode has up to date values for its variables. 2 Link to comment Share on other sites More sharing options...
SJEaton Posted February 6, 2019 Author Share Posted February 6, 2019 Hi @Victor Okey doke, thanks Sam Link to comment Share on other sites More sharing options...
.thumb.jpg.d5d3a83b710c9f83c4e4e8cccaba3f81.jpg)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now