Create and link PO/POL from Agreement line (UXPROD-1753)

[UXPROD-1679] Create Purchase Order Line (POL) from an Agreement Line Created: 30/Apr/19  Updated: 16/Jul/19

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Create and link PO/POL from Agreement line

Type: Sub-task Priority: P3
Reporter: Owen Stephens Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: agreements, erm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by ERM-239 Link existing Purchase Order Line (PO... Closed

 Description   

Value for user:
By creating a POL from an Agreement line a library can record, view and track information about the acquisition of the items within the agreement including

  • how much the resource costs/will cost
  • how much has been spent on the resource
  • when the last invoice was paid

Examples:
An Agreement consists of a subscription to a package of content and some individual titles. The library needs to track orders and payments for both the package and the specific titles. They create POLs for the relevant agreement lines to track this

Roles and restrictions:

  • The option create a POL should only display for users with the rights to create POLs in the Orders app

Workflow / UI expectations:
From Agreements (preview pane) -> Finances - agreement lines each agreement line should be displayed with an option to "Add POL"
Clicking "Add POL" will prompt the user to select an existing PO and then start the process of adding a new POL to that POL in the Orders App, with some parts of the POL form pre-populated based on information from the Agreement line/resource

Business rules & constraints:

  • When creating a POL all usual requirements and constraints for creating a POL should be followed. This is already defined in the Orders app and should be controlled there
  • Once a POL is linked to an Agreement line it can only be removed by deleting the POL in the Orders app

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