Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Acquisition units no longer restrict edit create or delete actions from action menu

Description

Overview: When using acquisition units only the view restriction is enforced for user that are not members of the acquisitions unit.

NOTE: This happens in orders, invoices and finance

Steps to Reproduce:

  1. Log into some FOLIO environment as User X

  2. Create an acquisition unit that restricts edit create and delete

  3. Assign your user to it

  4. Create a record

  5. Remove your user from the acquisitions unit

  6. go back to order view and click actions menu

Expected Results: Edit and delete DO NOT appear in the actions menu no matter what the status of the record

Actual Results: Edit and delete display in actions menu. When trying to save the edited record the system will not allow because user does not belong to acq unit. When confirming delete the system will not allow because user does not belong to acq unit

Additional Information:
URL:
Interested parties:

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges April 23, 2021 at 8:27 PM

 this seems to be working very well. I'm closing this story and have duplicated versions of it for orders, invoices and organizations as ideally this will be consistent behavior in all acquisitions apps. thanks!

Mikita Siadykh April 20, 2021 at 12:53 PM

hi
tested on testing env, please review

Dennis Bridges April 19, 2021 at 2:23 PM

Thanks  If "disable" is the established pattern it makes sense to follow that. I agree that It would not be a great user experience to have an empty action menu.

Mikita Siadykh April 19, 2021 at 8:18 AM
Edited

hi
should we hide actions or disable? according to https://ux.folio.org/docs/guidelines/ux-patterns/hiding-vs-disabling-elements-ux-pattern/ looks like we should disable them, additionally with Hide approach dropdown menu will be empty when button Actions is interactive (it works for case when user doesn't have permissions) - so IMO it's better to disable rather than hide - or in case of hide we should decide how to deal with cases when no actions are available (for me sounds like a separate story as we already have such cases)

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Thunderjet

Parent

Fix versions

Release

R2 2021

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 23, 2021 at 10:03 PM
Updated June 16, 2021 at 10:20 PM
Resolved April 23, 2021 at 8:27 PM
TestRail: Cases
TestRail: Runs