Future State Planning & Commit

Designer provides unique capabilities to perform future state planning without changing data in ServiceNow.

The future state elements and relationships can be "committed" manually or workflow triggered into the ServiceNow platform.

It is also possible to initiate other workflows and processes e.g. provisioning, procurement, or change processes during the commit.

Future & Current State Elements

Current State Elements (committed) are items populated in the ServiceNow repository. They have a SysID and are unique entries e.g. Business Application ABC in the cmdb_bus_application table.

Future State Elements (not committed) are shapes with a defined table, but are not existing within the ServiceNow repository yet. They are stored temporarily within the Designer environment and the Diagram and need to be committed into the ServiceNow repository.

Future State Elements are not shared across Diagrams

Future State Elements are only available within the Diagram and not shared across other Diagrams. So they are not searchable in the Repository Browser.

Distinguishing Future & Current State Elements

Clicking on a shape will show overlay symbols. A Future State Element has only the Hyperlink overlay symbol. A Current State Element has five overlay symbols.

Designer_Current_vs._Future_State_Element

Additionally, the Future & Current Elements and Relationships are shown in the Diagram Content widget in the Right-hand Panel.

Designer_Diagram_Content

Editing Shape & Relationship Data

Editing Shape (Element) Data

Select a shape (element) and press CTRL+M, or right-click on the shape and select Edit Data from the context menu to see the Shape Data form. Alternatively you can use the Data Panel on the right-hand panel. 

designer_shape_data

A – Name of the table / class the selected shape belongs to. The system will ignore shapes which have no table selected. A selected table with an empty element field will be recognized as a not committed element.

B – Name of the element instance in ServiceNow. If the field is empty, the element is not existing yet and needs to be committed to create the instance in ServiceNow. A selected table with an empty element field will be recognized as a not committed element. In case an element is selected here, the system will recognize the shape as a committed element.

C – Name of the Element which will be displayed in the diagram. This can differ from the real elements name in ServiceNow to make the diagram better readable.

D – User notes made during the diagramming process to share with peers which may be helpful during the review and approval process of the diagram.

E – The expected start date can be used for scenario planning purposes to indicate the target implementation date of an element.

F – The expected stop date can be used for scenario planning purposes to indicate the target stop date of an element.

G – The tooltip text shown when hovering the mouse on the shape. By default it is the table / class name.

H – Link to the element form.

I – Unique ServiceNow SysID of the element instance.

Future State Elements do not change ServiceNow data until committed

Designer supports storing any fields value temporarily for future state elements (not committed).

Editing Relationship Data

Select a relationship and press CTRL+M, or right-click on the relationship and select Edit Data from the context menu to see the Relationship Data form. Alternatively you can use the Data Panel on the right-hand panel. 

designer_relationship_dataA – Type of the relationship. Depends on the table / class of the start and end shapes the relationship is connected to (direction sensitive). The type is empty, if the relationship is not connected correctly, or has no suggested relationships defined.

Starting with V3.3 the first relationship is auto-selected when a relationship is created between 2 shapes with assigned table. You can change the order for Relationship Definitions if you want to set another relationship as the primary one for auto-select. 

B – Name of the Relationship which will be displayed in the diagram. This can differ from the real relationship name in ServiceNow to make the diagram better readable.

C – User notes made during the diagramming process to share with peers which may be helpful during the review and approval process of the diagram.

D – The expected start date can be used for scenario planning purposes to indicate the target implementation date of a relationship.

E – The expected stop date can be used for scenario planning purposes to indicate the target stop date of a relationship.

F – The tooltip text shown when hovering the mouse on the relationship. By default it is suggested relationship name.

G – Unique ServiceNow SysID of the relationship instance.

Only relationships with a selected type are considered as committed / not committed in the content browser.

Future State Relationships do not change ServiceNow data until committed

Designer supports storing any relationship fields value temporarily for future state relationships (not committed).

Committing Elements & Relationships

Creating Future State Elements & Relationships in ServiceNow through Designer.

Designer Commit Role Required

Committing Elements & Relationships are restricted to the role x_inpgh_des.commit by default. Please assign the appropriate right to users to provide them the rights to commit elements.

Designer provides a seamless feature to combine current and future state data within one Diagram. Future state data can be "committed" into the ServiceNow repository.

Prerequisites

Committing Elements & Relationships require the following configuration in place (to be performed by ServiceNow and Designer Admin):

  1. Having Class Definitions & Application Cross-Scope Privileges in place for the target tables.
  2. Associating a shape with a table with activated CREATE Cross-Scope Privileges.
  3. Setting Application Settings on Target Table to allow scoped applications with "Can Create" option.

Auto commit after final approval

The proposed approach is to activate the "Auto commit after final approval" within the Global Settings page. This will ensure, that all Future State Elements & Relationships will be automatically committed with the final approval step automatically.

Designer_Global_Settings_Auto_Commit

Committing through the Diagrams Form

In some cases, it makes sense to allow a selected group of key users to commit manually Elements & Relationships without an approval of the Diagram.

Navigate to the Diagram Form through the Diagrams application menu and select the Diagram:

Designer_Commit

A — The Commit button is only visible for users being part of the Designer Commit Group. Clicking this button will commit all the selected items.

B — Click to select all committable Elements & Relationships. Current State items will be ignored.

C — You can select/unselect individual items on demand.

D — Click on the columns to change sorting.

E — Search option within the Content area.

F — Designer distinguishes between Future & Current State, and Duplicate items. Committing duplicate Elements & Relationships is possible and to be configured in the Global Settings.

Commit Result Popup

After clicking the "Commit" button a popup window will show the results, if the commit process was successfully. For Elements & Relationships where the CREATE option on the table is not allowed error messages can appear.

Designer_Commit_Result

Editing the Diagram

Once the Element(s)/Relationship(s) are committed, click on the Edit button to open the Diagram in the Designer.

Designer_Commit_Edit

During the loading process Designer will compare the changes happened to the Diagram and will highlight newly committed Elements & Relationships, and if any Current State Elements & Relationships have been deleted. All changes are highlighted with the red dotted lines.

Confirming Changes

The popup information with the changes will appear every time until the Diagram is saved (CTRL+S).

 

Duplicate Handling

Please note, that Duplicate Elements have been updated and connected to the real Element automatically! They will disappear from the list as duplicates, as Designer has recognized them and related the shape to the real Element.