Query Based Data Element (QBDE) Evaluation

The Query Based Data Elements (QBDEs) are evaluated through one of the following ways:

Based on the refresh conditions, when the record is opened (even from the draft).
Based on the manual editing of the trigger elements, through user interface (this does not include the situation in which the record is initially created).
Based on when the record is created. That is, the system evaluates QBDE values based on trigger element population, when a new record is created.

When you create a business process (BP) record (creation step of a BP record), the system evaluates the QBDEs:

When the trigger element is edited manually on the form in the creation step.
When the trigger element is auto-populated.

However, QBDE query conditions with null or empty values are ignored when dynamic values are selected in the following areas: Data pickers, Autocreation (BP Creator and BP Line item creator), Gates, Auto updates status setup, and Planning sheets.

Notes:

Because the system evaluates QBDEs in a random order, Oracle recommends that you do not create a QBDE that uses a formula that references another QBDE.
DEs that have been defined as a QBDE trigger element should not be evaluated as part of QBDE calculation.
If a BP Data Picker (BP Picker) or any Data Picker is selected as a trigger element for QBDE and the picker value is automatically populated (auto populated) instead of manually entered, the QBDE element will not be evaluated.
Query conditions ignore the Timestamp for Date-type data elements. Therefore, at run-time, when queried on a date picker, search results display records that satisfy only the date criteria. For example, all records updated on April 10, 2024 display, regardless of the time they were updated.
When using QBDE, be aware that query elements are rounded off to use two decimal places, even if the Base Currency and various defined currency fields are different.

QBDE Evaluation in BP Records Created through CSV import or RESTful Services

The system evaluates the QBDEs when the trigger element is populated by way of a record that has been created through CSV, RESTful service (if the trigger element is entered in the input CSV request), BP templates, and Bypass I Step auto-creation.

QBDE Evaluation in BP Records Created through Auto-Creation

When a BP record is auto-created through Bypass I Step, the system evaluates the QBDE values in the auto-created records based on the trigger element population. When a trigger element is used for QBDEs, and the trigger element is auto-populated, the system evaluates the QBDE values in the creation step of the auto-created record.

In the case of Bypass I Step auto-creation, if the auto-created record resides in Initiation Step, the system does not evaluate the QBDEs.

The system evaluates formulas that use QBDE in the creation step of the BP form.

If the QBDEs are used in the workflow routing conditions, the QBDE values will be populated in the log and view form (if they are added after the successful creation of records). In this scenario, the system evaluates the QBDE values after evaluating the auto-populated DEs and formula DEs on the form.

You can use the QBDEs in BPs in the workflow routing condition, which lets you determine the route of the workflow based on the value of the data element.

The system evaluates the formulas in QBDEs, in the creation step of a BP record.

The system will not evaluate the QBDE values based on trigger element population in BP records that have been created by way of copy (with or without attachments). For example, when you create a Budget Item BP, you can view the QBDE Assigned Budget value, evaluated from the project cost sheet in the creation step.

QBDE Evaluation in BP Records Created through CSV import or RESTful Services

QBDE Evaluation in BP Records Created through Auto-Creation

See Also