Cleo Clarify supports every phase of business integration – building, integrating, and maintaining – in one simplified, streamlined product. An individual may create, test, and deploy integration processes from beginning to end, or Clarify can be used by teams with multiple participants and roles – including business analysts, developers, and IT operations personnel.
This set of comprehensive topics describe the available resources, tools, and processes used to transform data as part of an integration solution.
This set of topics describe Rulesets and how to use rules to transform your data.
A Ruleset is a collection of rules that govern the way Clarify transforms one business document into another.
While syntaxes vary from Ruleset to Ruleset, the basics behind creating rules and customizing each transformation remain the same, and rely on the use of Actions, Variables, and Methods.
A Ruleset Action performs some form of operation on data during a transformation run.
Compares two numbers (Number1 and Number2) and returns the lowest (minimum) number.
Cleo Clarify v5 introduces several new features. Many of these are closely interconnected, supporting the functions of other features, editors, and resources. For the latest feature descriptions, please refer to the Clarify v5 Release Notes on the Support Portal of Cleo.com.
Clarify is a platform-independent business integration middleware that tackles a wide variety of business integration requirements. It supports Business-to-Business, Application, Data, and Cloud integration, with one investment in middleware, tools, and skills.
Clarify is divided into two components: a design-time environment (Clarify Studio) and a runtime environment (Clarify Server).
Learn how the Studio is structured, and get familiar with its user interface.
Cleo recommends specific guidelines for creating, managing, testing, and deploying Projects, Packages, and objects.
Clarify supports options for sharing the same objects between different Projects, and for sharing the same objects and Projects between different users.
Clarify provides an interface to the Subversion® version control system, which allows users to share their projects on repositories, where they are stored afterwards.
This set of topics describe how to use objects to input and output data.
This set of topics describes how to use Schemas to define source and target documents or data.
Create a Ruleset object to set up a collection of rules that govern the way Clarify transforms one business document into another.
Returns true if the text matches the specified regular expression.
Returns the maximum number of two numbers (Number1 and Number2). For example: Max: [Number1=4, Number2=3] → [Returns] =4.
Moves data from source to target. (Replaces MoveNumeric, Normalize, Trim, TrimLeading, and TrimTrailing)
Multiplies two values (Factor1 and Factor2) and returns a numeric result.
Returns the negated value of a number.
Returns a new String replacing all multiple occurrences of white space with a single occurrence. It also trims the original text.
Changes a boolean value from False to True, or True to False.
Returns boolean of false if the text contains the specified string (str) value. Returns false if both strings are null.
Returns false if text ends with suffix, otherwise returns true. If both strings are null then returns false.
Returns boolean of false if text starts with prefix, otherwise returns true. If both strings are null returns false.
Returns boolean result of true when two numbers are equal (or both are null).
Returns a number.
Returns boolean result of false when two numbers are equal (or both are null).
Takes a number from source and converts it to a sting so that automatic trimming of leading zeros is prevented.
Checks whether up to 10 booleans are true, and returns a boolean.
RawMove transfers data at face value. Unlike Move, it does not facilitate automatic trimming/padding/spacing behavior.
Returns the remainder of a division.
Replaces occurrences of str in text and returns a new string.
Context points can be used to pass RDO and ENV variables between a Business Process and a Ruleset, or to backup and restore the data within the Ruleset. RestoreContext updates the variables and the RDO in the Ruleset with the data that is in the Storage Node.
Used in conjunction with the ExecuteMessageBusinessProcess and ExecuteRouteBusinessProcess Actions to return the script ID from a Route.
Returns a new list of strings after splitting the specified text into sub-strings based on a regular expression.
Returns true if text starts with prefix, otherwise returns false. Returns true if both strings are null.
Compares two strings for equality and returns a boolean.
Returns true if both strings are equal after normalizing them. If both strings are null returns true. If one is null and the other is not returns false.
Returns boolean of true if both strings are equal after normalizing them. If both strings are null then returns true. If one is null then returns false.
Compares two strings for inequality and returns a boolean.
Returns a substring of a string. (Used with SubstringReplace). For example, a substring of the word "computer" could be: puter or comp. Another use case would be take a 10-digit phone number and return only certain digits.
Subtracts the first number (subtrahend) from the second number (minuend) and returns a numeric result.
Subtracts two DateTimes and returns a new DateTime.
Subtracts the specified values from the DateTime and returns a new DateTime.
Replaces a substring within a string.
This task subtracts or decrements Duration from the DateTime value.
Returns a new string after converting all characters to lower case.
Returns a new string after converting all characters to upper case.
Returns a new string with leading and trailing spaces removed.
Returns a new string with leading spaces removed.
Returns a new string with trailing spaces removed.
Variables supply rules (and rule conditions) with values for their Inputs and Outputs parameters. A variable can hold system-generated information that is likely to change at runtime; it can also hold a user-defined initial value (in effect, making it a constant) – but that value too may change, if desired, at runtime.
A Ruleset Method, like a Composite Rule, is used to group rules. An important difference however, is that the method includes Type parameters which correspond to data types in the source and target of the Ruleset. Methods can also be re-used within the Ruleset, thereby providing better maintainability.
Configure Rules and general Ruleset behavior using several tabbed views in the Properties view located at the bottom of the Ruleset editor.
The new transformation engine gives you the ability to run Rulesets (complete or partial state) within the Studio without having to deploy the Ruleset and other resources first. In fact, you can test a Ruleset before even creating other objects such as Business Processes, Adapters, etc. This allows for regular testing, debugging, and observing specific results or behavior of the rules from directly within your transformation Ruleset.
Rules can be temporarily disabled so that they do not execute as part of normal Ruleset operation.
This example shows how a Ruleset can be configured to use different actions, conditions, and variables. There are many different ways to create rules to achieve a single transformation goal. Because of the many options Clarify provides, you may - and likely will - find other ways to create rules that accomplish your transformation needs.
Use these objects to further customize your transformations.
Clarify now includes a next generation transformation engine, and with it new versions of the Ruleset and other supporting resources, as well as new features and improved Ruleset usability.
This set of topics describe concepts and objects used to identify, process, and route data.
This set of topics describe how to use Business Processes to sequence and execute the tasks necessary for your integration solution.
This set of topics describe several Wizards and other tools to assist in the creation and configuration of Project resources.
Promotion describes the act of moving different resources (mainly objects and Projects) into a server environment that can be used for testing or production-ready integration with external servers. The Studio provides two methods to promote resources – either locally or remotely.
This set of topics describe how to configure Clarify to integrate with external applications, programs, and interfaces.
The following topics discuss guidelines, provide recommendations and best practices, and explain available tooling which support good system management and health for your Clarify environments. Topics cover everything from backups and upgrades, to data purging and daily operational maintenance.
This set of topics provide installation procedures, system requirements and other configuration details for the Clarify Studio.
This set of topics provide installation procedures, system requirements and other configuration details for the Clarify Server.
