Ordering functionality that FOLIO needs to stay competitive
(UXPROD-3440)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Morning Glory (R2 2022) | Parent: | Ordering functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Done | Votes: | 0 |
| Labels: | acq-morningglory-candidate, acquisitions, cf_candidate, chalmers, chalmers_debut_followup, crossapp, crossrmapps, orders | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Ordering functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 9 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 92 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
Purpose:Other modules in the FOLIO system will need to generate POs or start the process of creating a PO in order to streamline user experience and relate important information from other modules to purchase orders. High-Level Requirements:Define the required JSON payload for triggering the creation of a purchase order and subsequent purchase order lines Charlotte Whitt and Dennis Bridges This is feedback from Chalmers. Being able to create POLs from Inventory Instances is high priority for them. Please review and determine next step (finalize into a story, mark as will not implement, need more info, delete, etc.). The label chalmers_debut_followup helps us keep these issues all findable as a group. Additional use cases:Additional use case that supports this is creating an order from OCLC records as first they need to be imported to inventory. Approach:https://folio-org.atlassian.net/wiki/display/FOLIJET/Create+POL+automatically+from+Instance https://miro.com/app/board/uXjVO2exdM4=/?share_link_id=318071390532 NOTES |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 04/Sep/19 ] |
|
updated the feature to be focused on Inventory only. Charlotte Whitt this is an Inventory feature, but related to orders. It's a priority for Chalmers. Should we reassign the feature to you? Thanks! |
| Comment by Ann-Marie Breaux (Inactive) [ 11/Sep/19 ] |
|
Important feature for Chalmers; they may increase its rank Current workflow, without this option:
Preferred workflow:
|
| Comment by Ann-Marie Breaux (Inactive) [ 13/Sep/19 ] |
|
Dennis Bridges Charlotte Whitt Is there any way to consider increasing the rank of this feature? I'm not sure if the work would be done in Inventory or Orders or both. At RM SIG today, Chalmers just reiterated how helpful this would be for their workflow. |
| Comment by Marie Widigson [ 16/Sep/19 ] |
|
Thank you Ann-Marie Breaux These parts is very important for us and would make ordering much more streamlined and efficient: Please note that we still want to use the templates and that the instance information should be autopopulated when starting in inventory. |
| Comment by Dennis Bridges [ 16/Sep/19 ] |
|
Ann-Marie Breaux and Charlotte Whitt From the perspective of orders this is certainly possible. Thus I believe the work simply needs to be done for UIIN. I suppose any team could work on it, so the question for Charlotte Whitt is when would you be able to get to this work, or where does it fall in the feature priority? As the feature is assigned to me at the moment and the work is assigned to you this is likely to get lost. Perhaps we should reassign the feature or the related issues to help prioritize it? |
| Comment by Ann-Marie Breaux (Inactive) [ 17/Sep/19 ] |
|
Hi Dennis Bridges and Charlotte Whitt I agree with Dennis that this is one of the features that will end up falling through the cracks. The fact that the PO (Dennis) ranked it lower than the calculated rank, plus it's not po-mvp or cap-mvp reflects that. This is definitely important to Chalmers. Is there a way to get this reviewed? I'll add it to the list that MM SIG (and maybe RM SIG) are reviewing this week. |
| Comment by Ian Ibbotson (Use this one) [ 17/Sep/19 ] |
|
Hey Ann-Marie Breaux Dennis Bridges - I was watching this issue with some interest and mentioned it to Kirstin Kemner-Heek who suggested it might be an interesting topic for an App Interaction meeting - and that Martina.Schildt might be interested in reviewing the issue to see if there are any wider lessons that can be learned about the way we bridge the gap between functionally separate, but related apps. |
| Comment by Martina.Schildt [ 17/Sep/19 ] |
|
Hi Ian Ibbotson (Use this one) Dennis Bridges Ann-Marie Breaux Charlotte Whitt, I will review and reserve an App Interaction call for that topic. |
| Comment by Ann-Marie Breaux (Inactive) [ 17/Sep/19 ] |
|
Ian Ibbotson (Use this one) Martina.Schildt That's fine by me, so long as this Inventory-Orders related issue does not get delayed for that discussion. We need this in place regardless of what may happen between other apps and the Order app. Thanks, |
| Comment by Dennis Bridges [ 17/Sep/19 ] |
|
Note that the calculated total rank is increasing here as more folks become aware of this issue and see its value. I think it is a good candidate for the app interaction call as it presents the same problem as creating orders via agreements. All we can do now is send the user in to the order app or load the order form inside a modal. Once that has been decided it could be implemented. However, if the priority is not out ranking other areas of development perhaps this can wait until there is a more user friendly way to implement the cross app record creation which I believe John is actively working on spikes for? |
| Comment by Ann-Marie Breaux (Inactive) [ 18/Sep/19 ] |
|
Dennis Bridges Charlotte Whitt Calculated rank is increasing, but it's not PO-MVP or CAP-MVP for Orders or Inventory, so it's still likely to fall through the cracks. Chalmers needs it for Inventory before Agreements, so we definitely need to stay focused on Inventory, even if we discuss other apps. Thanks, |
| Comment by Charlotte Whitt [ 18/Sep/19 ] |
My stories are dev. ready (and have been since April 2019): |
| Comment by Dennis Bridges [ 18/Sep/19 ] |
|
Excellent Charlotte Whitt are you able to pull them into an upcoming sprint? |
| Comment by Dennis Bridges [ 27/Sep/19 ] |
|
The consensus in the app interaction group today was that plugins are not likely the best way to implement this functionality. As a result it will be blocked by technical investigation outlined in
cc: John Coburn Charlotte Whitt Ann-Marie Breaux Khalilah Gambrell |
| Comment by Ann-Marie Breaux (Inactive) [ 23/Feb/21 ] |
|
Hi Dennis Bridges and Charlotte Whitt, I had a session with Alabama about order workflow today, and they were delighted to see the new OCLC single record import that will be in Iris. Now all they need is an action on the instance that would allow them to create a PO and POL. Alabama has this ranked as P1. If there's any chance of doing this sooner rather than later, that would be awesome. Thank you! |
| Comment by Charlotte Whitt [ 24/Feb/21 ] |
|
+ 1 Alabama Totally agree: "... sooner rather than later, that would be awesome!" - most Summer 2021 Libraries will second that. |
| Comment by Dennis Bridges [ 27/Feb/21 ] |
|
Ann-Marie Breaux With 1 week to release there is no way for Thunderjet to pull this work for R1. If the core team is not picking this up we will once again weigh it against all other features that are currently scheduled for R2. thx! cc: Charlotte Whitt |
| Comment by Julie Brannon [ 31/Oct/22 ] |
|
@Dennis Re documentation: This feature is listed on the Nolana release notes, but it looks like it was already released in Morning Glory so we included the new Action in the Instance action menu "+ New order" in the Morning Glory release on docs.folio.org. Is there additional functionality in this Jira that needs to be documented for Nolana? Thanks? |
| Comment by Dennis Bridges [ 31/Oct/22 ] |
|
Thanks Julie Brannon, no this was already released with MG and at some point the fixed version was changed but it shouldn't have been. |