Please enable JavaScript.
Coggle requires JavaScript to display documents.
SNOW (Workflow (When to use (Approval, SLA, Task creation, Event…
SNOW
Workflow
-
-
-
-
Context
-
-
-
Regardless of the number of changes to a workflow definition, contexts continue to run using the workflow definition at the time of launch. In addition to loading a workflow, contexts also know which record the workflow was launched for.
-
Service Portal
?
A portal is a ServiceNow user interface (UI), built using the Service Portal framework, which provides an alternative user experience to the standard UI.
It is an intuitive way for users to interact with the underlying Now Platform using a minimum number of clicks from any device: desktop, tablet, or smartphone
can access any platform
Selected records from important tables, such as all tasks assigned to the user
Metrics, reports, and analytics
-
-
-
-
-
Portal Anatomy
Pages
?
Each portal is made up of one or more pages. Pages are not unique to a portal and can be used in as many portals as needed. A portal applies theming, a header, a footer, and some additional metadata to a page, allowing reuse without changes to a page's definition
Containers
Portal pages are organized by containers. Containers create the page layout by organizing pages into sections. Containers are divided into rows. Containers typically contain a single row but can have multiple rows. Each row has a specified number of columns. Each row can contain a different number of columns
-
Widget
Widgets define the content for a portal. The default portal container shown is one row which contains three columns. Although in this example, each column contains two widgets, each column can contain any number of widgets.
-
-
Page Editor
provides a tree view of every element on a portal page. Using the tree, developers can open the record for any element on the page to examine and change element configuration
Service Portal Framework
?
The Service Portal framework is a set of tools, APIs, AngularJS services and directives, and components used to create portals. The Service Portal Framework helps developers and non‑technical administrators create attractive and engaging user experiences which drive employee adoption of critical enterprise applications
-
-
Security
Access Controls.
-
-
-
-
-
To or Not to
-
*
Grant access to all fields where there is no field-specific Access Control
-
-
Flow Designer
Terminology
-
Subflow tabs: Subflow icon displays on subflow tabs Configure subflow inputs, outputs, and actions.
Action tabs: Action icon displays on action tabs Configure action inputs, outputs, and steps
Flow execution tabs: Flow execution icon displays on flow execution tabs View details captured from the execution of a flow.
Actions
When triggered, the flow progresses through a series of actions. ServiceNow provides a core group of actions to use in flows
-
-
-
-
-
-
Ask for Approvals Action
Flow Designer can create approvals for any record in ServiceNow. Use the Ask For Approvals action to request approvals
-
Flow Designer roles
-
flow_operator: view flow execution details, dashboards, and logs
-
-
-
-
Decision
Decision Table
A Decision Table maps decision inputs to decisions. Decision inputs are configuration fields that specify the information needed to make a decision
The Decision Table is associated with an Answer table. Decisions are mapped to records in the Answer table. Answer table records are the branches for Make a decision flow logic.
-
-
Flow Exection
A flow execution is created when a flow executes.A flow execution loads the flow configuration at execution time. Regardless of changes to a flow configuration, flow executions continue to run using the flow configuration at the time of execution
-
-
-
Runtime Access Tracking
-
None
No authorization required for application scripts to access resources from other applications as long as the other application allows it. No record is created in the Application Cross-Scope Access table.
-
Tracking
Allows application scripts to access resources from other applications. A record for the access is automatically inserted in the Application Cross-Scope Access table with a Status value of Allowed. This is the default setting
-
-
Enforcing
Allows application scripts to access resources from other applications only after an admin authorizes the access. A record is automatically added to the Application Cross-Scope Access table with a Status value of Requested
-