[UICIRC-70] Settings for patron notice templates Created: 08/Jun/18  Updated: 28/Mar/19  Resolved: 11/Dec/18

Status: Closed
Project: ui-circulation
Components: None
Affects versions: None
Fix versions: 1.4.0

Type: Story Priority: P2
Reporter: Darcy Branchini Assignee: Matt Connolly
Resolution: Done Votes: 0
Labels: demo53, sprint43, sprint44, sprint45, sprint48, sprint49, sprint50, sprint51, sprint52
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1 Patron notices - settings.png    
Issue links:
Blocks
blocks UICIRC-74 Patron notices - email templates Closed
blocks UICIRC-73 Pre-defined (out of the box) patron n... Closed
blocks UICIRC-117 Patron notices - templates for text o... Closed
blocks UICIRC-118 Patron notices - templates for printe... Closed
is blocked by CIRCSTORE-68 endpoint for patron notice templates Closed
is blocked by MODTEMPENG-3 Add a ‘subject’ field to mod-template... Closed
is blocked by MODTEMPENG-4 Unable to create new template Closed
Relates
relates to UICIRC-85 Delete custom patron notice template ... Closed
relates to UICIRC-86 Create, edit and clone patron notice ... Closed
relates to UICIRC-87 Read/view patron notice template Closed
relates to MODTEMPENG-1 Generate a Change Password email Closed
relates to MODTEMPENG-5 Reset a Password Email Template Closed
relates to MODTEMPENG-8 Create a password email template Closed
relates to UICIRC-148 CRUD Partials or snippet templates fo... Draft
relates to UIU-713 Add charge notice and action notice o... Closed
relates to FOLIO-1371 API Design: A Folio module to send an... Closed
relates to UICIRC-106 Single patron notice within a policy Closed
relates to UXPROD-675 CRUD patron notice templates Closed
Sprint:
Development Team: Prokopovych

 Description   

Purpose: Configuration/Settings for patron notices

Context/Stories: As an administrator, I want to setup patron notices, including name, description, active/inactive status and email templates. Generally, notices include availability, courtesy, overdue and/or fee/fine notices as well as notices specific to other workflows, such as claims returned. All notices will be sent via email initially. SMS and Print are OUT OF SCOPE for this release, but these will be developed in a future release.

This issue covers just create, edit and clone for notices, and not full CRUD or the triggering events, conditions and/or scheduling, which will be addressed through patron notice policies and circulation rules.

All notice mockups are available here - https://drive.google.com/drive/folders/1zNDRmeBiK6m1VU6OEU0STPlL7hN-YFxA. Attached mockups are relevant to this story.

Note: wherever an accepted UI pattern already exists, such as the Save button at top right, that should be implemented.


Scenario 1:

  • Given settings > circulation > patron notices
  • Displays
    • List of notice templates pre-defined, such as Courtesy, Overdue and/or Renew Confirmation, and those defined by administrators
    • New button on top right to create a new notice

Mockup(s): 1 Patron notices - settings



 Comments   
Comment by Cate Boerema (Inactive) [ 19/Jul/18 ]

Great to see this story come in! It's a big one. I vote for putting all the pre-formatted notices requirements into UICIRC-73 Closed . You could break this story down further, but if the developers are okay with this big story, I am fine with it.

It would be helpful if you could number the scenarios so people could reference them in comments.

Thanks!

Comment by Khalilah Gambrell [ 23/Jul/18 ]

This implementation could be leveraged to support sending a user a Create/Reset/change password.

Comment by Matt Connolly [ 30/Jul/18 ]

Cate Boerema Darcy Branchini I have some time available, so I can pick this one up if it's ready to go.

Comment by Darcy Branchini [ 30/Jul/18 ]

Matt Connolly - yes, they're ready! I'm happy to see someone pick this up. Please let me know if you have any questions. Also, you might want to connect with Michal Kuklis about his work with the rich text editor for staff slips. He used Quill JS and Mustache. Thank you!

Comment by Cate Boerema (Inactive) [ 06/Nov/18 ]

Matt Connolly and Jakub Skoczen, just checking in on this. It's been in progress for quite some time and this entire feature (not just this story but all of UXPROD-675 Closed ) is targeted for Q4 release (feature freeze in about 4 weeks). Do you have an update?

Comment by Darcy Branchini [ 06/Nov/18 ]

Cate Boerema, Matt Connolly and I were just discussing this. I made a few UI changes to be more inline with Filip's UX patterns. Matt thinks he can have this done within a week or two.

Comment by Cate Boerema (Inactive) [ 07/Nov/18 ]

Thanks for the update, Darcy Branchini and Matt Connolly. The entire feature ( UXPROD-675 Closed ) is targeted for Q4. Given where we are, I think we need to prioritize the stories in that feature to come up with a meaningful package of functionality for Q4.

I think we should really strive to get the settings described in this story plus a basic patron notice CRU(D) workflow complete (similar to the Staff slips CRUD).
I guess that would be UICIRC-86 Closed , UICIRC-87 Closed and UICIRC-74 Closed , Darcy? Could some of these be worked in parallel while Matt works on this one? Michal did staff slips, I think. He could probably take care of some of these pretty quickly.

Comment by Marc Johnson [ 07/Nov/18 ]

(I'm not sure if this is the right place to ask this, but wasn't sure of a better place)

Matt Connolly Is my understanding correct that this work is to use interfaces implemented by mod-template-engine and not mod-circulation-storage?

If so, should we CIRCSTORE-68 Closed as it isn't going to be done (and add any mod-template-engine dependencies where necessary)?

Comment by Matt Connolly [ 07/Nov/18 ]

Hi, Cate Boerema ... I appreciate that the time remaining is limited. I'd like to see how far I can get with the code this week. That will put us in a good position to figure out who can do what at the beginning of next week.

Marc Johnson, you're right; this is based now on mod-template engine, and so CIRCSTORE-68 Closed is redundant at this point.

Comment by Jakub Skoczen [ 29/Nov/18 ]

John Malconian this will require mod-template-engine (template-engine 1.0 interface) included in the snapshot and snapshot-core to operate. Can we get it in?

Comment by Darcy Branchini [ 30/Nov/18 ]

I removed general configuration from this story. It's just a list of defined templates. We'll address formats (such as email, sms and print) allowed and footer in a separate story. Footer will be more generic and instead we'll have templates and template snippets (such as footer, header, and/or signature).

Comment by Darcy Branchini [ 30/Nov/18 ]

Matt Connolly, please use the term "Patron notice templates" as label in settings. We'll also have "Patron notice policies," so I just want it to be clear.

Generated at Thu Feb 08 23:12:09 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.