Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

New SystemName - pyDefaultAccessGroup error

SA-31010

Summary



The administrator is attempting to clone their system so that this automatically generates the System Name and its 4 associated Requestor Types (APP, BATCH, BROWSER, PORTAL).
However, during this process it fails to build one of the Requestor Types (Portal) and presents an error to the user.

Error Messages



.pyDefaultAccessGroup: cannot be blank.
 

Steps to Reproduce



1. Choose the menu option Designer Studio > System > Settings > System Name.
2. Enter a value in the New Name text box.
3. Click Submit button.
 

Root Cause



During the creation of the Requestor Types this will generate the details based on detail of the current System Name’s equivalent Requestor Type.
Where the pyDefaultAccessGroup is determined based on the pyAccessGroups PropertyList
 
Examining the rule details for the original rule of a successfully cloned Requestor Type this was showing: -
 
<pyaccessgroups_opid REPEATINGTYPE="PageList">
  <rowdata REPEATINGINDEX="1">
    <pyRadioButtonAG>true</pyRadioButtonAG>
    <pxObjClass>Embed-Desktop-ValueList-AccessGroups</pxObjClass>
    <pyLabel>Custom:WebService</pyLabel>
  </rowdata>
</pyaccessgroups_opid>
<pxWarnings REPEATINGTYPE="PageList"/>
<pyAccessGroups REPEATINGTYPE="PropertyList">
  <rowdata REPEATINGINDEX="1"> Custom:WebService</rowdata>
</pyAccessGroups>
 
But for the failing Requestor Type the pyAccessGroup had no value
 
<pyaccessgroups_opid REPEATINGTYPE="PageList">
  <rowdata REPEATINGINDEX="1">
    <pyRadioButtonAG>true</pyRadioButtonAG>
    <pxObjClass>Embed-Desktop-ValueList-AccessGroups</pxObjClass>
    <pyLabel>PRPC:Unauthenticated</pyLabel>
  </rowdata>
</pyaccessgroups_opid>
<pxWarnings REPEATINGTYPE="PageList"/>
<pyAccessGroups REPEATINGTYPE="PropertyList">
  <rowdata REPEATINGINDEX="1"/>
</pyAccessGroups>
 

Resolution



Re-save the affected Requestor Type before using the System Name clone feature to resolve the issue.

 
Suggest Edit

Published December 14, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us