Discussion Items

5 minHousekeepingAndrea Loigman
  • Notetaker -  
30minWorkflowsMike GorrellCurrent and future plans for the workflows engineSIG members are aware of the state of the workflows engine -

Darcy Branchini Fee/fine tokens for patron notices

Fee/fine tokens for patron noticesWe are starting work on sending manual fee/fine charge and payment notices, so we need to add related fee/fine tokens, such as fee/fine type, fee/fine owner, balance, amount paid, etc. I'd like to have a decision regarding which tokens are needed. As a starting point, rows 57 -76 on this sheet -

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached


e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019


1 Comment

  1. Presentation by Mike Gorell on plans for the workflow engine

    Long term vision: integrate manual and automated functions through the workflow engine

    Requires a message queue implementation for modules and manual to interact

    Short term vision: deploy workflow engine, to-ap for manual workflows only

    Does not require message queue. May be more doable by summer 2020

    Message queue being worked on for data import, may affect what can be accomplished in workflow

    RA does not have a lot of purely manual workflows; most accomplished by reports

    There is some concern by RA that too much redesign will be necessary after 2020 if work arounds to workflow are implemented

    Mike: some alternatives to workflow may not need to be changed, especially if not cross-module

    Implementation of automated/module side of workflow more important to RA and ERM

    RA should document examples of workflow uses

    Priorities will be set for MVP

    Manual fee/fine notice tokens questions from Darcy

    what tokens are needed – review spreadsheet

    Types of notices: notices of new fees/fines are most important; payment receipts only if requested