Managing Configuration Data in Pega Rules
Identifying and incorporating configuration data into a rule base is one of the design best practices in PRPC development. PRPC has several out of the box features where users can create and manage configuration data with less effort and minimum steps. Configuration data in PRPC can be classified into three different domains mainly based on the actor who configures. The k ey to good design is identifying the best feature, for a given requirement with the actor in mind. Following table lists down all three actors and supported PRPC features with examples. Actor PRPC Feature Environment Examples Business User Data Table Decision rules that support rule delegation e.g. Map Value Production Limit Approval values for Managers System Administrator