Rule Management with Files

  • Updated

Using the File System for the Rule Development Life Cycle

  • No Catalog components are required (using a source control system is highly recommended)
  • Rules are managed the same way as any other application source file
  • Rule changes are propagated by copying rule application files across environments
  • Only one rule author can edit the same rule application concurrently
  • Rule changes can be hot-deployed from the production file system without restarting production application
  • Production application is not dependent on stability of the Catalog web service and database
  • Audit trail for rule changes is limited to whatever 3rd party source control system provides and is only available in development
  • A simple, custom-coded component may be required for integration with automated build processes or continuous integration


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.