Abstract: A method of generating and using a metadata files for integration flows may include analyzing definition files of integration flows to generate metadata files that include summary information for each of the integration flows. The method also includes extracting source-target relationships from the summary information for each of the integration flows and training a model using the plurality of source-target relationships. The method also includes receiving a source element from a current integration flow; providing the source element and characteristics of the current integration flow to the model; and receiving, from the model, recommended target elements to be connected to the source element in the current integration flow.

Abstract: Techniques are disclosed for providing notifications to a user. A user can configure the types of notifications they would like to receive. The notifications are generated according to messages that are generated in response to changes to activities in an integration flow. Types of notifications can include error notifications, system notifications and status notifications. The notification can be provided to the user via an electronic communication.

Abstract: Techniques are disclosed for collecting and visualizing historical data. Messages can be generated in response to user requests to make changes to activities in an integration flow. Data associated with the message can be collected in order to generate historical data regarding the message. Depending on the integration flow, a predetermined time point for generating the historical data can be obtained, and the historical data can be generated when the predetermined time point occurs.

Abstract: Described herein are systems and methods for providing stage file objects in a visual design tool for integration development. The integration can be developed on a cloud based integration service that can receive, via a visual development tool interface, selection of a stage file object for insertion into an integration flow. The cloud based integration service can also receive a selection of a type value for the stage file object. The scope for the stage file object can be determined, and the stage file object can be displayed in the integration flow based on the type value and the scope.

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: A method of generating and using a metadata files for integration flows may include analyzing definition files of integration flows to generate metadata files that include summary information for each of the integration flows. The method also includes extracting source-target relationships from the summary information for each of the integration flows and training a model using the plurality of source-target relationships. The method also includes receiving a source element from a current integration flow; providing the source element and characteristics of the current integration flow to the model; and receiving, from the model, recommended target elements to be connected to the source element in the current integration flow.

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: 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 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: 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: Described herein are systems and methods for providing stage file objects in a visual design tool for integration development. The integration can be developed on a cloud based integration service that can receive, via a visual development tool interface, selection of a stage file object for insertion into an integration flow. The cloud based integration service can also receive a selection of a type value for the stage file object. The scope for the stage file object can be determined, and the stage file object can be displayed in the integration flow based on the type value and the scope.

Abstract: Techniques are disclosed for providing notifications to a user. A user can configure the types of notifications they would like to receive. The notifications are generated according to messages that are generated in response to changes to activities in an integration flow. Types of notifications can include error notifications, system notifications and status notifications. The notification can be provided to the user via an electronic communication.

Abstract: Techniques are disclosed for collecting and visualizing historical data. Messages can be generated in response to user requests to make changes to activities in an integration flow. Data associated with the message can be collected in order to generate historical data regarding the message. Depending on the integration flow, a predetermined time point for generating the historical data can be obtained, and the historical data can be generated when the predetermined time point occurs.

Abstract: A system for migrating first data objects from a first repository product to a second repository product exports the first data objects from the first repository product into a schema. The schema describes a logical model of the first data objects. The system maps the first data objects to second data objects of the second repository product. The system trims the first data objects. Trimming comprises performing data modification on the first data objects so that the first data objects can be migrated to the second repository product. The system also creates placeholders for the first data objects for later deployment binding.

Abstract: A system for migrating first data objects from a first repository product to a second repository product exports the first data objects from the first repository product into a schema. The schema describes a logical model of the first data objects. The system maps the first data objects to second data objects of the second repository product. The system trims the first data objects. Trimming comprises performing data modification on the first data objects so that the first data objects can be migrated to the second repository product. The system also creates placeholders for the first data objects for later deployment binding.