We have surveys implemented across 13+ classes. Each class contains a large number of survey-related rules (Simple Questions, Complex Questions, Questions Pages, etc.), resulting in over 1000+ delegated survey rules in total across multiple delegated ruleset versions.
These rules are currently delegated so business users can maintain survey content. However, the business now wants to prevent direct updates by business users due to concerns about inappropriate or unintended modifications.
What is the recommended approach for removing or restricting delegation at this scale?
Is there a bulk method to remove delegation from a large number of survey rules?
Any guidance or best practices would be appreciated.
I came across this posting and found the topic interesting. My client also uses Pega Questionnaire extensively and we work closely with product manager at Pega. In general, they recommend questionnaire authors using App Studio to author and manage questionnaires from App Studio. This is a recommended approach, but I understand that each client normally has a unique need that all requirements may not be served by App Studio. I wonder, in your project, how and where the questionnaire is authored and what platform version is used today.
Btw i wasn’t aware that we could delegate questionnaire rules; in general i no longer hear often about delegation concept in later platform versions.
The questionnaire is maintained within the delegated rule. Users can open the questionnaire from the user portal menu and make quick updates as needed.
However, this capability isn’t enabled for the entire user group. We are currently on version 25.1.3.