Create a Message Filter to apply user-defined rules and conditions on inbound messages (AS2 generally) coming from external channels such as Cleo Harmony or other third-party software.
If this object can be shared across multiple Projects, Cleo recommends creating the object as part of a Core project.
- Select File | New | Message Filter from the main menu bar. The New Message Filter window appears.
- Provide the Source folder, Package, and Name.
- Click Finish. An editor appears.
You can also use the Wizard to create this object. Click New to select the object.
To define this object, you specify the channel on which the message will be received, the conditions/rules that the message will be filtered against, and the associated Event to be raised when conditions match.
The following steps take place in the Message Filter editor, which has these sections: Message Channels, Rule Builder, and Event Triggers.
- Under the Message Channels section, click Add to create a channel and begin defining the object. These indicate the source and type of incoming message being subscribed to. The Add a Channel window appears and provides a list of available external message interfaces. Default channels include payloads and acknowledgements to and from EXTOL Secure Exchange (ESX).
- Under the Rule Builder section, click Add to begin creating rules and conditions. Each rule consists of three parts: Message Header, Condition, and Value.
Note: To specify the conditions between Message Headers and Value, use these Match drop-down options:
- Any: This establishes an "OR" statement; conditions can be met, some may not, but rules may still apply.
- All: This establishes an "AND" statement. This requires all conditions to be in order for the rule to apply.
- None: This basically ignores any of the rules.
Note: Even though the Message-Header field can be entered with free-form text, you must ensure that the entries match the actual properties as named in the incoming AS2 message. For example, if your incoming message header is AS2-Sears-From, then this must be exactly how it must be defined in this object. Common message headers include:
Always confirm your channel’s actual header properties.
- Under the Event Triggers section, click Add to indicate the Event to be raised if the contents of the message header match those defined in the Rule Builder section.
Note: Events must exist in your Project prior to defining the Message Filter object.
- Click Save to complete this task.
Please sign in to leave a comment.