Debugging a Business Rule: Getting Traces Generated by the Customization Engine

These traces define the problems encountered (i.e. scripts not found, scripts not valid syntactically, scripts failing at runtime, etc.). For this purpose, you need to set the following variable: CKE_CUSTO_TRACES=1

By default, traces are generated each time a business rule is executed on a given object, whatever the type of objects and the opening ID.

If you want to focus on a particular opening ID and on a particular type of object, you can define it using the environment variable: CKE_CUSTO_TRACES_RESTRICTION=OpeningID;ObjectType.

You can also define a list of associated OpeningID/ObjectType like this: CKE_CUSTO_TRACES_RESTRICTION=OpeningID1;ObjectType1;OpeningID2;ObjectType2;...;OpeningIDN;ObjectTypeN

If you do not want to define the type of object, and find all the traces for a given opening ID, set the variable as follows: CKE_CUSTO_TRACES_RESTRICTION=OpeningID1;;OpeningID2;; until OpeningIDN;; if need be.