In order for transactional data to display in various pages of the CIC Cockpit, some configuration to your integration Projects in the CIC Studio will be required. This includes:
- Checking out Cleo-supplied Projects and other resources from the Cleo repository.
- Setting dependencies between those Projects and your existing integration Projects.
- 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.
To build a non-EDI cockpit Ruleset, then you will need to create that on your own using the actions available out of the product.
When using a single CIC environment
If you have a single CIC environment and have not procured a Stage/test environment, then 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 the sender ID is not different between Prod and Stage.