Sign in
< Back to Top

Naming Conventions for CIC Cockpit Resources

It is a good practice to use a standardized method for naming Endpoints, Data Flows, and Access Points in CIC.  The benefits of good naming practices include the following:

  • At-a-glance understanding of the context surrounding your Endpoints, Data Flows, and Access Points 
  • Enhance clarity in cases of potential ambiguity
  • Avoid naming collisions or duplicate names
Resource Recommendation
Access Point Use a name that reflects the following:
  • Machine the Access Point resides on.
  • Purpose of the Access Point
Endpoint Use a name that reflects the following:
  • Direction of transfer, for example, inbound or outbound.
  • Document type you expect to transfer to or from the Endpoint

Note: Some Endpoints are automatically named after a CIC Studio object and  cannot be renamed. In these cases, be careful about how you name your CIC Studio objects. For information about naming CIC Studio objects, see Naming Conventions.
Data Flow Use a name that reflects the following:
  • Endpoints used
  • Trading Partner
  • Purpose of the transfer

Related topics

Related articles

Comments

0 comments

Please sign in to leave a comment.