How to build for change

Benefits

Business environments change, sometimes suddenly, in response to external change or internal decisions. Process Commander allows you to design and implement applications that respond to change with agility and efficiency.

By recording business practices and policies in rules rather than in code, all Process Commander applications provide a degree of modularity and transparency that can simplify maintenance. For example, line managers can review and comment on a business process presented as a Visio diagram, even without knowing Visio or how to maintain a flow rule.

To go beyond this basic Process Commander benefit, application developers can delegate responsibility for updating selected important parts of each application to business managers. This promotes:

• Agile response to changing business conditions
• Reduced workload for application developers of minor, low risk maintenance items
• Shared responsibility for the success of production applications
• A degree of empowerment of those closest to day-to-day operations
• Experimentation and process innovation by line managers

To build this capability into your application, plan during the requirements and design phases. See Pega Developer Network articles PRKB-25565 Implementation Methodology — Contents and PRKB-25665 Introduction to the Pegasystems Implementation Methodology.

Which rules can managers update?

C-494 KHATV Managers who have the PegaRULES:WorkMgr4 access role (or other roles that include the UpdateLimitedForm privilege) can view and update the leftmost tab of any delegated rule. They can also view and update the History tab.

By design, the leftmost tab of the forms for ten rule types provides access to fields most likely to change over time. Although rules of any type can be delegated, managers are most likely to learn and understand the following types:

• Case match
• Constraints
• Decision table
• Decision tree
• Declare Expression
• Flow
• Flow action
• Service level
• Map value
• When condition

Designing for delegation

To empower managers to change selected rules:

1. Identify during design which rules are useful to delegate to managers to maintain.
2. Choose rule names and property names that are meaningful in the business context.
3. Choose Short Description text carefully for properties that may be referenced in the rules.
4. After initial testing is complete, copy the rules into a RuleSet containing only the delegated rules. This segregates any later changes to them from the rest of the application.
5. Delegate the rules, and confirm that they can be accessed from the manager's dashboard, with meaningful labels.
6. Provide appropriate training and documentation to line managers.

	delegated rule
	How to delegate a rule Process Commander documentation

SysAdmin category