# US 2018/0324051 A1 · User interface for automated flows within a cloud based developmental platform > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0324051 A1 - Document ID: US20180324051A1 - Status: Published application - Kind: A1 - Application number: 15/814,967 - Filed: 2017-11-16 - Published: 2018-11-08 - Earliest claimed: 2017-05-05 - Applicants: ServiceNow, Inc. - Inventors: Rebecca Dias; Mark Brennan; Nicholas Stark - Web page: https://patentgrep.com/patent/US20180324051A1 ## CPC - G06F 8/34: Graphical or visual programming - G06F 3/0482: Interaction with lists of selectable items, e.g. menus - G06F 3/04847: Interaction techniques to control parameter settings, e.g. interaction with sliders or dials - G06F 9/54: Interprogram communication - G06Q 10/00: Administration; Management - G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations - H04L 41/22: comprising specially adapted graphical user interfaces [GUI] - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Creating, executing, and managing flow plans by performing at least the following: presenting on a display an operational view of an executing flow plan within an operational view user interface that includes: a flow plan graphical outline associated with the executing flow plan, wherein the flow plan graphical outline comprises a trigger instance graphical element for a trigger instance, at least one action instance graphical element for at least one action instance, and at least one step instance graphical element for at least one step instance; one or more state indicators adjacent to the flow plan graphical outline that provide an overall state of the trigger instance, the action instance, and the step instance; and one or more metrics relating to executing the trigger instance, the action instance, and the step instance. ## Claims ### Claim 1 A system comprising: a non-transitory memory; and one or more hardware processors configured to read instructions from the non-transitory memory to the one or more hardware processors to: present on a display an operational view of an executing flow plan within an operational view user interface that comprises: a flow plan graphical outline associated with the executing flow plan, wherein the flow plan graphical outline comprises a trigger instance graphical element for a trigger instance, at least one action instance graphical element for at least one action instance, and at least one step instance graphical element for at least one step instance; one or more state indicators adjacent to the flow plan graphical outline that provide an overall state of the trigger instance, the at least one action instance, and the at least one step instance; and one or more metrics relating to executing the trigger instance, the at least one action instance, and the at least one step instance. ### Claim 2 (depends on 1) The system of claim 1, wherein the one or state indicators represent whether the trigger instance, the at least one action instance, the at least one step instance are currently being executed, have not been executed, or completed execution. ### Claim 3 (depends on 1) The system of claim 1, wherein the one or more metrics comprise a start time metric, a duration, or both. ### Claim 4 (depends on 1) The system of claim 1, wherein the instructions further cause the one or more hardware processors to: receive a user input selecting the at least one action instance graphical element; and generate, in response to the user input, an expansion window in the flow plan graphical outline for the at least one action instance graphical element, wherein the expansion window provides runtime information of the at least one action instance. ### Claim 5 (depends on 4) The system of claim 4, wherein the expansion window is displayed within the operational view user interface without switching to another window outside the operational view user interface. ### Claim 6 (depends on 4) The system of claim 4, wherein the expansion window includes one or more links that allows a user to select and view a window with detail run time information. ### Claim 7 (depends on 1) The system of claim 1, wherein the executing flow plan that the operational view user interface displays corresponds to a published snapshot version of the executing flow plan, and wherein the published snapshot version of the executing flow plan differs from a current version flow plan. ### Claim 8 (depends on 1) The system of claim 1, wherein the instructions further cause the one or more hardware processors to present the executing flow plan within the operational view user interface while modifying a current version of the executing flow plan in another interface. ### Claim 9 (depends on 1) The system of claim 1, wherein the instructions further cause the one or more hardware processors to: receive a user input selecting the at least one step instance graphical element; and generate, in response to the user input, an expansion window in the flow plan graphical outline that for the at least one step instance graphical element, wherein the expansion window provides runtime information of the at least one action instance. ### Claim 10 A method comprising: presenting on a display an operational view of an executing flow plan within an operational view user interface that comprises: a flow plan graphical outline associated with the executing flow plan, wherein the flow plan graphical outline comprises a trigger instance graphical element for a trigger instance, at least one action instance graphical element for at least one action instance, and at least one step instance graphical element for at least one step instance; one or more state indicators adjacent to the flow plan graphical outline that provide an overall state of the trigger instance, the at least one action instance, and the at least one step instance; and one or more metrics relating to executing the trigger instance, the at least one action instance, and the at least one step instance. ### Claim 11 (depends on 10) The method of claim 10, further comprising: receiving a user input selecting the at least one action instance graphical element; and generating, in response to the user input, an expansion window in the flow plan graphical outline for the at least one action instance graphical element, wherein the expansion window provides runtime information of the at least one action instance. ### Claim 12 (depends on 11) The method of claim 11, wherein the expansion window is displayed within the operational view user interface without switching to another window outside the operational view user interface. ### Claim 13 (depends on 11) The method of claim 11, wherein the expansion window includes one or more links that allows a user to select and view a window with detail run time information. ### Claim 14 (depends on 10) The method of claim 10, further comprising presenting the executing flow plan within the operational view user interface while modifying a current version of the executing flow plan in another interface. ### Claim 15 (depends on 10) The method of claim 10, wherein the one or state indicators represent whether the trigger instance, the at least one action instance, the at least one step instance are currently being executed, have not been executed, or completed execution. ### Claim 16 (depends on 10) The method of claim 10, further comprising receiving a user input selecting the at least one step instance graphical element; and generating, in response to the user input, an expansion window in the flow plan graphical outline for the at least one step instance graphical element, wherein the expansion window provides runtime information of the at least one action instance. ### Claim 17 A system comprising: a non-transitory memory; and one or more hardware processors configured to read instructions from the non-transitory memory to the one or more hardware processors to: present on a display an operational view of a first version of a flow plan within an operational view user interface that comprises: a flow plan graphical outline associated with the first version of the flow plan, wherein the flow plan graphical outline comprises a trigger instance graphical element for a trigger instance, at least one action instance graphical element for at least one action instance, and at least one step instance graphical element for at least one step instance; and one or more state indicators adjacent to the flow plan graphical outline that provide an overall state of the trigger instance, the at least one action instance, and the at least one step instance; and present on the display a current version of the flow plan within a second user interface while the first version of the flow plan executes. ### Claim 18 (depends on 17) The system of claim 17, wherein the operational view user interface further comprises one or more metrics relating to executing the trigger instance, the at least one action instance, and the at least one step instance. ### Claim 19 (depends on 17) The system of claim 17, wherein the instructions further cause the one or more hardware processors to: receive a user input selecting the at least one action instance graphical element; and generate, in response to the user input, an expansion window in the flow plan graphical outline for the at least one action instance graphical element, wherein the expansion window provides runtime information of the at least one action instance. ### Claim 20 (depends on 19) The system of claim 19, wherein the expansion window includes one or more links that allows a user to select and view a window with detail run time information.