Question
Infosys
IN
Last activity: 31 Oct 2019 8:51 EDT
Unable to see save as and check-out buttons in dev studio
Hi
Unable to see save as and check-out buttons in dev studio. (PRPC version 8.2)
1. Operator ID has the "Allow Rule check out" option selected on the security tab of operator rule.
2. "Use check-out" option in security tab of the rule set rule needs is enabled.
All operators (access role administrator) are facing same issue while accessing application.
Could you please help ?
Thanks,
Josina
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Infosys
IN
Thank you all for the inputs. The issue is resolved now. The application configuration got messed up and we had to revert back to older version to fix the issue.
Pegasystems Inc.
FR
Hello,
Is it something you just having suddenly? No changes, no upgrade?
Have you tried with Out-Of-The-Box users. Maybe you could compare with those ones if it is working.
Infosys
IN
Thanks for the reply. Yes this issue started appearing today. We never faced this before. No Known Changes from our side.
Proximus
BE
Hello,
Any change of Access Group or a change in Access Group roles/grants ?
Regards
Anthony
Infosys
IN
No changes done on accessgroup/role/grants.
Proximus
BE
Someone locked the ruleset your AG is pointing to ?
Infosys
IN
it is not locked
Pegasystems Inc.
US
Hi
Is this specific to a browser ? If you are checking on IE-11, can you check on other browsers like Chrome as well ?
Infosys
IN
I tried IE and chrome. Same issue in both browsers
Pegasystems Inc.
FR
Is it on all environments? Can you compare with another one?
Infosys
IN
It is only in development environment. Compare operator privileges,access role, ruleset security option etc. Do you have any suggestion on what else needs to be checked?
Proximus
BE
If you create a new operator, is it the same?
if you resave/update your operator or import it from another working env, no effect?
Check production level also.
Has requested before, is it the same for any out of the box users ([email protected] if still there)
Something has clearly changed...
in history of dev activities, there's absolutely nothing?
Have you restarted your server, cleared temp dir?
check pr_log & pr4_history_rule to see whether anything not directly visible has been done
Infosys
IN
Thanks for the reply.
[email protected] is getting option to check out. But the operators with administrator role are not having option.
Yes, we restarted server and cleared cache, didn't help
Hexaware
IN
Hi , what was the password did you used to login using [email protected] operator Id. could you please let me know.
Pegasystems Inc.
US
The buttons are shown based on a visibility condition so for understanding better open any rule and see the clipboard values of page RH_1.pyToolBarSettings
Properties
pyBranchOut = false
pySaveAs = true
pyCheckOut = true
THE OOTB WBToolBarDDSettings Final rule sets these values in Step 13 its a JAVA step. Can you please have a look on this JAVA step as that would help in debugging.
Infosys
IN
Thanks for the reply. I checked clipboard page after opening rule.The properties pySaveAs and pyCheckOut are not populated by OOTB activity WBToolBarDDSettings .Attached is the screenshot.
Proximus
BE
When you mention Admin, is it your own admin AG or it's the default PEGA Admin AG?
Since it's for All operators, I guess It's at AG level.
can you send printscreen of the role of your AG?
And/or compare with a working one in other env
Pegasystems Inc.
IN
Hi Josina,
Thanks for posting the query.
Could you please check whether the checkout option is unchecked in ruleset security which might lead to not to show the private checkout or checkout options for those particular rules in that ruleset.
-
Rabi Asirwadh
BPM Company
NL
1. What stated in the pop-up tip, when you click on the lock icon (near Actions button)?
2. Does it happen only for particular rule/ruleset?
3. What's in Actions menu? Is there "Release lock" action?
Accepted Solution
Infosys
IN
Thank you all for the inputs. The issue is resolved now. The application configuration got messed up and we had to revert back to older version to fix the issue.
Pegasystems Inc.
IN
Thank you for the update. We have marked this post as Answered.