RQF Request Types

Each request created with ProRequest is assigned an request type. This request type defines:

  • The status network and the initial status at creation

  • Fields and how they are grouped

    • For information on field labels, input help and value checks, see the "Fields" Customizing view in the online documentation for the "Technical structure" field.

  • Status dependent field control

    • In addition to the status, an assignment of the dynamic field control can also be made via selection conditions depending on the various values.

    • With several valid assignments, the first set is used according to priority.

    • With status *, the assignment is only determined via the selection conditions.

    • The target field name can also be masked with *.

  • Dependent values

    • Allows setting field values dependent on other field values.

    • The value is defined for a target field and via selection conditions when this field value is to be assigned to the field. Thus, an activation is also possible depending on several fields and their values.

    • Initial values can also be defined via the "New request" field (X = yes) of the "Application header and control data" context.

    • In case of several valid assignments, the first record is used according to priority.

    • Values can also be set in multiple levels:

      • <field1> sets <field2> and this <field3>.

      • However, it should be noted that only when a field value is changed by the target field, further actions are triggered if necessary.

      • If as in the above example the <field2> already contains the value which should be set, then <field3> will not be changed either.

  • Valid values

    • Allows the definition of valid field values, depending on other field values.

    • It is defined for a target field the values and via selection conditions when these values are allowed.

    • If there are several valid assignments, the first set is used according to priority.

    • An entry without selection condition is also applied according to priority.

    • The possible values can be entered as follows:

      • Several possible values separated with ;:

        • <value1>;<value2>;...

      • The operators < (less than), <= (less than including the value), > (greater than) and >= (greater than including the value).

        • Also >value1;<value2, so e.g. >=10;<1000 this results in all values from 10 to 999

        • So these values are ANDed, all must match

        • More than two values linked like this makes no sense

      • A mixture of values separated with ; and the greater than and less than operators is not supported.

During a status change, the original status is alwaysys used for validation. This ensures that the checks are always consistent until the final update of the status, regardless of the sequence in which the user performs the steps.

 

© ProNovia AG | Imprint | Data Protection