Parameters

When you configure a parameter in TIBCO Fulfillment Provisioning Catalog, you are defining how parameters in the datasets of incoming orders are evaluated and processed. A parameter configuration specifies the parameter's type, cardinality, and templating.

For details on how you can construct flows, refer to the TIBCO Fulfillment Provisioning Developer's Guide.

The following table shows the constraints you can define, and the processing that TIBCO Fulfillment Provisioning Catalog performs, for each type.

type

definition includes

TIBCO Fulfillment Provisioning Catalog Verifies

enum

A list of valid values.

That the parameter's value is in this list.

const

A single value.

That the parameter's value matches this value.

long

Minimum and maximum numeric values.

That the parameter's value falls between these limits.

string

A regular expression. (Perl-compatible regular expression or PCRE)

That the parameter satisfies the regular expression.

boolean

-

That the value is any of the following: true/false, yes/no, on/off, 1/0. Case is ignored: NO and no are equivalent.

range

Minimum and maximum alphabetic sort values.

That the parameter's value falls between these limits.

The definition also includes the cardinality of the parameter- how many occurrences may be in the dataset.

TIBCO Fulfillment Provisioning first checks in dataset of product orders to see if the value of the parameter, if present, is kop::VALUE_RETRIEVED (GETDEF). If so it starts a new iteration to retrieve the value from an external system.

For each parameter related to the technical product, through patterns, the following applies:

Case 1 2 3 4 5 6 7 8
present yes no yes no yes no yes no
published yes yes yes yes no no no no
mandatory yes yes no no yes yes no no
TIBCO Fulfillment Provisioning behavior is as follows:

  1. OK: do nothing. TIBCO Fulfillment Provisioning Catalog does not add any pm/value.

  2. If parameter can be retrieved then a new iteration is started. Else, TIBCO Fulfillment Provisioning returns NOK: ERROR: "Parameter <pname> is mandatory".

  3. OK: "do nothing". TIBCO Fulfillment Provisioning Catalog does not add any pm/value.

  4. OK: ERROR: "Parameter <pname> is published but not present".

  5. OK: as the parameter is present TIBCO Fulfillment Provisioning Catalog replaces the value with the one value found in TIBCO Fulfillment Provisioning Catalog configuration.

  6. If parameter can be retrieved then a new iteration is started. Else, TIBCO Fulfillment Provisioning Catalog returns NOK: ERROR: "Parameter <pname> is mandatory.

  7. OK: as the parameter is present TIBCO Fulfillment Provisioning Catalog replaces the value with the one value found in TIBCO Fulfillment Provisioning Catalog configuration

  8. OK: TIBCO Fulfillment Provisioning Catalog adds a new parameter with the value found in TIBCO Fulfillment Provisioning Catalog configuration

Note: present indicates that TIBCO Fulfillment Provisioning Catalog found the same parameter in the incoming dataset of the product order.

Case: 5, 7 and 8: If value is kop::VALUE_RETRIEVED (GETDEF) and parameter is linked to a POF a new iteration is started.

Case: 5, 7 and 8: If value is kop::VALUE_RETRIEVED (GETDEF) and parameter is not linked to a POF, it is an error.

Case: 7 and 8 (parameter is not mandatory): If value is UNDEF, TIBCO Fulfillment Provisioning Catalog will NOT add or enrich the parameter.

State Variable Assignments

NVSet assignment can be performed on the states. On a state, add an action, and specify the following string: 
entry/Assign CES_ASSIGNMENT

Where CES_ASSIGNMENT is one of the following commands:

  • FORMAT:
  • FORMAT_NUMERIC:
  • FORMAT_LIST:

The assignments are executed before onEntry action plugins and before the state is processed by client application (before session layer execution for Work Order Flow and before the work order is launched in Product Order Flow).

There can be multiple assignments in a state. The order of assignments is dictated by the order in the resulting XMI file.