Links

Test environment: https://folio-devedev-thunderjet-2nd-diku.ci.folio.org/

Test credentials:  claimtest/claim

Jira feature: 

Feedback form: https://forms.office.com/r/8jQ6irHpKh

Dates: Jan. 21-2728, 2025

Slack channel for UAT questions and discussion: #acquisitions-uat

Required permissions

Related videos

Claiming Setup

Claim setup.mp4

Claiming Overview

Claiming app.mp4

Known Issues

...

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 some sample late pieces have been configured in the system. If you do claim these pieces, when testing is complete, please go to those titles in the Receiving app and reset those pieces to “Late” status (which can be done by editing the piece in the Expected accordion - see below.)

Setup

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. In most real world cases, the receipt date should also be filled in, as this provides the expected date (without which FOLIO doesn’t know whether a piece is actually late.)

   5. 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

      1. “Joe’s Books” has an existing integration for CSV claims downloads

      2. GOBI has an existing integration for EDI claims downloads

   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.

...