Servicenow, Inc.

Jacob Samuel Burman

Harry Thomas Nelson

Alberto Alvarado Jimenez

Rebecca Anita Dias

Joshua Timothy Nerius

Christopher Maloy

Michel Abou Samah

Juell Chase Solaegui

Venkata Kiran Kumar Koya

Russell Samuel Sarbora

Nikhil Dvivedi

Yaron Guez

Pierce Edward Courtney

Denis George Angleton

Deepti Suryakant Bhogle

Reynaldo Hernandez

Sharon Elizabeth Carmichael Ehlert

Chris Widlowski

Kylin Follenweider

Meredith Van Lier

Douglas Bradley

Craig Brian Santa Ruiz

Suzanne Lai

Reema Shah

Derek Gregory Stainer

Akhilesh Kondra

Lubomir Kostadinov Vardin

Alejandro Moreno Ruiz

Enrico Cruz

Jingfei Chen

Michael Alan Jones

Brian P Bimschleger

Jennifer M Lyons

Andrew K Fry

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 system could include persistent storage containing application components. A plurality of software applications could be installed on the system. The software applications could be respectively associated context records that include references to application components that provide some behavior or data for the software applications. The system could also include processors configured to perform operations. The operations could include receiving a request to generate a topology map for a software application and identifying, based on a context record for the software application, a subset of application components that provide some behavior or data for the software application. The operations could further include determining relationship types between pairs of application components and generating a topology map for the software application. The subset of application components may be represented as nodes in the topology map, and edges between the nodes may be defined from relationship types between corresponding pairs of application components.

Application and related object schematic viewer for software application change tracking and management

Persistent storage may contain: (i) a database table containing entries, (ii) a definition of a communication endpoint of a remote system, and (iii) outbound flow processing. One or more processors may be configured to: detect a state change associated with a local entry in the database table; read, from the database table, a set of data representing the local entry; transform, using the outbound flow processing, the set of data into a format receivable by the remote system; create, for the set of data, a correlation record that contains a local correlation identifier, wherein the correlation record specifies the local entry; transmit, to the remote system, the set of data as transformed and the local correlation identifier; receive, from the remote system and for the set of data, a remote correlation identifier; add, to the correlation record, the remote correlation identifier; and write, to a correlation table, the correlation record.

Cross-platform communication for facilitation of data sharing

An embodiment may involve defining a process by first and second process design applications, wherein the process includes a set of stages; receiving, by a process visualization application, a reference to a parent entry and a definition of the process referencing the parent entry; based on the parent entry, identifying a first transformer class associated with the first process design application and a second transformer class associated with the second process design application, wherein the individual classes contain executable functions; converting an output of the first and second process design applications in a first configuration into a second configuration based on a first transformer class associated with the first process design application and a second transformer class associated with the second process design application, wherein the second configuration is accessible to the process visualization application; generating a display of the process in a hierarchical arrangement, wherein the hierarchical arrangement reflects the sets of stages and the associated activities.

Software architecture and user interface for process visualization

An embodiment may involve a definition of a process, wherein the process is referenced by a parent entry, wherein the process includes a set of stages, wherein the stages in the set of stages are respectively associated with sets of activities, and wherein a process design application was used to define the process. The embodiment may also include one or more processors configured to: (i) receive a reference to the parent entry; (ii) identify a transformer class associated with the process design application, wherein the transformer class converts output in a first configuration related to the process design application to input in a second configuration; (iii) receive, from the transformer class, data related to the process in the second configuration; and (iv) generate a graphical user interface that displays the process and the set of stages in a hierarchical arrangement.

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 computational instance of a remote network management platform may include persistent storage and one or more processors. The persistent storage may contain a recursively-defined complex data object, and one or more processors may be configured to: (i) transmit a depiction of a graphical user interface including a visual representation of the recursively-defined complex data object, where the complex data object as well as each array and object therein is represented as a collapsible menu item that can either display or hide its elements; (ii) receive a modification to an element of the complex data object, wherein the modification is either removal of the element, addition of the element, or a change to the associated type of the element; (iii) update the persistent storage to represent the complex data object as modified; and (iv) transmit an update to the visual representation that reflects the complex data object as modified.

Graphical user interfaces for incorporating complex data objects into a workflow

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.

Growing community of inventors

Carlsbad, CA, United States of America

Jacob Samuel Burman