Replacing Non-Secure Functions
The following topic describes how to replace non-secure functions manually in a mashup. You can also replace non-secure functions using the Mashup Migration dialog.
 |
Not all non-secure functions that contain references to unsupported APIs can be migrated automatically.
|
Replacing Non-Secure Functions in a Mashup
To replace non-secure functions, perform the following steps:
1. Edit an existing Mashup entity in Mashup Builder, then open the Functions panel. All non-secure Expression and Validator functions are grouped and listed under a Not Secure label.
2. Expand the Expressions (Not Secure) or Validator (Not Secure) sections to view the list of non-secure functions in the mashup.
3. To replace a non-secure function, click 
. The function edit dialog box opens.
. The function edit dialog box opens.4. Review the current expression and resolve any issues that are highlighted in the code editor under Expression. Remove references to unsupported objects or functions. For more information, see Supported Runtime Functions and Objects.
5. Click Done to replace the function with the new standard version.
6. Repeat steps 2 through 5 to replace additional non-secure functions in the mashup.
7. Click Save to save the changes.
| | The latest functions execute asynchronously at run time. Make sure to use completion events to execute bound services that depend on the function. |