Pick + Pack Service Request
***************************

Pick + Pack Service Request is used when both picking and packing has to be done
by the GreyMatter system.

The :gm:data:`serviceRequest.type` parameter for a Pick+Pack request should be
set to ``PICK``. The system decides which "``PICK``-type" requests to send for
packing based on system configuration.

Create a PickPack Request
=========================

.. http:post:: /api-gateway/sr-service/platform-srms/service-request

   To create a new pick+pack service request, a :ref:`Service Request Object`
   should be sent in a HTTP POST request to the above endpoint. The newly
   created or modified object will be returned in the response if the request is
   successful.

   Pick+Pack requests should have the :gm:data:`serviceRequest.type` parameter
   set to ``PICK``.

   :reqheader Content-Type: the request's content-type has to be passed in this
                            header
   :reqheader Accept: the response content type depends on
                      :mailheader:`Accept` header
   :reqheader Authorization: OAuth token to authenticate
   :statuscode 200: No error
   :statuscode 400: Bad data

   .. container:: toggle

      .. container:: header

         **Example request**:

      .. sourcecode:: http

         POST /api-gateway/sr-service/platform-srms/service-request HTTP/1.1
         Host: example.com
         Content-Type: application/json
         Accept: application/json, text/javascript

      .. literalinclude:: pick_pack/create_pick_pack_request.json
         :language: JSON

   .. container:: toggle

      .. container:: header

         **Example Response**:

      .. sourcecode:: http

         HTTP/1.1 200 OK
         Content-Type: application/json;charset=UTF-8

      .. literalinclude:: pick_pack/create_pick_pack_request.json
         :language: JSON

PickPack Request Notifications
==============================

In the pick+pack complete notifications, the :gm:data:`serviceRequest.type`
parameter will be set to ``PACK``.

Pick Pack Complete Notification
-------------------------------

A notification is generated when the whole packing is completed for a Pick+Pack
Service Request.

If there are exceptions raised during the packing process, it's information is
present in the complete notification.

**Examples:**

.. container:: toggle

   .. container:: header

      Complete without exceptions

   .. literalinclude:: pick_pack/pick_pack_complete_notification.json
      :language: JSON

.. container:: toggle

   .. container:: header

      Complete with damaged

   .. literalinclude:: pick_pack/pick_pack_damaged_notification.json
      :language: JSON

.. container:: toggle

   .. container:: header

      Complete with unscannable

   .. literalinclude:: pick_pack/pick_pack_unscannable_notification.json
      :language: JSON

.. container:: toggle

   .. container:: header

      Complete with unexpected items

   .. literalinclude:: pick_pack/pick_pack_unexpected_notification.json
      :language: JSON

.. container:: toggle

   .. container:: header

      Complete with missing items

   .. literalinclude:: pick_pack/pick_pack_missing_notification.json
      :language: JSON

.. container:: toggle

   .. container:: header

      Complete with split box

   .. literalinclude:: pick_pack/pick_pack_split_box_notification.json
      :language: JSON

Pick Pack End Notification
--------------------------

.. warning:: This notification does not follow the generic notification object
             format.

.. container:: toggle

   .. container:: header

      Show/Hide

   .. literalinclude:: pick_pack/pick_pack_end_notification.json
      :language: JSON