They then walked through the high-level workflow that will allow a user to create an order:
Select order type (one time, ongoing)
Select inventory type (container, instance, none)
Select PO line format (physical, electronic, mixed)
Once these steps are complete, the app will present the user with a blank order. The fields will be customized based on the user's selections.
Discussion:
Several people stressed the importance of making sure that it will be possible to move an order from one inventory record to another (container or instance) after creation.
A question came up about whether an inventory record will be able to have more than one order attached. This will be possible. An inventory record has no limit on the number of orders attached. Each order behaves independently of the others.
Initial feedback was positive, people felt like this approach helps solve some of the issues that came up in the last call related to the conflation of inventory type and PO line format.
We still need to see how Orders interacts with ERM. One outstanding question is whether you will need a container record and an ERM record or just the ERM record.
Anne-Marie stressed the importance of making sure there is a single place to search for previously purchased resources, regardless of whether they have inventory records or not. This will probably be Codex.
Dennis plans to walk through the order creation process for each of the five use cases. We will aim to review one use case at next week's meeting.
The outcome of this discussion was a recommendation that future UATs include a briefing on what functionality is not yet completed, so testers will know what to focus on.