Cockpit Implementation

In order for transactional data to display on various pages of the CIC Cockpit, some configuration to your integration Projects in the CIC Studio is required. This includes: 

1. Checking out Cleo-supplied Projects and other resources from the Cleo repository.
2. Setting dependencies between those Projects and your existing integration Projects.
3. Checking out document-specific Projects and configuring them to work with existing Projects. This includes predefined Business Process tasks and Rulesets which can then be referenced by inbound/outbound Routes, Business Processes, and Rulesets in use with existing Customer Integration Projects.

Please see how to get data from the CIC Studio to the CIC Cockpit for more details.  

Non-EDI Implementation

If you want a non-EDI cockpit Ruleset, you must create it yourself using the actions available in the product.

When using a single CIC environment

If you have a single CIC environment and have not procured a Stage/Test environment, you can override the trading partner name in the Cockpit Ruleset by modifying the sender ID to make it unique between Prod and Stage if it's not already.