TIBCO Fulfillment Subscriber Inventory Services

The TIBCO Fulfillment Subscriber Inventory services are the set of services which are related to entities associated with the item or party objects. These services allow you to get information about these entities and perform other operations.

• Common Elements
  Most of the web service request or response bodies for the application contain the following elements and can be referred to in the following tables. The rest of the elements for each web service are detailed with the respective topics.
• Lock Notification
  The lock notifications are published on dedicated topics to indicate lock timeout, removal, or grant.
• Authenticate
  The authenticate operation is used to fetch an authentication token from the application. The token has to be sent back as a header in all other operations.
• Start Batch
  You can use the start batch operation to start batches.
• completeBatch
  You can use the complete batch operation to complete or rollback batches.
• Create
  Create makes one-to-many new entities in TIBCO Fulfillment Subscriber Inventory. For items only, you can also use this operation to create orders, associated characteristics, and relationships, as well as linking to other items; this is item specific, and cannot be done for parties. Referential integrity is assured for item to item relationships.
• Delete
  Delete performs a logical delete of one-to-many items in TIBCO Fulfillment Subscriber Inventory. The records are not physically deleted at this time. Instead a flag is set on the items, and they will only be physically deleted when the Purge operation is invoked. Records can also be undeleted using the Update operation.
• Purge
  The purge performs a physical delete of entities in the application that have previously been marked for deletion through the delete operation.
• Get
  Get retrieves items from TIBCO Fulfillment Subscriber Inventory by a primary key. The amount of information included in the returned data can be controlled by setting flags on the request message. For performance reasons, it is best practice to retrieve as little information as required as part of a Get operation invocation.
• Update
  Update modifies one-to-many existing items in the application. The operation specifies a delta of what to change on the current entity rather than a full snapshot. Only fields that need updating need to be included on the request.
• Query
  The query operation retrieves entities from the application by a list of filtering criteria. The amount of information included in the returned data can be controlled by setting flags on the request message. For performance reasons, it is best practice to retrieve as little information as required as part of a query operation invocation.