BE | Add settings page for Request type tokens

Use case:

As a system administrator in a tenant that uses Reading room circulation requests, I require the ability to set predefined text that can be used in print and email notices. This predefined text will need to change based on the notice type and format. For example a Recall notice would have predefined text for the different types of Staff slips and email templates.

In scope:

• Add a new settings area Circulation -> Requests -> Request type tokens

• New settings store for the values

  • Populate with null values. There is no validation on the form fields

Senarios:

1. Scenario

   1. Login to FOLIO environment, as user with the necessary permissions

   2. Go to the Settings > Circulation > Requests

   3. A new subpage labeled Request type tokens, listed below Request policies displays

2. Scenario

   1. When viewing the new subpage labeled Request type tokens

   2. Then in the third pane the top menu is Request type tokens

3. Scenario

   1. When viewing the third pane,

   2. then a table with 5 columns displays. This table has following headings:

      1. Requests type

      2. Pick slips

      3. Hold slips

      4. Email

      5. Actions

   3. The table has 6 predefined rows:

      1. Hold

      2. Hold reading room circulation in library request (alternatively: persistent request, or repeatable circulation) - TBD

      3. Recall

      4. Recall reading room circulation in library request (alternatively: persistent request, or repeatable circulation) - TBD

      5. Page

      6. Page reading room circulation in library request (alternatively: persistent request, or repeatable circulation) - TBD

4. Scenario

   1. When viewing the Action menu, which is the 5th column

   2. An icon, an edit pen, is displayed

5. Scenario

   1. When clicking on the edit pen for a given request type

   2. Then data can be entered for following values

      1. Pick slip

      2. Hold slip

      3. Email

   3. In the Action column two buttons displays

      1. Cancel

      2. Save

6. Scenario

   1. When done editing and the changes is to be saved

   2. Then click on Save will save the edits

7. Scenario

   1. If regretting the edits and the changes is not to be saved

   2. Then click on Cancel and the edits will not be saved

8. Scenario

   1. When no data is entered (null)

   2. Then a dash will display in detailed view.

Out of scope: permissions

See: UICIRC-1205

New permissions - required for the back end???
1. All (including Settings > Circulation > Request type tokens)
2. View only (including Settings > Circulation > Request type tokens)