Business rule deployment

In a production PolicyCenter cluster, Guidewire requires that you deploy a rule before PolicyCenter can evaluate the business logic of the rule. Thus, to deploy a business rule is to make that version of the business rule active within PolicyCenter.

Before deployment, PolicyCenter creates a work-in-progress version of the rule. At rule deployment, PolicyCenter assigns a version number to the rule.

A rule must go through the following states before you can deploy the rule:

  • Draft
  • Staged
  • Approved

A rule must be in the approved state before it is possible to deploy the rule. Approving a rule does not deploy the rule. You must actively deploy a rule before PolicyCenter evaluates that rule at runtime.

Rule deployment is distinct from rule import. On completing a rule import, you must deploy any new approved rule versions before PolicyCenter can evaluate the rules.

In general, Guidewire recommends that you use separate cluster environments for each of the following in working with PolicyCenter business rules:

  • Development
  • Test
  • Production

Typically, you deploy a rule version in a production environment only.

Important: In a production environment, you must set configuration parameter BizRulesDeploymentEnabled to true and provide a value for configuration parameter BizRulesDeploymentId. If you have multiple PolicyCenter production clusters, the BizRulesDeploymentId value for each cluster must be unique.

See also