Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Creating guidance for developers

Updated on November 18, 2021

Create internal documentation to provide guidance to the developers who implement or extend your application.

Use the following techniques to create internal documentation:

Adding usage information to a rule

Add usage information to a rule to help developers decide whether they can reuse the rule in their features or applications.

As a best practice, provide usage information when you create a rule.
  1. Open a rule by searching for it or by using the Application Explorer.
  2. Click the History tab.
  3. In the Documentation section, enter text in the Description field that describes the purpose of your rule.
  4. In the Usage field, enter text that helps developers understand how to use this rule.

    For example, you can describe the expected inputs and outputs.

  5. Click Save.

Adding historical information to a rule

Describe the recent changes to a rule in the rule history to help developers trace your implementation and compare versions more quickly.

  1. Open a rule by searching for it or by using the Application Explorer.
  2. On the History tab, click View full history.
  3. Click History For All Versions.
  4. In the Add Memo field, enter text that describes the differences between this version of the rule and the prior version.
  5. Click Add Memo.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us