Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
customfield_11100 21344
-
EPAM-Veg Sprint 8
-
5
-
Vega
Description
Context
Notice policies (UICIRC-98) may contain one to many notices. Each notice has a set of possible fields and some are dependent on other fields' values.
Mockups attached, see Notice options for form field dependencies.
Scenario 1
Given a new notice within a notice policy
Allow library staff (FOLIO administrator) to define one notice
Display
- Notice count at top left
- Delete icon (trash can) at top right. If clicked, delete notice.
- Possible fields (nothing selected by default and no placeholder text):
- Template on first line
- Required select with options populated from patron notice template names with respective category for section (i.e., Loan, Fee/fine, Request)
- via on first line (plain text)
- Format on first line
- Required select with options populated from patron notice templates general settings > format, possible options include:
- Email is the only option for first release; other options will be developed at a later date.
- Required select with options populated from patron notice templates general settings > format, possible options include:
- Frequency on first line
- Required select with options:
- One time
- Recurring
- Required select with options:
- Send Event or Starting Send Event on second line
- Required select with options:
- Upon/At
- Before
- After
- Required select with options:
- Due date/time
- Overdue
- Renewed
- If Before or After is selected (above)
- by (plain text)
- Required number input (1 through 100 are valid numbers) and placeholder of 1 (NOT select)
- Required select with options:
- Minute(s)
- Hour(s)
- Day(s)
- Week(s)
- Month(s)
- Year(s)
- If Recurring is selected (above)
- Send Every on third line
- Required number input (1 through 100 are valid numbers) and placeholder of 1 (NOT select)
- Required select with options:
- Minute(s)
- Hour(s)
- Day(s)
- Week(s)
- Month(s)
- Year(s)
- Send Every on third line
- Required select with options:
- Send in real-time
- Checkbox
- Template on first line
—
User Story 1
Send a courtesy notice one time before overdue by 3 days. It can be sent via the format defined in the user record and in batch.
Options:
- Template: Courtesy Notice 1
- Format: Default
- Frequency: One time
- Send Event: Before Overdue by 3 Days
- Send in real-time: Not checked
User Story 2
Send an overdue notice one time upon/at overdue. It can be sent via the format defined in the user record and in real-time (immediately).
Options:
- Template: Courtesy Notice 1
- Format: Default
- Frequency: One time
- Send Event: Upon/At Overdue
- Send in real-time: Checked
User Story 3
Send an overdue notice after overdue by 5 minutes and then subsequently every 10 minutes. It can be sent via the format defined in the user record and in real-time.
Options:
- Template: Courtesy Notice 1
- Format: Default
- Frequency: Recurring
- Starting Send Event: After Overdue by 5 Minutes
- Send Every: 10 Minutes
- Send in real-time: Checked
TestRail: Results
Attachments
Issue Links
- is blocked by
-
UICIRC-86 Create, edit and clone patron notice templates
-
- Closed
-
- relates to
-
UICIRC-70 Settings for patron notice templates
-
- Closed
-
-
CIRCSTORE-100 Backend - Request-related notices added to a notice policy
-
- Closed
-
-
UICIRC-98 New/edit notice policy
-
- Closed
-
-
UICIRC-108 View notice policy
-
- Closed
-
-
UICIRC-157 Frontend: Request-related notices added to a notice policy
-
- Closed
-
-
UICIRC-167 Settings - list of notice policies
-
- Closed
-
-
UICIRC-198 Add toggle for user initiated v. time based events to notices
-
- Closed
-