Abstract: The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Abstract: Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Abstract: Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Abstract: The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Abstract: The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Abstract: Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Abstract: Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Abstract: The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Abstract: The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Abstract: Systems and methods are provided and include a processor, memory, and an application that is stored in the memory and includes instructions. The instructions are configured to initiate a stateful session for the application by sending a session initiation request addressed to a global endpoint and receive a response to the session initiation request from a first server of a first server cluster, the response including a cluster identification associated with the first server cluster. The instructions are further configured to send a session request addressed to the global endpoint, the session request including the cluster identification associated with the first server cluster. The instructions are further configured to receive an error message in response to the session request from a second server of a second server cluster to resend the session request addressed to the first server cluster in response to receiving the error message.

Abstract: Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Abstract: Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Abstract: Systems and methods are provided and include a processor, memory, and an application that is stored in the memory and includes instructions. The instructions are configured to initiate a stateful session for the application and receive an initial server response including at least one configuration parameter to be used during the stateful session. The instructions are further configured to determine whether the at least one configuration parameter is not acceptable and send an initial client response to the server in response to a determination that the at least one configuration parameter is not acceptable, the initial client response including a proposed adjustment to the at least one configuration parameter.

Abstract: The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Abstract: According to examples, an apparatus may include a processor and a memory on which is stored machine readable instructions that are to cause the processor to store a copy of an external resource on the apparatus, transmit a request for renewal of a lock lease for the external resource, and based on a failure to receive a reply to the renewal request, enter the apparatus into a state in which: the processor processes a new operation on the stored copy of the external resource, and following a determination that the lock lease is lost, the processor outputs a notification that the apparatus lost the lock lease.

Abstract: Systems and methods are provided and include a processor, memory, and an application that is stored in the memory and includes instructions. The instructions are configured to initiate a stateful session for the application by sending a session initiation request addressed to a global endpoint and receive a response to the session initiation request from a first server of a first server cluster, the response including a cluster identification associated with the first server cluster. The instructions are further configured to send a session request addressed to the global endpoint, the session request including the cluster identification associated with the first server cluster. The instructions are further configured to receive an error message in response to the session request from a second server of a second server cluster to resend the session request addressed to the first server cluster in response to receiving the error message.

Abstract: Systems and methods are provided and include a processor, memory, and an application that is stored in the memory and includes instructions. The instructions are configured to initiate a stateful session for the application and receive an initial server response including at least one configuration parameter to be used during the stateful session. The instructions are further configured to determine whether the at least one configuration parameter is not acceptable and send an initial client response to the server in response to a determination that the at least one configuration parameter is not acceptable, the initial client response including a proposed adjustment to the at least one configuration parameter.

Abstract: A facility for using gestures to attach visual inflection to displayed text is described. The facility receives first user input specifying text, and causes the text specified by the first user input to be displayed in a first manner. The facility receives second user input corresponding to a gesture performed with respect to at least a portion of the displayed text, the performed gesture specifying an inflection type. Based at least in part on receiving the second user input, the facility causes the text specified by the first user input to be displayed in a manner that visually reflects application of the inflection type specified by the performed gesture to the at least a portion of the displayed text with respect to which the gesture was performed.