Question
Cognizant
IN
Last activity: 20 Sep 2017 2:56 EDT
Unable to unlock a case in Test environments through SSO login
Hi Team,
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.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
What error you are getting ?
Have you run tracer and found which step it is failing ? Also is there anything interesting in the log files?
Cognizant
IN
Hi Santanu/Prasanth,
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.
Incessant Technologies
GB
Hi Lakshmi,
I hope that you are not trying to submit the case that has already been submitted. If the lock is not relased by workUnlock activity it can be because of any of the following.
1. WorkUnlock will not release the lock immediately if it is a different requestor. It will be released after next system pulse. We can see the same in WorkUnlock activity step 3 java code comments.
if(!blnStatus && differentRequestor)
{
// lock is not released, Lock will be released when after system pulse execution is done that
}
2. Starting from Pega7 locks are also cached. try disabling the cache for the locks. If your test env is a multi node env, perform the change suggested in the below link. https://community.pega.com/support/support-articles/workunlock-activity-does-not-work-multi-node-systems.
3. Also check for the instances of "System-Locks" class and check for your WO lock.
Cognizant
IN
Hi HarshaVardhan,
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.
-
Moe Nomura MOUNIKA KANCHARLAPALLI
Incessant Technologies
GB
I guess the error you are getting " 'Other operator has already taken precedence over you' " is the default behaviour when you try to submit the assignment/case that has already been submitted.
Are you sure that you were able to do this in lower env without any error?
Cognizant
IN
Hi HarshaVardhan,
Thanks for the reply.
The issue here is , I am not getting that error when logged in through SSO.
Pegasystems Inc.
IN
Can you help me the prpc version and pega logs to check any errors logged?
Capgemini
GB
Try to put some logs in SSO activity and see whats happening there.
Try to share pega logs or systemout logs from server.
Regards,
Vishal