You can create a generic service contract for a Ruleflow. This is not an enforced contract but a description of the inputs expected and outputs produced by a Decision Service generated from the Ruleflow. This is useful to document the "API" of a Decision Service or for use with the underlying mechanism such as REST/JSON that does not have an enforced contract. The generic service contract is output as a .csv file such that you can view it in Microsoft Excel or reporting tools that support .csv format.

For example, the CSV file for the Tutorial's tutorial_example.erf looks like this:
Service Contract for Ruleflow
               
 ,,Datatypes,Masking,Input/Output
               
Cargo,,Cargo,,I/O
 ,needsRefrigeration,Boolean,,I
 ,volume,Integer,,I
 ,container,containerType{String},CDT,O
 ,weight,Integer,,I
               
               
Custom Data Types(CDT)
containerType,standard,oversize,heavyweight,reefer,
When tutorial_example_ServiceContract.csv is opened in Excel, the CSV file looks like this: