Abstract: Techniques for user gesture recording are provided. In one technique, while recording user actions with respect to a website, it is detected that a user entered text within a text field of a webpage of the website. An action pane is presented that includes a value text field and a test value text field. In response to the detection, the text is inserted into the test value text field of the action pane. An association between the text, the text field, and the test value text field is stored as part of a workflow. In a related technique, user input is received through the action pane, where the user input selects a reference, to a source of input, to include in the text field during execution of the workflow.

Abstract: Techniques are provided for limiting access to a feature in an application. Certain application features, such as access controlled features, are not generally accessible to all users of an integration cloud service system. When a user makes a request to access an access controlled feature, the system can determine whether user information satisfies the requirements to access a requested access controlled feature. If the user satisfies the requirements for the requested access controlled feature, an access key can be dynamically generated based on the user information.

Abstract: Techniques are disclosed for identifying, applying and validating changes to activities in an integration flow. A user may make a change to an activity in an integration flow. Other activities in the integration flow may be affected because of the change. Any activities that are affected by the change are identified and changes are made to the affected activities so that the integration flow can operate correctly. After the changes are made, the activities are validated to ensure that the changes made are consistent with the integration flow.

Abstract: In accordance with an embodiment, described herein is a system and method for exporting and importing integration flows in a cloud-based integration service. The cloud-based integration service includes a web interface application for creating an integration flow, and a runtime for executing the integration flow. The web interface application can provide an import interface and an import logic component, and an export interface and an export logic component. The export logic component can be configured to export an integration flow and its dependent resources, regardless of their lock states, and with secured information removed from the dependent resources. The import logic component can be configured to import an integration flow and its dependent resources; and perform a plurality of checks and validations for each dependent resource being imported, to determine whether to create the dependent resource in the system, or keep an existing dependent resource in the system.

Abstract: Techniques are described for controlling availability of objects in a visual design tool for integration development. An integration developer may select a node to add to an integration and, in response, the integration cloud system can analyze the structure of the integration flow, query other nodes within the structure of the integration flow for configuration data, and generate available configuration options for the selected node. The integration cloud system can use the available configuration options to control the availability of objects by only providing the available configuration options for selection by the developer.

Abstract: Techniques are provided for limiting access to a feature in an application. Certain application features, such as access controlled features, are not generally accessible to all users of an integration cloud service system. When a user makes a request to access an access controlled feature, the system can determine whether user information satisfies the requirements to access a requested access controlled feature. If the user satisfies the requirements for the requested access controlled feature, an access key can be dynamically generated based on the user information.

Abstract: Techniques are described for controlling availability of objects in a visual design tool for integration development. An integration developer may select a node to add to an integration and, in response, the integration cloud system can analyze the structure of the integration flow, query other nodes within the structure of the integration flow for configuration data, and generate available configuration options for the selected node. The integration cloud system can use the available configuration options to control the availability of objects by only providing the available configuration options for selection by the developer.

Abstract: Techniques are disclosed for identifying, applying and validating changes to activities in an integration flow. A user may make a change to an activity in an integration flow. Other activities in the integration flow may be affected because of the change. Any activities that are affected by the change are identified and changes are made to the affected activities so that the integration flow can operate correctly. After the changes are made, the activities are validated to ensure that the changes made are consistent with the integration flow.

Abstract: Various arrangements for organizing business components for use in creating a business object are presented. A selection of a business context may be received from a plurality of business contexts. After receiving the selection of the business context, for each business component of the plurality of business components, whether the business component is within the received business context or outside of the received business context may be determined. An indicator may be assigned to each business component of the plurality of business components based on the business component being determined as being within the received business context or outside of the received business context. Each business component of the plurality of business components with the business component's assigned indicator may be presented.

Abstract: Various arrangements for organizing business components for use in creating a business object are presented. A selection of a business context may be received from a plurality of business contexts. After receiving the selection of the business context, for each business component of the plurality of business components, whether the business component is within the received business context or outside of the received business context may be determined. An indicator may be assigned to each business component of the plurality of business components based on the business component being determined as being within the received business context or outside of the received business context. Each business component of the plurality of business components with the business component's assigned indicator may be presented.