Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-4172] Build custom purchase order templates Created: 05/Apr/23  Updated: 30/Nov/23  Resolved: 08/Aug/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Won't Do Votes: 0
Labels: LC-priority2, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Ordering functionality that FOLIO needs to stay competitive
Front End Estimate: XXL < 30 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: Some libraries transmitting purchase orders via print or pdf need the ability to create customized purchase order print templates.

In scope

  • Enable the library to select the purchase order layout, including the order and position of specific PO fields
  • Enable the library to assign static text to the purchase order template, in library-defined locations and positions
  • Allow libraries to save multiple layouts as templates
  • Allow libraries to associate specific templates with specific organizations (as default templates for that organization)

Out of scope

Use case(s)

A library places orders via creating purchase orders as a pdf. This library deals with multiple international vendors with differing requirements. The library wants the ability to create custom templates for these vendors to simplify the ordering process.

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Joseph Reimers [ 08/Aug/23 ]

Requirements were clarified and current functionality is adequate for building templates without further development.

Generated at Fri Feb 09 00:37:51 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.