The CIC Studio's transformation engine gives you the ability to run Rulesets (complete or partial state) 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.
A Run Transformation button can be found at the top-right of the Ruleset editor. Just make sure the Ruleset has been saved first.
Note on Project Dependencies: Please ensure that the
com.extol.ebi.lib.ebisrc Project is set as a dependency for your Project(s) being tested.
Flat File and EDI transformations
The screen below shows run options for Flat File and EDI transformations. You’ll need to provide certain information first:
- Source represents the incoming data to be used for testing; in this case, sample data or a document in a basic flat file format. Options include selecting the file from your workspace (recommended) or another file location.
- Target will be the immediate result of the transformation, in a flat file format. Again, options include placing the output file in your workspace or another file location.
Once you've provided the source and target information, the Run button is enabled, allowing you to launch the transformation.
Set how the test data will be read/written as defined in the selected Transformation Settings object. Browse from any available object visible from the current Project, and use Unset to clear the selected object.
Exit after launch (check box)
With this check box selected, the Run Transformation window closes once the transformation is complete. By clearing the check box, it keeps the dialog open to support continuous testing and debugging efforts.
Note: Use the LogInfo Ruleset action to display certain data in the Details section. Add this to your Ruleset as you test to have desired values displayed (string-only).
Click this button to display transformation/application logs. This does not display output results, but it is useful for troubleshooting.
A best practice is to keep sample data within your Project.
When testing a source Database transformation, use the Create Database File button, displayed next to the source field, in the Run Transformation dialog. This button opens a new dialog that allows you to choose a Database Select Adapter and an output file path to write the result of the Select Adapter as a Database File. This file is then used as the source for the Run Transformation.
Note: Current functionality supports the use of this button for source only; future development will provide the option to select an Insert, Delete, or Update Adapter for target.
After clicking the button, the Create Database File screen allows you to select criteria for source and target. Use the Select Interaction field to point to the Database Select Adapter in your package or Project. Only Select Adapters will be available (for source).
Selection Criteria (Optional): Use this section to add parameters to filter results. An example might be selecting from a specific table where a parameter equals a certain value. Calling the adapter would then pass this parameter.
Use the Output File Path to indicate the file name and location of the output result.
Finally, click Create to set the necessary source and target criteria. You are returned to the Run Transformation screen, and can then click Run to complete the process.