Description:

To define the behavior for the Request anonymization settings page.

Purpose:

As a FOLIO administrator I want to be able to configure if and when closed requests are automatically anonymized

As a FOLIO staff member I want to be able to view the configuration for if and when closed requests are automatically anonymized.

Scenarios

Scenario 1:

• Given a user with a role assigned that includes the "UI-Circulation Settings Request Anonymization" view capability set logged in to FOLIO

• When the user navigates to Settings > Circulation > Request anonymization

• Then the Request anonymization pane opens

• and the current request anonymization configuration is displayed

• and the configuration fields are disabled

• and the "Save" button does not display

Scenario 2:

• Given a user with a role assigned that includes the "UI-Circulation Settings Request Anonymization" edit capability set logged in to FOLIO

• When the user navigates to Settings > Circulation > Request anonymization

• Then the current request anonymization configuration is displayed

  • and the configuration fields are enabled

  • and the "Save" button is displayed but disabled

Scenario 3:

• Given a user with a role assigned that includes the "UI-Circulation Settings Request Anonymization" edit capability set, on the Settings > Circulation > Request anonymization page

• When the configuration is changed

• Then the "Save" button is enabled

Scenario 4:

• Given a user on the Settings > Circulation > Request anonymization page and a change has been made to the current configuration

• When the user selects "Save"

• Then the new configuration is saved and the "Save" button is disabled

Scenario 5:

• Given a user on the Settings > Circulation > Request anonymization page and a change has been made to the current configuration

• When the user navigates away from the page

• Then a confirmation modal appears

  • Titled "Are you sure?"

  • With the message: "There are unsaved changes."

  • With a secondary option on the left "Close without saving"

  • With a primary option on the right "Keep editing"

Scenario 6:

• Given a user has made changes to the configuration, attempted to navigate away from the page, and the unsaved changes modal is displayed

• When the user selects "Keep editing"

• Then the modal closes and the user remains on the same page

Scenario 7

• Given a user has made changes to the configuration, attempted to navigate away from the page, and the unsaved changes modal is displayed

• When the user selects "Close without saving"

• Then the changes are not saved and the user is brought to the selected page.