***************************************************** ***************************************************** ***************************************************** ***************************************************** ***************************************************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** This Confluence article was automatically generated from Asciidoc. Any changes you make to this document will be overridden! If you want to change the content, consider leaving a comment. You can edit the content directly here: https://gitlab.pricefx.eu/training/pricefx-knowledge-base/-/tree/dev/public/content/docs/concepts/introduction/logic-structure ***************************************************** ***************************************************** ***************************************************** ***************************************************** ***************************************************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING ********************** ********************** WARNING **********************
Within a Pricefx source directory (package), logics reside in the CalculationLogic
and WorkflowFormula
directories. Each logic consists of a few script files and metadata.
Metadata for logics are defined by the logic.json
file. There are three mandatory properties: uniqueName
, validAfter
, and status
.
uniqueName
Used to reference logics
validAfter
Used to schedule releases
status
Used to activate and deactivate logics
These three properties make up a composite primary key.
The logic.json
file also contains a property elements
. This property is an array of objects, where each object references one script inside the elements/
directory. These scripts — together with the associated metadata — make up an element.
|
There are many other valid properties in the logic.json
file. Price Studio helps you to maintain a valid structure by providing a visual editor.
|