This article will outline the main differences between CIC Studio (Cloud Edition) and Clarify Studio (Private Cloud Edition).
The CIC Studio allows you to design and build integration projects on your desktop and publish them to the Cleo Integration Cloud. While CIC Studio provides much of the same functionality and UI as the on-prem Clarify Studio, it has several important distinctions:
- Users download CIC Studio directly from Cleo Integration Cloud
The download option is available from the Integrations > Studio Download page on Cleo Integration Cloud. Once downloaded locally, users can install CIC Studio and can quickly get started building integrations.
2. The CIC Studio does not require licensing
There is no licensing required for CIC Studio. Therefore, the options that were used in the on-prem Clarify Studio to view, update and apply a server license have been removed from the Admin Console.
3. Users will sign into CIC Studio
CIC Studio now requires you to sign-in and select a tenant. In most cases, only one tenant will be available; but multiple tenants may exist - Production and Test are examples of multiple tenants. By selecting a tenant, the CIC Studio, when launched, will automatically connect to resources specific to your selected tenant. Users sign in with their usual CIC login credentials. SAML-enabled tenants will automatically redirect the user to IDP at sign in.
Note: all user management, including sign-in credentials and permissions for CIC Studio users, will now be controlled in Cleo Integration Cloud. For more details on user management in CIC, please see User Management.
4. New Cloud Monitor & Cloud Adapter objects are available
Two new objects are available in CIC Studio - the Cloud Monitor and the Cloud Adapter. These will replace all other monitors and adapters that currently exist in Clarify Studio. These two objects are the primary means for sending data back and forth from the CIC Studio to the Cleo Integration Cloud.
- A Cloud Monitor waits for incoming payloads and launches an Event to execute Business Process(es) to process the incoming payloads. In this way, Cloud Monitors are similar to other monitors in Clarify. However, in the case of CIC Studio, Cloud Monitors monitor Endpoints created in Cleo Integration Cloud rather than the file system (File Monitor) or databases (Database Monitor). For more details, see Cloud Monitors.
- A Cloud Adapter is responsible for ensuring files coming out of the transformation engine are sent to their final destination Endpoint. For more details, See Cloud Adapters.
5. All Monitors have been removed.
The following objects are no longer used in the CIC Studio: File Monitors, Database Monitors, Email Receive Monitors, and Web Service Providers (SOAP).
CIC Studio provides comparable functionality for the first three by using a Cloud Monitor that can connect to Endpoints of different types to receive payloads from file systems, databases or over email.
6. Web Service objects removed
The SOAP Web Services Provider Objects have been removed. The CIC Studio still supports the use of the Web Service Consumer object, but for REST only. As such, certain Business Process tasks will not be made available. This includes the following tasks:
7. The Admin Console has removed functionality that no longer applies
Some of the functionality in the Admin Console that does not apply for CIC Studio has been removed including:
- The Resource Monitors view still exists in CIC Studio and reports on resource metrics for the Cloud Monitor. Metrics for the other types of monitors and adapters that existed in on-prem Clarify Studio, but do not exist in CIC Studio, have been removed.
- The Schedules view has also been removed in CIC Studio. This calendar view showed all deployed Process Schedules. Given that scheduling of integrations works differently in CIC Studio (Data Flows are scheduled in the Cleo Integration Cloud, this view is no longer needed.
- The Settings view has fewer setting types available. Business Process, Email, and Logging have all been removed.
- The Server controls have changed.
- The Server Environment toolbar has been streamlined. Users cannot add, edit, or a server connection.
- The buttons used to update a server, view server license, and apply a server license have been removed.
- The ability to sign in and out of a server connection has also been removed.
Besides the changes described above, the Admin Console still provides most of the same UI tooling to bundle and deploy Business Processes. The Projects view, Business Process view, and Auditor views function the same as they did in on-prem Clarify Studio.
8. Publishing integrations to Cleo Integration Cloud rather than remote servers.
The CIC Studio allows you to publish integrations that you build in the CIC Studio directly to the Cleo Integration Cloud. There is no Local Test Server.
9. Pre-built Core Projects are provided to synchronize data with the CIC Cockpit
Several new Projects - called CIC Cockpit Projects (CCP) are available from the Cleo repository that users will download and configure that their transactional data (EDI and non-EDI) can display in the CIC Cockpit's Messages view.
These Projects contain predefined Business Processes tasks and Rulesets that can be configured with existing inbound/outbound Routes and other resources in your integration Projects.
This includes out-of-the-box Projects for various X12 4010 EDI transactions.
This is explained in Populating Your Dashboard.
10. Version 2 Rulesets only
The Ruleset wizard no longer provides the option to create V1 Rulesets. V2 is the default for all new Rulesets.
11. Renaming of Objects due to Rebranding
Some named objects in the product have been changed to align with the Cleo Integration Cloud Studio name.
12. In-Product Help changed to Solution Center
The Help system in CIC Studio will direct the user to Solution Center help, rather than in-product help. This will allow us to provide the most up-to-date help from within the product. This also applies to the Welcome page.
Other objects/wizards removed
- External API wizard
- Formula wizard