What is "Diagram Builder" and why is it visible to all users in San Diego?

[klaytonz]

I just updated my Test instance to San Diego and have found a few new navigator items that are visible to all users including those with no roles etc. One item is called "Diagram Builder" and the other is "Usage Tracking Consent". I can not find any reference to these in the SN docs. I know it seems to be standard that Service Now forgets to add roles to new items to the application menu with every release so an admin has to hide them, but now a complete mystery? Is this a contest? 🙂
Thanks for any information on what these are and what is the intent that these are visible to the general public on our system.

oh, I note "San Diego" is not an option on versions for the forum selection.

[klaytonz · Accepted solution]

Looks like I will be hiding these from the menu for now. Per SN support these are new and accessible by design. They did open a problem to review why they are added without roles etc as below:

SOLUTION PROPOSED:
Both "Diagram Builder" and "Flow Diagramming" are introduced in "San Diego". "Diagram Builder" is an internal application which gets installed when "Flow Diagramming" gets installed since it is one of its dependency. Following docs help us to understand the use of flow diagramming :
https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/administer/flow-designer/concep...

Right now the "Diagram Builder" module is accessible for all the users but the components under the module are read-only as this is internal application. This is the expected behavior as OOB. I have created a PRB(PRB1566166) for review from dev to check the visibility of "Diagram Builder" module by all the users.

[Inactive_Use469]

Getting a page is not available when clicking the link.

The disposition we are taking is based on a similar conclusion:

Diagram Builder - Created a new role and group and then removed the OOB snc_internal role from the 'Diagram Builder' application and added a new role to the application so only users in the group can see the application.

Justification: Since ServiceNow has opened this up to 'snc_internal', we don't have a full understanding of the implications of users being able to create diagrams. There is no documentation we can find for this module. As you indicated Diagram Builder" is an internal application that gets installed when "Flow Diagramming" gets installed since it is one of its dependencies and we can see the reference to Flow Designer but not anything specific to this module and its exposure to all users (snc_internal).  Perhaps the PRB will address it. 

Reference:
Flow Designer: https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/flow-designer/concept/flow-designer.html

Dispositions for the other similar applications/modules exposed to 'user' in San Diego (if helpful):

1. Content Taxonomy - Created a new role and group and then remove OOB snc_internal role from the 'Content Taxonomy' application and added a new role to the application so only users in the group can see the application.

Justification: Since ServiceNow has opened this up to 'snc_internal' and we understand 'itil' can see or view the taxonomy, taxonomy nodes, services, and service offerings but notice there are two issues here for us. One regarding performance when an 'itil' user accesses the taxonomy. See below for steps to reproduce. The other re: the 'Edit' button is available. Meaning, users can add/remove services in the related list. This is typically controlled by Admins in a structured way with governance and it seems wide open to any internal user without a full understanding of the impacts.

Reference: https://docs.servicenow.com/bundle/rome-employee-service-management/page/product/employee-center/task/create-taxonomy-content.html

(Steps to reproduce) - Content Taxonomy performance issue:
1) In the TEST environment login as an 'itil' user.
2) Click All,
4) Type Taxonomy in the left application navigator.
5) Click on your 'taxonomy'
6) Click on any of the taxonomy nodes in the related list.
7) Click on any service in the related list.
Note:  We experience a 30-second delay in rendering the service and a similar delay when clicking on the subsequent service offering.

2. Usage Tracking Consent - We see the 'User Experience Analytics is not appliable. Please contact your admin with any questions' under User Experience Analytics or the 'Usage Tracking Consent' application's Enable/Disable Tracking module when logged in as 'itil'.  We plan to keep the tracking setting as is OOB so we can track usage. However, in our instance, we do not grant non-rolled users access to the native UI. They get automatically redirected to the Service Portal. And, starting with the San Diego release we are moving from the Service Portal to Employee Center. In either case, non-rolled users will not see the native UI. Please see attached which shows what Admin sees vs. what 'itil' sees.  We have a case to determine what needs to be changed to configure the 'Enable/Disable' for 'itil' since there is little point to exposing the application/module only for the user to be told to contact an admin.

Justification: Admins can enable/disable but 'itil' users are just told to contact the administrator and it's not clear what property or other configuration setting needs to be added/updated so that 'itil' users also can enable or disable tracking.

Reference: https://docs.servicenow.com/bundle/sandiego-now-intelligence/page/administer/user-exp-analytics/task/user-exp-analytics-user-set.html

3. Targeted Communications - We are updating the path this module points to so it points to /esc (Employee Center) vs. the OOB /sp (Service Portal).

Justification: Since the application and module don't do anything but point to a location where publication could be posted we are leaving this OOB but pointing it to Employee Center instead of Service Portal.

Reference: https://docs.servicenow.com/bundle/quebec-customer-service-management/page/product/customer-service-management/concept/c_TargetedCommunications.html

[Ronald11]

Hello,

Has anyone discovered yet what is the purpose of diagram builder?

[dsaha]

Has anyone found the purpose of Diagram Builder?