Modeling of the Required Characteristics in the Fulfillment Catalog
As per the requirement of the amendment use case, some or all of the following characteristics are required to be available in the product model published to TIBCO Order Management. The modeling of these characteristics and relating them with the required products, needs to be done in the TIBCO® Fulfillment Catalog at the design time. For more information about modeling, see the following procedure:
Note:
This section covers just the high level modeling steps specific to the characteristics required for amendments. Refer the TIBCO® Fulfillment Catalog documentation for details.
- Create the following records in the CHARACTERISTIC repository:
EPMR_ACTION_PROVIDE
EPMR_ACTION_CEASE
EPMR_ACTION_UPDATE
EPMR_ACTION_WITHDRAW
COMPENSATE_PROVIDE
COMPENSATE_CEASE
COMPENSATE_UPDATE
- For more granular EPMR actions based on the plan item statuses, the user can add additional characteristics mentioned below in generic format. Note that these characteristics are used only in case of the new and improved user-defined field modification functionality. Refer the New Characteristics subsection in OrderLine user-defined field change.
EPMR_ACTION_<<action>>_UDF_CHANGE_<<Plan Item Status>>
. For example,EPMR_ACTION_PROVIDE_UDF_CHANGE_SUSPENDED
.
- Create the Characteristic relationship between the records in the
PRODUCT
repository and one or moreEPMR_ACTION_*
records in theCHARACTERISTIC
repository mentioned in point 1 and 2 above. The logically valid value for the RelationshipValue attributes in all these Characteristic relationships can be one of the four EPMR actions -COMPENSATE
,RESTART
,COMPENSATE_RESTART
, orIGNORE
. Refer the Execution Plan Modification Rules (EPMR) topic for the significance of these four actions. For example, the technical product Router can have a Characteristic relationship withEPMR_ACTION_PROVIDE
characteristic, with the value of RelationshipValue attribute asCOMPENSATE_RESTART
. - Create the Characteristic relationship between the records in the PRODUCT repository and one or more
COMPENSATE_*
records in theCHARACTERISTIC
repository mentioned in point 1 above. The logically valid value for the RelationshipValue attributes in all these Characteristic relationships must be the ID of the plan fragment record that is required to be run as the compensation task for the corresponding action. For example, the technical product Router can have a Characteristic relationship withCOMPENSATE_PROVIDE
characteristic, with the value of the RelationshipValue attribute as the planFragmentIDRouter_Cancel
.