User interface for automated flows within a cloud based developmental platform
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
exact text as granted — not AI-modifiedWhat is claimed is:
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.
2 . 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.
3 . The system of claim 1 , wherein the one or more metrics comprise a start time metric, a duration, or both.
4 . 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.
5 . 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.
6 . 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.
7 . 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.
8 . 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.
9 . 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.
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.
11 . 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.
12 . 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.
13 . 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.
14 . 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.
15 . 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.
16 . 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.
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.
18 . 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.
19 . 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.
20 . 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.Join the waitlist — get patent alerts
Track US2018324051A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.