Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2327

Display Simple Order Alerts

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XL < 15 days
    • Development Team:
      Thunderjet
    • Report Functional Area(s):
      Resource Management
    • Calculated Total Rank:
      22
    • Kiwi Planning Points (DO NOT CHANGE):
      1
    • PO Rank:
      80
    • PO Ranking Note:
      Hide
      Alerts will be essential to the management of orders in FOLIO. Particularly in the absence of other workflow tools that may help users keep track of where an order is in its lifecycle and the things the user is required to do to bring that order to maturity. Alerts will also help complete fiscal year rollover, claiming and other order functionality.
      Show
      Alerts will be essential to the management of orders in FOLIO. Particularly in the absence of other workflow tools that may help users keep track of where an order is in its lifecycle and the things the user is required to do to bring that order to maturity. Alerts will also help complete fiscal year rollover, claiming and other order functionality.
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R4
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: hbz (TBD):
      R4
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Overview: The system can performs actions in orders on behalf of users or applications. When a user is not performing the actions themself they may need to be made aware of what has taken place, or not taken place. Order alerts will make users aware of issues that have arisen with orders as a result of indirect actions made by the user and scheduled actions performed by the system.

      Problem: User has placed an order with a vendor successfully, but something has come up since that order was opened. If the user has no way of identifying orders for which actions need to be taken, order processing, receiving and invoicing may be negatively impacted.

      Use cases:

      • User has indicated that pieces will arrive on a certain day. That day comes and goes but the user is so busy with other orders they forget to follow up. This may go unoticed until a patron comments or an invoice arrives.
      • Orders are created via a third party integration when ordered in a vendor system. That order is created in folio but can not be opened on account of a configuration change made in folio. User may never notice this order was left unopened and forget to follow up.
      • During fiscal year rollover some orders were not able to be encumbered because the funds the were allocated to have insufficient funds in the coming fiscal year. These orders will remain unencumbered unless a user intervenes and if they do not the library may need to cancel order.
      • User has requested a purchase and would an acquisitions person to be notified.
      • User is importing a number of orders from an external system. Post import if the orders are identified as duplicates they should be flagged and user should be notified.

        TestRail: Results

          Attachments

            Activity

              People

              Assignee:
              dennisbridges Dennis Bridges
              Reporter:
              dennisbridges Dennis Bridges
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  TestRail: Runs

                    TestRail: Cases