Abstract: The disclosure generally describes one or more techniques for supporting deployment of application extensions for a client system. An inline frame is implemented in a user interface and a secure session established between the inline frame and a server. A user can update data displayed at the user interface through the secure session established in the inline frame to activate an extension available at the server to update the data. The extension can respond with data indicating how the user interface should be updated.

Abstract: The disclosure generally describes one or more techniques for supporting deployment of application extensions for a client system.

Abstract: In some embodiments, a computer system receives a user interface corresponding to an event-based workflow, generates event data based on a user input to the user interface, and provides the event data to the host platform system causing the host platform system to attempt to execute a first step corresponding to one or more events of the event-based workflow, wherein a failure to execute the step is resolved in at least one of a first manner or a second manner, the first manner corresponds to a first set of one or more execution criteria associated with the step, and the second manner corresponds to a second set of one or more execution criteria associated with the step. In response to providing the event data, the computer system receives a result corresponding to the attempted execution of the step and updates the user interface based on the result.

Abstract: In some embodiments, after receiving event data corresponding to an event-based workflow, the computer system attempts to cause execution of the first step corresponding to one or more events; and in response to receiving an indication that execution of the first step corresponding to the one or more events has failed, the computer system resolves failure the first step in a manner that is based one or more execution criteria (e.g., failure criteria) that is associated with the first step.

Abstract: Aspects of the present disclosure relate to systems and methods for managing access to data in a cloud-based software platform. An end-user account associated with an organization account may request access to data in a data store of the organization account. A schema associated with the data may specify collections of user access permissions, each collection being associated with a different user role. The request for access to the data is then granted (or denied) subject to the collection of user access permissions that is associated with the user role of the end-user account.

Abstract: In some embodiments, after receiving event data corresponding to an event-based workflow, the computer system attempts to cause execution of the first step corresponding to one or more events; and in response to receiving an indication that execution of the first step corresponding to the one or more events has failed, the computer system resolves failure the first step in a manner that is based one or more execution criteria (e.g., failure criteria) that is associated with the first step.

Abstract: Aspects of the present disclosure relate to systems and methods for managing access to data in a cloud-based software platform. A first cloud-based software application running on the cloud-based software platform and connected to a user account generates first data associated with the user account, where the first data is structured in accordance with a first data schema. This first data is stored in a cloud data store in association with the user account, where access to the data by a second cloud-based software application connected to the user account is subject to access permissions specified by the first data schema.

Abstract: The disclosure generally describes one or more techniques for supporting deployment of application extensions for a client system.

Abstract: An online collaborative workspace system includes a set of first subsystems and a workflow subsystem. The first subsystems provide a project-oriented social network environment in which system users collaboratively interact with user-defined application objects that store user data and user-determined application functions executed to display the user data and interlink the application objects into project-scale organizations. The first subsystems can include commenting, task and status subsystems. The workflow subsystem includes a workflow builder and a workflow engine. The workflow builder provides a visual interface enabling a user to define custom workflows for the application objects, where a workflow is a cause-effect structure identifying a trigger event that causes the workflow to be executed and defining an action performed on or by an application object in response to the trigger event. The workflow engine receives system events and executes workflows having corresponding triggers.

Abstract: An online collaborative workspace system includes a set of first subsystems and a workflow subsystem. The first subsystems provide a project-oriented social network environment in which system users collaboratively interact with user-defined application objects that store user data and user-determined application functions executed to display the user data and interlink the application objects into project-scale organizations. The first subsystems can include commenting, task and status subsystems. The workflow subsystem includes a workflow builder and a workflow engine. The workflow builder provides a visual interface enabling a user to define custom workflows for the application objects, where a workflow is a cause-effect structure identifying a trigger event that causes the workflow to be executed and defining an action performed on or by an application object in response to the trigger event. The workflow engine receives system events and executes workflows having corresponding triggers.