Use the Custom Restrict node to apply restrictions using custom classes. You can base the restrictions on both predefined and custom attributes. The behavior of the custom restrict node is same as that of the restrict node, but the only difference is that you can specify a custom class to apply the restriction. The following table lists the properties and descriptions of the node:
Property Name |
Description |
Name |
Use this as a display name in the campaign strategy editor. If you do not specify a name, then the default name is Custom Restrict. |
Description |
Use to specify the description for the Custom Restrict node. |
Type |
Type property decides whether to apply the restrictions permanently or temporarily. If the restrictions are of type permanent, the contact which matches the restriction condition is not attempted and gets the disposition as Restricted_Other. If the restrictions are temporary, the contact which matches the restriction condition is not attempted. The contacts is validated against all the restrictions defined in that handler again after the specified recheck interval. The contact is attempted for dialing only when it does not match any of the restriction conditions. The default value is permanent. |
Re-check Interval |
Use this to specify a time interval after which when a contact attempt is restricted because it matched some restriction of type 'temporary' it will be again checked for all the restrictions defined in that handler. If no value is specified for this parameter then it will be considered as 1 minute. |
Custom class |
Use to specify the custom class POM can use for a custom implementation. Custom class must be the fully qualified Java class name and this class must be available on all POM servers in the system. For more information ,see Developer Guide for Proactive Outreach Manager. |
