The b2bcloud.core Project provides important resources to be used with all CIC implementations. Contents include Exit Point Events and Business Processes that should be assigned on the server once this Project has been deployed. There are also Business Processes that can be used as part of Inbound and Outbound EDI Route Processes, Connection Business Processes, as well as for error notifications.
Note: All other Core and Trading Partner Projects in your Studio Workbench should depend on this Project.
These Projects are available for checkout from https://cleo.plan.io/svn/b2bcloud
Important Business Processes
These Business Processes can be used for Error notifications, Inbound and Outbound EDI Route Processes, and Connection Business Processes.
Used on EDI Envelopers as the connection BP. Contains the necessary parameters required to integrate with older CIC Harmony implementations.
This is the standard error notification and should only be used on Business Processes that will not pass a User Reference value. The only parameter is bpsName.
This is the Error Notification BP that should be used on all inbound and outbound message processing (both EDI and non-EDI). The parameters on this business process are required when generating an email notification or creating a Zendesk ticket using the CreateTicketBPS within the com.cleo.b2biaas.clarify cockpit project.
This is the error notification when there are no outbound routes configured for an outbound document. This BP must be invoked inside the Version 1 Data Application Ruleset (DARS) as shown below.
This is the error notification when there are no outbound routes configured for an outbound document. This BP must be invoked inside the Version 2 Data Application Ruleset (DARS) as shown below.