>

Adding/Editing a Note for Express User

Refer to Product Ideas

Comments

6 comments

Date Votes
  • Cathy Herrick

    I tested in 25.1 and 24.4 QE with and Express User

    1. I could not add a note at all if Add/Change/Delete Events By Event Status Limit was not added to my Role or test User.
    2. When setting Add/Change/Delete Events By Event Status Limit at access level of 30 for my test user in both environments the test user could then only add a note on events with <30 status level and could not add on any events above 30

    I'm not sure what the business case is for having Express Users needing to add notes to events but change nothing else - but maybe they should enter a Pendo request for another access privilege that manages just note entry?

    Richard Marmura  - I think this is working as designed. The application is treating adding a note as editing the Event - I think that sounds like what we would expect, is that correct?

  • Heather Lightsey

    Richard Marmura just checking in to see if you've had a chance to review Cathy's message from last week regarding whether this is WAD or not. Consulting is advising that they believe it should not work this way, and Cathy and I are unsure. If you have a moment to weigh in, it would be greatly appreciated!

  • Cathy Herrick

    Richard Marmura  - are you able to review and confirm whether this the Add/Change/Delete Events By Event Status Limit  privilege is working as designed to prevent Note entry?

  • Seth Halvaksz

    Anthony Costantino do you know if express users can edit a note on an event?

    I looked at Express User functionality, and it just shows “Edit Note” - which makes me think an Express user could edit a note anywhere in the system

  • Anthony Costantino

    Seth Halvaksz yes, Add Note and Edit Note are actions allowed in the Express user type, BUT that's not the question here. The access privilege Add/Change/Delete Events By Event Status Limit does not do a good job explicitly stating what ‘a change to an event’ means in terms of specific Enterprise workflows. Blocking the user from editing Event fields is pretty obvious and expected, but when we enact the privilege, we experience inconsistent behaviors between child subjects to the event. for example, the user can complete work orders, but can't edit service orders, the user can add activities but can't add notes… we need a more explicit definition of what ‘change event’ means for purposes of this privilege.

    Some of us in Services believe that notes should be excluded from this privilege so that add/edit is not blocked by this privilege.

    The common job to be done: there are a class of users who are expected to add operational details to the event but are not permitted to change the business critical or reporting critical fields on the event. These users need to add notes to the event, upload documents, and add/respond to activities but must not change any fields on the event page. This privilege is the closest to achieving the desired results except that it's preventing us from adding notes.

    The work around we've recommended is to stop using the privilege and instead add a protect field restriction on all event fields. The workaround is a lot of one-time setup and causes frustration for an admin when this privilege is sitting there, …taunting us… 

  • Seth Halvaksz

    Anthony Costantino got it. So the question here is what the access privilege “The access privilege Add/Change/Delete Events By Event Status Limit” controls.

    This sounds like a good enhancement to review what this should do.  Should it be consistent and not allow to edit any fields if the event status is below the access privilege?

    Thanks for the suggested workaround for now.

Please sign in to leave a comment.