Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira feature: 

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4274

...

Routing Overview

Known Issues

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryissuetype = Bug AND issuekey in linkedissues("UXPROD-4274")
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Instructions

The feedback form generally follows the steps listed below. We suggest filling out the form as you work your way through the test.

...

Please note that this test is set up for ongoing orders, but can also be tested with firm monographic orders, if desired.

  1. In the Orders app, create an order and order line:

    1. The order should be ongoing (recommended, not required)

    2. Ordering and receiving quantity should be independent (recommended, not required.)

    3. Claim active should be checked/true (this is required.)

    4. When complete, open the order.

  2. In the Organizations app, verify that the selected vendor for the order has an associated claiming integration

    1. Select the organization

    2. Click on "integrations" in the third pane

    3. Expand the "integration details" accordion

    4. If at least one integration exists verify that it is a claiming integration

    5. If no integrations exist, click "add integration" and create a claiming integration:

      1. Make sure integration type is "claiming"

      2. Selecting transmission method "ftp" without a valid ftp server will generate an error when the job is created, but the claim file will be downloadable.

      3. The simplest check will be transmission method "download" and file format "CSV" (recommended).

      4. If using "download" and "CSV", EDI configuration and FTP details can be ignored.

  3. In the Receiving app, create receiving pieces - OR - use the Serials app to generate receiving pieces

    1. The number of pieces doesn't matter, but multiple pieces are recommended for this test.

    2. Once pieces have been created and are "expected", click each piece to enter its detail screen

    3. Use the drop-down next to "Save & close" and select "Mark late"

  4. You may want to repeat steps 1-3 so you have multiple orders from multiple vendors.

Claiming

  1. Open the Claiming app

  2. Verify that all pieces marked "late" appear on the screen

  3. If desired, experiment with column sorting (Expected date, Chronology and Enumeration are all sortable.)

  4. If desired, select Actions → Group by vendor. This allows you to view all late pieces from a single vendor together.

  5. If desired, experiment with search & filter options.

  6. Actions menu

    1. Selecting one or more pieces will allow you to act on those selected pieces

    2. Send claim will create claims based on the vendor integration parameters (as described in Setup)

    3. Delay claim will allow you to defer claims to a future date. That piece will not appear in the Claiming display until that date OR you manually change the status of the piece.

    4. Unreceivable will mark selected pieces as unreceivable.

  7. Experiment with common claiming actions as you would encounter in your ordinary work.

Export Manager

  1. When you have finished sending claims, open Export manager