Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2893

...

  • Orders are still occasionally printed and sent via mail to a vendor
  • Orders are often Saved as PDF and sent to vendors via email that cannot accommodate other forms of communication?
  • Potentially during the claiming workflow users will want to print/save to PDF and communicate order information to Vendor once again

Voucher/invoices - Note this will require additional FE dev work as we can not leverage existing order export logic

  • Vouchers at some institutions are printed for a physical archived
  • ?

Combined Workflow - TBD

When viewing a record like an order record, user has a print option in the actions menu

Print layout will include a set number of fields from the Order and order line(s)

Image Added

Print settings modal is displayed and user can choose what fields they would like to be included from the PO and POL for printing based on the full print layout

Image Added

User clicks print and the and the system gather order data to populate the HTML template with selected data points

The populated template is sent to browser and triggers the browser print function. (Note this is not a mock of the real layout)

All selected orders and order lines appear in one large document that can be printed or saved to PDF

Image Added Possible layout ->Image Added


Record is printed or saved to PDF. No log or history of printing is captured

Possible Workflow 1 - TBD

When viewing a record like an order record, user has a print option in the actions menu

...

Record is printed or saved to PDF. No log or history of printing is captured

Possible Workflow 2 - TBD

User executes a search for order records

...