Fixing an Outbound transaction: Connector vs Rules Engine

There are two options to fix an outbound transaction with an Invalid status. They are -

1. Using the Orderful Rules Engine
2. Making changes to your connector

This article elaborates on when to use the Rules Engine vs when to use the Connector. 

Rules Engine

The Rules Engine was designed and is best suited for minor changes to the data. 

Examples of when to use the Rules Engine:

• Date/Time format changes
  • Example: The date needs to be changed from YYYY/MM/DD to DD/MM/YYYY format. 
• Setting hard coded values
  • Example: The vendor number needs to be set '78960'.
• Simple conditional logic
  • If sender ISA is 90876, set Vendor number to 12345)
• Replacing values in the transaction
  • Replacing vendor part number qualifier from VN to VP as per specifications. 

Connectors

Irrespective of whether you chose to build your connector ground up or if you choose to use a low code IPAAS platform, the connector is better suited for more complex logic because it is more than likely to have logging, versioning, and capability for making advanced changes to the transaction. 

Examples of when to make changes to the Connector:

• Turning data around from an inbound document
  • Example: Getting the buyer part number from the purchase order into your invoice.
• Complicated changes that require multiple functions
  • Example: If you have to split a string by commas and then uppercase them. 
• Any changes on looping elements
  • Example: Some Trading partners require only Bill To address while others require Bill To, Ship To, and Ship From. 
• Creating new segments
  • If a TP requires summary segment and you are not sending it through the connector today, then this change must be in the connector. 
• Structure of the document
  • Common in the 856 Advance Ship Notice. Some Trading partners will require an SI structure while others will require an SOI structure.