An Application Interface is an object that contains attributes defining Application Routes. The CIC Studio uses values from a Data Analysis Ruleset (DARS) to route data by comparing them to Application Routes and Outbound EDI Routes. It uses information contained in your data to help identify that data's purpose and to which trading partner it should be sent. One example of an attribute could be a customer number.

An Application Interface only holds the attribute containers in this object; it does not define values for the attributes. That is done later within each Outbound EDI Route or Application Route that refers to this Application Interface. This makes it easier to use a single Application Interface with multiple Routes.

Each Application Interface can hold up to 20 attributes.

Video: See the Cleo Community Video for more information on this object.

Business Use

Both outbound EDI and A2A integrations require this object.

How the Object Works

You can either use a single Application Interface per Route or have multiple Routes point to a single Application Interface.

Process Summary

To use this object, you must:

• Create and define the object.
• Reference it as the Application Matching Parent in a Route.
• Define the values for each attribute in the Route.

Defining Application Interfaces

Defining an Application Interface creates the individual attributes that will identify the purpose of outgoing data and to which trading partner it should be sent. These will be available to use in an Outbound EDI Route.

These steps take place in the Application Interface editor.

1. Under the Attributes section, click the Add button to create an attribute. The default text Attribute appears in the list.
2. Type a new name to describe the attribute and click Enter.

   Note: You are only creating labels for the attributes in this object; you will set the values for each attribute from within each Outbound EDI Route that refers to this Application Interface object.

3. Repeat Steps 1 and 2 until you have all the Attributes needed for your Outbound EDI Route(s).
4. Click Save to complete this task.

Next: Reference the Application Interface in an Outbound EDI Route. See Defining Outbound EDI Routes for more information.