This document intended to provide a detailed guide on how to deploy a Business Rule using CATRule and CATRuleExit files.
Version – 2022x FD01 (FP2205), 2023x FD04 (FP2333)
Pre-requisites: Installed Native Client.
Business rules development can be done using the CATRule and CATRuleExit files. This method is a Legacy way of doing customization, however it is strongly recommended to use Data Setup app.
With these files, the collaborative space axis is not taken into account whereas, with resource sets the collaborative space is considered. The user must bind a resource set to a collaborative space inside the Data Setup app and the resource set will be executed in that particular collaborative space.
About CATRule and CATRuleExit files
The CATRule and CATRuleExit files are similar to a text file having the extension like MyBLFile.CATRule and MyBLFile.CATRuleExit. The CATRule file contains the Business Logic rule and the CATRuleExit file contains the details of the OpeningID, Type and Name of the script file. For example: CATRuleExit file
Opening ID: It provides contextual information and contains information on the context in which the rule operates.
Type: It is the input object to which the rule is applied (also called the Fact).
ScriptName: Name of script (Without extension
The CATRuleExit files can have multiple entries for different Types for the same Opening ID as shown in the above example.
Users can keep the CATRule and CATRuleExit files in client installation at the following location:
\\win_b64\\resources\\knowledge\\scripts
Note:
- Business Rule deployed on native client using above method does not get stored in database. You can only use it on the specific native client where it is deployed and not on the server (irrespective of the native client where server is accessed)
- Dassault Systèmes default CATRule and CATRuleExit files are also located at this path. It is not recommended to modify the default Dassault Systèmes CATRule and CATRuleExit files. It is not recommended to have multiple implementations of the same Opening ID for the same PLM Type.
Authors
Author: @JJ
