Staff Slips (UXPROD-19)

[UXPROD-3199] Make all fields available as tokens for staff slip templates Created: 29/Jul/21  Updated: 23/Feb/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Staff Slips

Type: New Feature Priority: TBD
Reporter: Darcy Branchini Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: staff_slips, staff_slips_tokens
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Staff Slips
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

From RA SIG meeting notes on 7/19: Another option is to make all data available to users to be a token. Would require changing the UI – users would need to indicate what kind of token you want, for example, inventory, user, or loan, otherwise it would be too many things being thrown at the user all at once. Responsibility for describing available data could reside with module owners, which is how permissions work now.

Current situation or problem: New fields are added to modules/components through new feature development, such as preferred name or user's (requester's) department. Also, more generally, users may decide a token that's not currently available to templates would be helpful to their workflow. At this point in time, they need to request new tokens as a new feature. This feature would allow them access to any field in any relevant module which is a more sustainable longer-term solution.

In scope

  • UI design for selecting a token (perhaps start with type, inventory, loan, etc., then be provided token options for that type)
  • BE, if required, to support new UI design for selecting a token
  • Build out BE to allow for descriptions of each field and whether it's available to FE as a token (if this isn't already done)

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