How to Set-up Cleo Clarify Server Exit Points
Background of Clarify Exit Points
Clarify Exit Points are specialized events activated whenever certain inbound EDI transactional activities occur. Once assigned to a Business Process, each Exit Point can be configured to alert Clarify users via email when certain activities occur, provide relevant data, and help you quickly identify and address errors.
Type of Exit Points
•Inbound Acknowledgment Error - Raises an Event when an inbound acknowledgement is received and not accepted or accepted with errors. If enabled, this Exit Point will raise an Event for each inbound 997 that reports an error. Launches at the message or document level. For a list of codes, see Acknowledgement Error Codes
•Inbound Duplicate Interchange - Raises an Event when Clarify identifies a duplicate interchange. This only works when the Process Duplicate Interchanges check box in the Inbound EDI Route editor is not selected.
•Inbound EDI Route Error Handler - Raises an Event when an Inbound EDI Route used during processing contains an error. Launches at the Interchange level.
•Inbound EDI Route Not Found - Raises an Event when Clarify cannot find an Inbound EDI Route during processing. (For example, if Clarify encounters a Sender ID with no associated route.) Launches at the Interchange level.
•Inbound EDI Route Process Binding Not Found - Raises an Event when Clarify finds a route, but does not find the corresponding process binding (to the Business Process used for the message/interchange). Process Binding is set in the Inbound EDI Route editor. Launches at the Interchange level.
•Inbound Interchange Processed - Raises an Event every time Clarify identifies and analyses an EDI interchange. Processed does not mean "processed without errors" - you can still get other Exit Point notifications after receiving an Inbound Interchange Processed notification.
Location of Exit Points
By: Sean Hoppe on