8/13/2019 17 Ten Guardrails to Success

1/2

8/13/2019 17 Ten Guardrails to Success

2/2

2/19/14 Video

https://academy.pega.com/prweb/PegaSSO/WmhSmvRrQ7qWntq73M7R4oiuqIskpuJu*/!THREAD1?pyActivity=%40baseclass.pzTransformAndRun&pzTra 2/2

4. Limit Custom Java

Avoid Java steps in activities when standard PRPC rule types, library functions, or act ivity methods are available.

Reserve your valuable time and Java skills for implementing things that do not already exist!

5. Build for Change

Identify and define 10-100 specific rules for business users to own and maintain. Activities should not be on this

list - use other rule types for business-maintained logic.

6. Design Intent-driven Process

Your application control structure must consist of flows and declarative rules. Use flow actions to prompt a user

for input and present fewer than five connector flow actions for any individual assignment - if you need more than

that, you need to redesign the process.

To maximize reuse, create activity rules that implement only a single purpose, and call activities only as needed.

7. Create Easy-to-Read Flows

Flows should fit on one page and should not contain more than 15 SmartShapes (excluding Routers, Notify

shapes & Connectors). If a flow has more than 15 SmartShapes, either create a subflow or use parallel flows to

perform additional functions.

8. Monitor Performance Regularly

For best results, evaluate and tune application performance at least weekly. Use the Performance Analyzer (PAL)

to check rule and activity efficiency - establish benchmarks early on; compare these results to follow on readings

and correct application as required.

9. Calculate and Edit Declaratively, Not Procedurally

Whenever the value of a property is calculated or validated, use declarative rules wherever appropriate.

Use a declare expressions rule instead of a Property-Set method in an activity and a declare constraints rule

instead of a validation rule.

10. Keep Security Object-Oriented Too

Your security design should be rule-based and role-driven based on who should have access to each type of work.

Use the standard access roles that ship with Process Commander only as a starting point and use RuleSets to

segment related work for the purpose of introducing rule changes to the business, not as a security measure.

Never code security controls in an activity.