2023-02-07 Acquisitions Meeting notes



  • Aaron Neslin, Ana Ugaz, Ann Crowley, Ann-Marie Breaux, Carol Sterenberg, Corrie Hutchinson, Daniel Huang, Dennis Bridges, Dung-Lan Chen, Dwayne Swigert, Emily Robertson, Jackie Magagnosc, Julia, Julie Brannon, Julie Stauffer, Kathleen Norton, Kimberly Pamplin, Lisa Smith, Lucinda Williams, Marica Masters, Mark Arnold, Martina Schildt, Martina Tumulla, Mary Moran, Heather McMillan, Molly Driscoll, Nancy Pelis, Nina Stellmann, Okay Okonkwo, Peter Breternitz, Peter Sbrzesny, Rhonda Fuhrmann, rmerrell, Robert Heaton, Sabrina Bayer, Sara Colglazier, Scott Perry, Shannon Burke, Steve Selleck, Sven Thomsen, Sylvia Hamann, Victoria Anderson, Winter White, wiljanen


  • Housekeeping -

    Business -

    • Order Version History UAT Overview and Results (by Dennis Bridges)
    • If time permits, discuss Implementers Topics #83 and continues (Molly Driscoll )
      • No.83
        Export transaction list from Finance
        • Finance - Villanova University would like to be able to filter and export transaction details from budgets in the Finance app.
        • What would be some key use cases for extracting this information?
        • Would you need transactions for only 1 budget at a time?
        • What detail from the transaction would you need (i.e. amount, budget ID, Expense class, Description, tags etc.)?

Discussion items

:00Housekeeping Dung-Lan
 :03 Order Version History UAT overview Dennis
  •   Order Version History UAT overview
    • Main points
      • No showstopper defects identified
    • Bugs Identified: 
        • “Created on” seems to be updated for every version
        • Manual checkbox not checked
        • Reason for closure not highlighted
        • Results list not cleared in find instance plugin with “Reset all”
        • Unrecognized fields appear as changed when edit fund
        • Exchange rates cannot be updated on invoice lines with multiple funds.
    • Suggested Enhancements
      • Extend HIT area to make easier to activate a different version
      • Add some description of action taken that resulted in changed fields
        • Need stories that capture this. There is detail about this in the documentation for version history, but no specific user stories. 
      • Display indication at PO level of which POLs have been edited
        • Dennis: Need use cases that support this. What are the specific scenarios where it would be helpful to see this?
          • Kimberly Pamplin: Version History would be helpful for po's with multiple titles, and a title left the package or membership, it would be helpful to see previous versions and what titles were included. 
          • Sara Colglazier: Agree with Kimberly. With a package that has multiple pol's, would be helpful to know which pol was edited. 
          • wiljanen 12:21 PM
            It could just be like the cancelled icon that shows up on a PO with multiple POLs
      • Make “Date updated” a hyperlink to the version history
      • A comment field would be useful to explain to colleagues why changes have been made.


  • Will there be a function to delete old version histories from closed orders?
    • At the moment, no. This needs to be discussed more.
  • Will automatic edits from the system also be included in the version history?
    • Essentially, yes, When you make changes to other records in the system that results in updates to the order that is captured in the version. We do need to identify what was the action that resulted in the change. 

Action items