Problem: Different Results With Different Access Role
Good day guys!
I got a problem here when testing a case, it appears when I'm using another operator ID to test the case.
I've already checked running a case with different OperatorID and the result page is different than my operator ID.
This is what I know:
1. I am creating/updating/designing 'that' case with my operator ID (ex:@jimmy.wijaya) and I've already checked in all ruleset.
2. The other Operator ID's Access is "MyApplication:Users" and my Operator ID's Access is "MyApplication:Administrator".
3. I am using clipboard page to reference a grid layout on that Section (Other section works fine though).
4. There's a missing clipboard page between case created by my Access and other's Access. (I've already checked, it didn't related with the grid layout)
5. The data inside clipboard page that being referenced to a grid layout is a mess when using another Access Role
6. I did not using any validation involving Access Role or involving specific OperatorID.
Is there something missing from 'that' case?
Picture 1: A case when creating from my Operator ID (This is the right one)
Good day guys!
I got a problem here when testing a case, it appears when I'm using another operator ID to test the case.
I've already checked running a case with different OperatorID and the result page is different than my operator ID.
This is what I know:
1. I am creating/updating/designing 'that' case with my operator ID (ex:@jimmy.wijaya) and I've already checked in all ruleset.
2. The other Operator ID's Access is "MyApplication:Users" and my Operator ID's Access is "MyApplication:Administrator".
3. I am using clipboard page to reference a grid layout on that Section (Other section works fine though).
4. There's a missing clipboard page between case created by my Access and other's Access. (I've already checked, it didn't related with the grid layout)
5. The data inside clipboard page that being referenced to a grid layout is a mess when using another Access Role
6. I did not using any validation involving Access Role or involving specific OperatorID.
Is there something missing from 'that' case?
Picture 1: A case when creating from my Operator ID (This is the right one)
Picture 2: A case when creating from other Operator ID (with different Access Role)
Picture 3: This is the design prototype.
I trace the process (in the Designer studio as Administrator) and didn't found any problem and it works fine/good, but still this problem occurs when using different Access Role. Please. Do help me resolve this.
Thank you,
Jimmy
Accepted Solution
Pegasystems Inc.
US
Hi,
While I don't have a quick answer for what might be going wrong, I have a couple thoughts on ways you might be able to debug this further:
1. When you traced the process, did you trace the good scenario (your operator) or the bad scenario (the other operator)? If you haven't traced the bad scenario, you can use the Remote Connection option in the tracer to trace against an operator who doesn't have developer portal acces by pointing it at that operator's requestor.
2. You could compare the two access to see if any differences stand out that might be related.
3. You can check to see if the operators have access to different rulesets (configured at the access group level, as opposed to the access role level). Its possible that there are different skins or portal rules that can be accessed via one operator and not the other.
Hope this helps!
-Kurt