Hamur Labs Integrations - rettersoft/rbs-docs GitHub Wiki

Interacting With "Shipment Journey" Process

In RBS, orders might have more than one shipments and delivery life-cycle lives on those shipment records instead of their order. Projects might have one or more processes to manage delivery life-cycles. For every shipment, a SHIPMENT_JOURNEY process will be fired and you can interact with that process by following steps in its definition.

As Hamur Labs, you have a service called "hammurlabs.wms" in RBS ecosystem. Via your service, you're allowed to send some actions, as well as receiving some actions and responding to them.

Status Update: Packaging Started

When packaging started, you should fire following event.

Action Name: hamurlabs.wms.event.PACKAGING_STARTED

You don't have to send anything as payload but in headers you should provide following attributes. You will receive these values in headers when you receive process events.

x-rbs-processid: SHIPMENT_JOURNEY
x-rbs-processexecutionid: EXECUTION_ID

Status Update: Packaging Completed

When packaging completed, you should fire following event.

Action Name: hamurlabs.wms.event.WAITING_FOR_CARGO

Headers:

x-rbs-processid: SHIPMENT_JOURNEY
x-rbs-processexecutionid: EXECUTION_ID

Body:

{
    "boxCount": number
}