Have you tried to use the integration to read the files from FTP and wondered if there was a way to externalize the FTP location outside the integration? Or create an integration that sends out notification and wanted to externalize the recipient of the email as a property to be passed as a parameter to the integration? We have heard from our customers on the need for an easy way to externalize properties from the integration and be able to modify the values without editing the integration.
Changing hard-coded parameter values in the integration canvas can be a time-consuming task as
i) Integrations needs to be edited
ii) Familiarity with the integration and the design tool in order to update the appropriate action and property.
Also, there are use cases where an integration is developed by a one user and run by different users. The user running it might not have privileges to edit the integration making it difficult to change the parameter values.
We have introduced a new feature that allows the integration developer to define properties which are exposed and can be modified outside of the integration designer. Integration developers can define properties of their choosing, providing them with meaningful names and default values, and then use them throughout the integration in the rich set of available actions. Although property values are not modifiable using integration actions, what makes them extremely useful is that the default value can be overridden outside of the design tool prior to running the integration. This feature is available for both - App Driven and Scheduled Orchestration styles. Read the complete article here.
For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.