8.9 Rating and Feedback Management
BPP provides the list of entities that can be rated in its system to the BAP
Contains any additional or extended inputs required to confirm an order. This is typically a Form Input. Sometimes, selection of catalog elements is not enough for the Provider Platform to confirm an order. For example, to confirm a flight ticket, the airline requires details of the passengers along with information on baggage, identity, in addition to the class of ticket. Similarly, a logistics company may require details on the nature of shipment in order to confirm the shipping. A recruiting firm may require additional details on the applicant in order to confirm a job application. For all such purposes, the can choose to send this object attached to any object in the catalog that is required to be sent while placing the order. This object can typically be sent at an item level or at the order level. The item level XInput will override the Order level XInput as it indicates a special requirement of information for that particular item. Hence the Consumer Interface must render a separate form for the Item and another form at the Order level before confirmation.
Indicates whether the form data is mandatorily required by the Provider Platform to confirm the order.
Form object
Contains any additional or extended inputs required to confirm an order. This is typically a Form Input. Sometimes, selection of catalog elements is not enough for the Provider Platform to confirm an order. For example, to confirm a flight ticket, the airline requires details of the passengers along with information on baggage, identity, in addition to the class of ticket. Similarly, a logistics company may require details on the nature of shipment in order to confirm the shipping. A recruiting firm may require additional details on the applicant in order to confirm a job application. For all such purposes, the can choose to send this object attached to any object in the catalog that is required to be sent while placing the order. This object can typically be sent at an item level or at the order level. The item level XInput will override the Order level XInput as it indicates a special requirement of information for that particular item. Hence the Consumer Interface must render a separate form for the Item and another form at the Order level before confirmation.
Indicates whether the form data is mandatorily required by the Provider Platform to confirm the order.
Form object
create a form
ID of the form
Successful closure of a chat session
Describes how a an order will be rendered/fulfilled to the end-customer
Unique reference ID to the fulfillment of an order
A code that describes the mode of fulfillment. This is typically set when there are multiple ways an order can be fulfilled. For example, a retail order can be fulfilled either via store pickup or a home delivery. Similarly, a medical consultation can be provided either in-person or via tele-consultation. The network policy must publish standard fulfillment type codes for the different modes of fulfillment.
Whether the fulfillment can be rated or not
Rating value given to the object. This can be a single value or can also contain an inequality operator like gt, gte, lt, lte. This can also contain an inequality expression containing logical operators like && and ||.
Indicates whether the fulfillment allows tracking
falseThe physical path taken by the agent that can be rendered on a map. The allowed format of this property can be set by the network.
Successful closure of a chat session
Update fulfillment state for an order
Unique reference ID to the fulfillment of an order
Describes the state of fulfillment
ID of entity which changed the state
Successful closure of a chat session
Describes how a an order will be rendered/fulfilled to the end-customer
Unique reference ID to the fulfillment of an order
A code that describes the mode of fulfillment. This is typically set when there are multiple ways an order can be fulfilled. For example, a retail order can be fulfilled either via store pickup or a home delivery. Similarly, a medical consultation can be provided either in-person or via tele-consultation. The network policy must publish standard fulfillment type codes for the different modes of fulfillment.
Whether the fulfillment can be rated or not
Rating value given to the object. This can be a single value or can also contain an inequality operator like gt, gte, lt, lte. This can also contain an inequality expression containing logical operators like && and ||.
Indicates whether the fulfillment allows tracking
falseThe physical path taken by the agent that can be rendered on a map. The allowed format of this property can be set by the network.
Successful closure of a chat session
Cancel the fulfillment for an order
Human-readable ID of the order. This is generated at the Provider Platform layer. The Provider Platform can either generate order id within its system or forward the order ID created at the provider level.
Successful closure of a chat session
Describes how a an order will be rendered/fulfilled to the end-customer
Unique reference ID to the fulfillment of an order
A code that describes the mode of fulfillment. This is typically set when there are multiple ways an order can be fulfilled. For example, a retail order can be fulfilled either via store pickup or a home delivery. Similarly, a medical consultation can be provided either in-person or via tele-consultation. The network policy must publish standard fulfillment type codes for the different modes of fulfillment.
Whether the fulfillment can be rated or not
Rating value given to the object. This can be a single value or can also contain an inequality operator like gt, gte, lt, lte. This can also contain an inequality expression containing logical operators like && and ||.
Indicates whether the fulfillment allows tracking
falseThe physical path taken by the agent that can be rendered on a map. The allowed format of this property can be set by the network.
Successful closure of a chat session
BPP provides the list of entities that can be rated in its system to the BAP
Describes the rating of an entity
Category of the entity being rated
Id of the object being rated
Rating value given to the object. This can be a single value or can also contain an inequality operator like gt, gte, lt, lte. This can also contain an inequality expression containing logical operators like && and ||.
Form object
Contains any additional or extended inputs required to confirm an order. This is typically a Form Input. Sometimes, selection of catalog elements is not enough for the Provider Platform to confirm an order. For example, to confirm a flight ticket, the airline requires details of the passengers along with information on baggage, identity, in addition to the class of ticket. Similarly, a logistics company may require details on the nature of shipment in order to confirm the shipping. A recruiting firm may require additional details on the applicant in order to confirm a job application. For all such purposes, the can choose to send this object attached to any object in the catalog that is required to be sent while placing the order. This object can typically be sent at an item level or at the order level. The item level XInput will override the Order level XInput as it indicates a special requirement of information for that particular item. Hence the Consumer Interface must render a separate form for the Item and another form at the Order level before confirmation.
Indicates whether the form data is mandatorily required by the Provider Platform to confirm the order.
Form object
Last updated
Was this helpful?