...
Preferably, if the logic is tight tied to a certain object type, it should start with the type code as a prefix:
Logic type | Formula Nature | Prefix | Suffix | Example |
|---|---|---|---|---|
Calculation Flow | calculationFlow | CF_ | CF_RebateRecords | |
Calculated Field Set | null (default) | CFS_ | CFS_ProductEnrichment | |
Contracts | CT_ | CT_DefaultContractLogic | ||
DataloadData Load | paDataLoad | DL_ | DL_ProductCost | |
Dashboard | null (default) | DB_ | DB_Waterfall | |
Price List | null (default) | PL_ | PL_National | |
Live Price Grid | null (default) | PG_ | PG_Computers | |
Quotes | null (default) | Q_ | Q_DefaultQuoteLogic | |
Groovy Library | library | Lib | SharedLib MonitoringLib |
...
InvoicePrice
CustomerPrice
ResultPrice
MarginNew
Exception: this This rule is not valid for logics serving as a custom HTTP API where the letter case of JSON fields needs to be matching the API interface specification.
| Info |
|---|
During deployment, the Groovy logic element scripts get compiled into classes. During logic execution, the logic engine instantiates singleton objects from those classes. These objects then get bound to variables with the same name as the elements. Thus, to call a method
Pricefx Studio will make IntelliJ interpret this as a static call – even though it’s it is not – and that will make the auto-completion work. |
Unique Element Names Within Projects
Element Names names should also be unique within the entire project – across all logics. This is to enable the auto-completion and unit testing with TDD4C.
...
Element labels are optional for those elements that are hidden for the end - users.