Hi Balaji
This does indeed have to do with how a Nanoflows run differently from Microflows.
See the documentation on Nanoflows, specifically chapter 3, point 6:
3 Differences from Microflows
There are five main differences between nanoflows and microflows:
- When a nanoflow steps through its actions, client actions are directly executed. For example, an open page action immediately opens a page instead of at the end of the nanoflow. This is different from client actions in a microflow, which only run when the client receives the result from the microflow.
- When used in nanoflow activities, expressions do not support the following objects and variables:
$latestSoapFault
, $latestHttpResponse
, $currentSession
, $currentUser
, $currentDeviceType
.
- Nanoflows are not run inside a transaction so, if an error occurs in a nanoflow, it will not roll back any previous changes.
- Nanoflows and microflows do not provide the same actions. Some actions available in microflows are not available in nanoflows, and vice versa.
- Because nanoflows use JavaScript libraries and microflows use Java libraries, there can sometimes be slight differences in the way expressions are executed.
- Changes done to the lists in a sub-nanoflow are not reflected in the original nanoflow.
Best regards,