2018-08-10 Meeting notes
Date
Attendees
- Michael Arthur
- Anya
- Kristen Wilson
- Dennis Bridges
- Peter McCracken
- Martina Schildt
- Charlotte Whitt
- Bethany Greene (Deactivated)
- Kirstin Kemner-Heek
- John Ballestro
Discussion items
Item | Who | Notes |
---|---|---|
Minute Taker? | Eric Hartnett||
Announcements/Updates Product Council: Ongoing discussion of workflow support, moving to Technical Council for better resourcing estimate | Mike Gorell did a rough estimate of the work/time needed to implement workflows. He is now going to take it to the Technical Council for further discussion. Comunda, an open source work engine, is being investigated. Hard-coded value lists - is it worth spending the time on this. Looking for ways to make this more flexible. There is a controlled vocabulary that can help. It's going to be taken back to the POs. | |
Batch Loading Update | Developer group has been assigned (name.., in Ukraine). Began working about 4 weeks ago starting with password management. They will then work on internal infrastructure and then UI. Filip and small group have been working on UI sketches. | |
Acquisitions Items
| Nothing new on vendors. PO Order Types changeable? Use case, mistakenly added wrong order type, or decision made to change the order type. It's being discussed because it could have other ramifications. Having this not changeable seemed like the simplest, short-term solution. Certain fields only appear depending on the type selected. Once you've opened an order, you can work on the order, add PO Lines. Once you've opened a PO, it cannot be deleted - it has to be closed. Once an order has been submitted, it cannot be editable. Which fields will be editable is still up in the air - the business logic is still being developed. What other fields need to be editable? Funds, vendors. Basically, we need to be able to correct mistakes. Add in ability to delete if there hasn't been any activity on the record. Acquisitions units - being able to have separate units (law, medical, etc., departments) within the same tenant. Be able to identify certain POs or funds as accessible to certain groups of people. Should provide a way to filter permissions. Ex. this PO/fund is associated with X acquisition unit. Assignment can be done in the User app. A user can be associate with more than one acquisition unit. Acquisitions units can be created and details are listed in the Finance app and users can be assigned to the unit in the Finance app as well. In order for an acquisition unit to be able to do anything, it must be assigned to a fund or funds. At the moment a unit cannot be assigned at the ledger level - it's at the fund level to provide more flexibility. Is there a way to bulk add users to an acquisition unit? May be related to batch loading of users. How do acquisitions units tie to ERM? Kirstin will take it to the ERM subgroup. Material types list - this list does not drive functionality. Comment that this list should be editable from the beginning because it depends on the institution's needs. It's currently probably too long and the values change periodically. This is going to be investigated further. |