...
| Warning |
|---|
This means that you should not upgrade a production Profound.js 5 instance before thoroughly testing the application with Profound.js 6 and making any needed modifications. Testing should be done in a separate Profound.js instance, so that production applications are not affected. |
Modifications for Async/Await
Existing applications may need slight adjustments to add async and await keywords for Promises where Profound.js module transformation is not able to do so automatically. For details, see Coding With Promises in Profound.js and the section Limitations of Module Transformation. The scenario given on that page is just one example. There may be other cases where module transformation is unable to add async/await, depending on how the application is code.
Low Code Steps/Routines Converted to Code
Low Code applications which contain steps or routines that have been converted to code will need a slight adjustment if the converted steps/routines contain calls to other routines which were created by the Call Another Routine or Call Internal Routine plugins.
For example, the Call Another Routine plugin for Rich Display Files generates code like this:
The generated code needs to be adjusted to add await to the call, for example:
Similarly, the Call Internal Routine plugin for low code modules generates code like this:
The code needs to be adjusted like this:
Conversion of Start.js Files
...