Notifications

26 views

Description

Certain users (who are usually non-admin) are not able to see the journal field selector on the Activity Stream flyout window even if they have read/write access to those journal fields.

The journal fields themselves are visible and are writeable on the actual record form.

 

Steps to Reproduce

 

1) Create the following two ACLs:

a. Operation : read
Admin overrides: checked
Name : Incident.Additional comments
Requires role : itil

Conditions : None

b. Operation : write
Admin overrides: checked
Name : Incident | Additional comments
Requires role : itil

Conditions : Active is true

2) Make sure that there are no conflicting similar ACLs by deactivating or deleting all other ACLS other than the two that were recently created for incident.comments.

3)  Now open any existing non-closed incident record.


4) Right click on the form header. Configure -> Form Layout.


5) Remove the 'Activities (filtered)' from the Notes section. Save the changes.


6) As an admin, go to an incident and click on the activity stream button on the top right hand side of the header. A flyout window pops open to show the activity stream.


7) The admin user is able to read/write to the Additional comments and Work notes fields.


8) Impersonate 'ITIL User'.


9) Open an existing incident and click on the activity stream button on the top right hand side of the header. A flyout window pops open to show the activity stream.


10) The ITIL user can see that only Work notes field is writable where in actuality the ITIL user has access to read and write on the 'Additional Comments' field.

This can be confirmed (that the ITIL user does indeed have read/write access to the Additional Comments field) if the 'Activities (filtered)' is added back to the Notes section.

Workaround

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

 


Related Problem: PRB1312770

Seen In

There is no data to report.

Intended Fix Version

Madrid

Fixed In

London Patch 5

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-01-21 09:24:04
Published:2019-01-21