Skip to main content

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

Preparing for modifying rules

Updated on November 18, 2021

Adjust your application to your unique business scenario by modifying existing rules. As a result, you save resources, such as time and money, and deliver software that precisely meets your business requirements. You can also delegate a rule so that non-IT stakeholders can perform needed changes.

Before you modify a rule, you need to check out the rule to ensure that no other developer modifies the same rule at the same time. If your business requirements change, you can revert to the previous state of the rule, or completely delete the rule.

  • Checking out a rule

    To avoid accidental rule changes or conflicts that might result from multiple developers working on the same rule, perform a check out, so that you can lock the rule and safely make changes to it. By checking a rule out before editing, you avoid unwanted rule changes, and as a result save time and maintain a better quality application.

  • Restoring the earlier state of a rule

    During application development, you can undo recent changes to a rule and replace the current rule with a previous copy, even if another developer created the newer copies.

  • Creating guidance for developers

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

  • Delegating a rule or data type

    To delegate a rule or data type to enable your business line to configure simple application logic without involvement from IT, complete the following steps.

  • Deleting a rule

    Save disk space by deleting rules that are no longer relevant in your application. For example, during application development, you create a field property to capture a phone number, but later you need to capture multiple phone numbers. You create a list property, and then delete the field property. As a result, you improve the extensibility and user understanding of your application by providing only the rules that your application requires.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us