Unable to unlock a case in Test environments through SSO login
We are using WorkUnlock activity to unlock a case. Its working in Development environment (both Servlet URL and SSO). but its not working in some test environments when logged in through SSO though its working through Servlet URL. Can anyone please suggest if you come across this issue any time.
Thanks for the reply. Following are the steps causing the issue through SSO Login only.
1.In one session, access a Work object with OperatorId A and aquire the lock.
2.Login with OperatorId B in the other session and unlock the WO followed by submitting the case. Now case gets resolved.
3.Try to submit the case already opened by OperatorId A. I am not getting error saying that 'Other operator has already taken precedence over you' though OperatorId B has already submit the case.
I didn't find anything interesting in Logs.
but in Tracer found that in performFlowAction (OOTB) activity, at step no 5, tools.getDatabase().getLockManager().isLocked() function is returning true as a result lockGone local variable is holding false value instead of true. Is it because of cache issue? we are using PRPC V7.1.9 Please suggest.
Thanks for the reply. As I mentioned in my previous post ,
1.yes. I am able to submit the case that has already been submitted with the below approach.
After logging with second operator, unlocked the WO and submitted the case. I didn't refresh the session of first operator. So the case in first operator session was still in perform mode. That is why the first operator (OperatorId A) was able to take the decision on the case again.
2. The system-pulse was on and after 10 min of time from the case has been submitted by second operator, I tried submitting with first operator.
Eventhough , without any error the first operator is able to submit the case again.
3. Checked the instances of "System-Locks". The instances are getting created and removed properly.