This page was last edited on December 17, 2014, at 16:45.
Comments or questions about this documentation? Contact us for support!
Rules are mandatory for managing actionable events generated from the System and Business event flows submitted by the Browser Tier. To add rules, you must create a package and then a set of rules. For details about rules, refer to the Genesys Rules System documentation.
As of version 8.1.2, Genesys Web Engagement supports multi-package domain oriented rules. You can map your rules package to a particular domain by reversing the domain zone in the name of the rules package. For example, the blog.genesys.com domain would have a rules package called com.genesy.blog.
You can have multiple rules packages on the same server at the same time. New rules packages (with a different package name) that are deployed do not rewrite the current rules, but are instead added to the current rules set. When the existing rules package is deployed, it rewrites selected package rules in the current rules set.
This domain mapping is applied hierarchically - the "root" domain is processed by the "root" package and the sub-domain is process by the sub-package and all parent packaged (including "root").
For example, your website contains the following sub-domains:
And you have the following rules packages:
The rules packages are processed as follows:
Domain | com.genesys | com.genesys.blog | com.genesys.communication | com.genesys.communication.personal |
---|---|---|---|---|
genesys.com | + | - | - | - |
blog.genesys.com | + | + | - | - |
communication.genesys.com | + | - | + | - |
personal.communication.genesys.com | + | - | + | + |
Complete the steps below to create the rules package associated with your Web Engagement application. This procedure is an example of how to create a rules package. For further information about creating rules, refer to the Genesys Rules System Deployment Guide.
Prerequisites
Start
End
Prerequisites
Start
End
Prerequisites
Start
End