Functions
A dynamic logic function is the most generic type of dynamic logic: it can have one or more input arguments and return different types of output. A dynamic logic function is used to extend default behavior in certain areas. Each usage of dynamic logic functions is described in a separate paragraph below.
Extension
This is a common signature, available in all the applications. This signature has no bindings. It allows for writing extensions to the dynamic logic scripts that are delivered by the product.
Reusable Code
This is a common signature, available in all the applications. This signature has no bindings. It allows for writing standalone methods/reusable classes code that can be shared across other scripts.
If a reusable dynamic logic is changed, and the changes are not reflected in the dynamic logics that have used or imported the reusable dynamic logic. To get it to work, invoke the invalidateall operation before starting other operations. See Invalidate Dynamic Logic, for more info.
|
Test Unit
A dynamic logic with the Test Unit signature tests another dynamic logic. Such a dynamic logic that runs a test on another dynamic logic is called a test case. A test case sends objects as input to the unit under test (UUT) and validates the output.
In or Out | Name | Type | Description |
---|---|---|---|
Out |
Not Available |
Boolean |
Returns |
You can run a test case using the Test Dynamic Logic. |
URL Composition
A flex code field usage of a dynamic record definition can reference a dynamic logic function to build up the URL needed to access an external application. In this way it is possible to change, for example, a server location in a central way.
In or Out | Name | Type | Description |
---|---|---|---|
In |
dynamic Record |
Dynamic Record |
The dynamic record |
Out |
n/a |
Alphanumerical |
The composed URL |
Example:
return " http://financialsystem.oracle.com?p_check_number= "+dynamicRecord.checkNumber
Validation Check (Edit Product)
This type of dynamic logic can be attached to a user defined validation check to edit product and its list resources.
-
Which input parameters are passed along depends on the "level" field of the validation check.
-
Each level uses the "Product" object as input, this object allows the logic to iterate over the product service options and product services contained in the validated product.
-
The following signature applies to validation check (Edit Product), the write protection is disabled for this dynamic logic which mean using this dynamic logic a user will be able to edit a product attributes and its list resources:
-
Validation Check (Edit Product) applies at Product Level
-
In or Out | Name | Type | Description |
---|---|---|---|
In |
validation Check |
Validation Check |
The validation check being evaluated. Can be used to parametrize the dynamic logic. |
In |
product |
Product |
The product that is being evaluated |
Out |
object |
Product |
The product updated by the dynamic logic functionality |
The following list resources are allowed to be updated based on the entity (including native fields, dynamic fields and records as applicable):
-
Product Services
-
Product Service Options
-
Product Limit Renewal Periods
-
Product Provider Groups
-
Parameter Values
-
Carry Over Settings