Description

Benefit

• Prevents unnecessarily repeated scans during registrations. speeding up registrations overall.

How to use it

1. In Application.cfg, add the pinnable values within the Order Lines Configuration:

   The following snippet is an example of using pinnable values where the results are shown on the right.

   <page id="ReceiveLines" type="OrderLines" icon="mainmenureceive">
     ...
     <orderLinesConfiguration ...>
       ...
       <pinnableRegistrationValues>
         <pinnableByAi eanAi="10" name="LotNumberImagePurpose" icon="document.png" displayLabel="Lot Number" clearAfterPost="true" />
         <pinnableByFormat format="^(\d{6})$" name="ExpirationDate" icon="calendar.png" displayLabel="Exp. Date" clearAfterPost="false" />
       </pinnableRegistrationValues>
       ...
     </orderLinesConfiguration>
     ...
   </page>

   <pinnableRegistrationValues> - Values that can be applied to all order lines throughout registrations. These values can be enabled by scan and will appear similar to the bin filter. When multiple values have same attributes, only the first one matching the scan is taken into account even if there are other matching pinnable values.

   • <pinnableByAi> - A value that is enabled/pinned when the scan matches specific application identifiers (eanAi).

     • eanAi - Comma separated application identifiers. E.g. "10".

   • <pinnableByFormat> - A value that is enabled/pinned when scanning barcodes that matches a specific regular expression (format).

     • format - Regular expression. E.g. "^(\d{6})$".

   • Common attributes - these attributes can be applied to both <pinnableByAi> and <pinnableByFormat>.

     • name - Fallback if no registration step matches the format. E.g. "LotNumberImagePurpose" for <pinnableByAi> and "ExpirationDate" for <pinnableByFormat>.

     • icon - Image displayed on the left of the view, could be image id or image file name. E.g. "document.png" for <pinnableByAi> and "calendar.png" for <pinnableByFormat>.

     • displayLabel - Optional value prefixing when the pinnable value is shown. E.g. "Lot Number" for <pinnableByAi> and "Exp. Date" for <pinnableByFormat>.

     • clearAfterPost - Determines whether the pinnable registration value should be cleared after success posting, the value is set to "true" by default.

2. Open Order Lines

3. Scan a barcode that matches the pinnable values added in Application.cfg.

   • If the scanned value matches any pinnable value, the matching pinnable value will be displayed similar to bin filter.

4. When entering the registration collector, these pinned values should be automatically applied to the matching steps.

Pinned values that are not used

If there are pinned values that are not used in the registrations, it will be sent as ExtraInfo in the posting. The codesnippet below demonstrates how the request would look like if the pinned value is sent as ExtraInfo.

<request name="PostReceiveOrder" created="" xmlns="">
  <requestData name="PostReceiveOrder">
    <Order backendID="" DeliveryNote="DeliveryNote" modified="" xmlns="">
      <Line lineNumber="">
        <Registration created="" xmlns="">
          ...
          <ExtraInfo>
            <LotNumber>DummyLotNumber-1234</LotNumber> 
          </ExtraInfo>
        </Registration>
      </Line>
    </Order>
  </requestData>
</request>

The pinned values are removed by

• The user using the "X"-icon on the right of the control in Order Lines page.

  • Once the pinned values are removed the scanned values will no longer be automatically applied to the registrations.

• The user is posting the registrations

  • If the attribute clearAfterPost is set to true: the user have finished the registrations and posted, the pins will automatically be cleared.