Servicenow, Inc.

Harry Thomas Nelson

Rebecca Anita Dias

Jacob Samuel Burman

Alberto Alvarado Jimenez

Joshua Timothy Nerius

Venkata Kiran Kumar Koya

Christopher Maloy

Russell Samuel Sarbora

Juell Chase Solaegui

Qian Zhang

Christopher Tucker

Nicholas Michael Stark

David Tamjidi

Sunil Kumar

Nikhil Prashant Bendre

Michel Abou Samah

Stuart Dean Swope

Khosrow Jian Motamedi

Matthew Stoddart

Nikhil Dvivedi

Robert Peter-Paul Recatto

Reynaldo Hernandez

Christen Mitchell

Reema Shah

Craig Brian Santa Ruiz

Derek Gregory Stainer

Carl Solis

Pierce Edward Courtney

Deepti Suryakant Bhogle

Mark Brennan

Alejandro Moreno Ruiz

Gabrielle Gordon

Alberto Alvarado Jiminez

Michael Samah

Chong Lee Khoo

Nick Stark

Brian P Bimschleger

Jennifer M Lyons

Andrew K Fry

Enrico Cruz

Jingfei Chen

Juell Solaegui

A specification of one or more steps of a digital workflow specified using a graphical user interface is received. An indication of a program transfer control step in the digital workflow to return to a previously specified step in the digital workflow is received. The already specified specification of the one or more steps of the digital workflow is analyzed to determine one or more constraints of the program transfer control step. Based on the determined one or more constraints of the program transfer control step, a configuration of the program transfer control step in the digital workflow is restricted in the graphical user interface.

Transfer control step for digital workflows

A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programing interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

System and method for workflow application programming interfaces (APIS)

Non-volatile memory may contain definitions of: (i) a plurality of message queue implementations respectively associated with different queue behaviors, the different queue behaviors specified by corresponding sets of modes, and (ii) an application programming interface (API) through which applications can access one or more message queues. One or more processors may be configured to: create a message queue of a particular message queue type, supported by a corresponding message queue implementation, by specifying a set of modes corresponding to a queue behavior; receive, from a producing application and by way of the API, one or more messages for the message queue; store the one or more messages in a data structure associated with the message queue; receive, from a consuming application and by way of the API, a request to read from the message queue; and provide a message from the message queue to the consuming application.

Message queue architecture and interface for a multi-application platform

Executing and managing flow plans by performing at least the following: receiving an indication to initiate a task flow including a plurality of discrete but related operations at a customer instance environment of a cloud-based computing platform; obtaining a definition of the task flow identifying run-time requirements for each of the plurality of operations; determining a first execution environment for the first of the plurality of operations; initiating execution of the first operation in the first execution environment; and determining the proper execution environment for subsequent operations of the task flow until all operations of the task flow are complete. Factors, such as look-ahead optimization, environmental operational capabilities, access and security requirements, current load, future load, etc. may be considered when determining the proper execution environment for a given operation. Operations may be executed in environments hosted in the public cloud or in environments present in a dedicated private network.

Management instrumentation and discovery (MID) server support for executing automated flows within a cloud based system

Persistent storage may contain metadata actions and integration actions related to a remote service, wherein the remote service includes a remote service application programming interface (API) that provides access to structured data, and a metadata API that provides access to a schema of the structured data. Processors may be configured to: (i) generate and provide, for metadata action design graphical user interfaces (GUIs), options for specification of a metadata action, where the metadata action defines a metadata query to the metadata API, rules for parsing the schema, and a normalized format for the structured data; (ii) generate and provide, for integration action design GUIs, options for specification of an integration action, where the integration action defines a structured data query to the remote service API and an indication that the metadata action is to be used to represent a result of the structured data query in the normalized format.

Workflow support for dynamic action output

A first workflow item grouping container and a second workflow item grouping container are a part of a collection of workflow item grouping containers organizing an end-to-end multi-process workflow solution. An identification and execution condition of the first workflow item grouping container and an identification and execution condition of the second workflow item grouping container are received. A specification of one or more workflow items belonging to the first workflow item grouping container and a specification of one or more workflow items belonging to the second workflow item grouping container are received. Each of the one or more workflow items belonging to the first and second workflow item grouping containers has an individually configurable execution condition and corresponds to a different individual activity of the end-to-end multi-process workflow solution.

Multi-process workflow designer

A wait duration for a timer action element of a design-time flow plan is set. The wait duration being set relative to a specified data point of a table associated with the design-time flow plan. An operation associated with the timer action element executes at run-time to pause a flow for the wait duration prior to execution of an operation associated with an action element that is set to execute subsequent to the timer action element in the design-time flow plan. A specified timeframe for the timer action element of the design-time flow plan is set. The operation associated with the timer action element to pause the flow for the specified wait duration executes at run-time during the set specified timeframe. A natural language annotation associated with the timer action element of the design-time flow plan is displayed. The annotation presents the set duration and timeframe in a human-readable format.

Wait a duration timer action and flow engine for building automated flows within a cloud based development platform

A user modifiable user interface representation of a first workflow item grouping container and a second workflow item grouping container are provided. The first and second item grouping containers are part of a collection of workflow item grouping containers organizing a design of an end-to-end multi-process workflow solution. An interactive user interface representation of a first workflow item belonging to the first workflow item grouping container and a second workflow item belonging to the second workflow item grouping container are provided. The first and second workflow items correspond to different individual activities of the end-to-end multi-process workflow solution. A user is able to interact with the interactive user interface representation of the first workflow item to modify a workflow property of the first workflow item and to interact with the interactive user interface representation of the second workflow item to modify a workflow property of the second workflow item.

Multi-process workflow designer user interface

Persistent storage may contain a definition of an application programming interface (API) of a remote service, where the API provides access to input information stored at the remote service. One or more processors may be configured to: (i) provide, for display on an action design graphical user interface (GUI), a first menu that allows selection of a first set of the input information to be dynamically retrieved from the API during design of a workflow; (ii) provide, for display on the action design GUI, a second menu that allows selection of a second set of the input information to be dynamically retrieved from the API during design of the workflow; and (iii) provide for display, on the action design GUI, options for specifying the API, how to remotely access the API, and how to parse data received from the API.

Workflow support for dynamic action input

A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to configure, via the data stream handler system, the data stream object to transmit a request to an external system. The server is additionally configured to configure, via the data stream handler system, the data stream object to capture a response from the external system, wherein the response comprises a paginated data set, a data stream, or a combination thereof, wherein creating the data stream object, configuring the data stream object to transmit the request, configuring the data stream object to capture the response, or a combination thereof, comprises using visual controls in lieu of entering text for a computer program.

System and method for large volume data streaming as a service

Creating and executing flow plans by performing at least the following: obtaining a run-time flow plan that comprises a trigger, a first operation, and a second operation, wherein the first operation precedes the second operation within the run-time flow plan and one or more input values of the second operation are linked to the first operation, determining whether one or more conditions of the trigger are met, execute the first operation based at least on the determination that the one or more conditions of the trigger are met, monitoring whether the second operation is ready for execution based at least on a determination that the one or more input values of a second action operation are ready, and executing the second action operation when the second action operation has been identified as ready for execution.

Flow engine for building automated flows within a cloud based developmental platform

A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programming interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

Creating, executing, and managing flow plans by performing at least the following: presenting on a display an action instance associated with a flow plan within an action designer user interface, wherein the action designer user interface comprises: an action outline component that includes an input graphical element, one or more step instance graphical element, and an action graphical element, wherein one of the graphical elements is highlighted within the action outline component; and an action window adjacent to the action outline component, wherein the action window comprises one or more input fields that dynamically change based on a user selection of one of the graphical elements within the action outline component, and present a window to select from a list of pre-existing step instance types for a step instance.

User interface for automated flows within a cloud based developmental platform

A system may involve persistent storage defining primitive data types and compound data types, where the compound data types include objects and arrays, where the objects contain sets of elements that have various primitive data types, compound data types, or both, and where the arrays contain sets of elements that all have one particular primitive data type or compound data type. The system may also involve one or more processors configured to provide a representation of a graphical user interface for designing a hierarchy of elements, each of the elements therein having a data type that is either a primitive data type or a compound data type, where elements in the hierarchy are associated with data type change controls, and where object elements in the hierarchy are: (i) associated with child element controls, and (ii) represented as collapsible menu items that can either display or hide their child elements.

Graphical user interfaces for defining complex data objects

Growing community of inventors

San Diego, CA, United States of America

Harry Thomas Nelson