Skip to content

Commit 5020584

Browse files
committed
Remove note on difference between microflows and nanoflows in String attributes handling
1 parent 9024398 commit 5020584

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

  • content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/_index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,4 +35,3 @@ Below presents a list of main differences between microflows and nanoflows:
3535
* When used in nanoflow activities, expressions do not support the following objects and variables: `$latestSoapFault`, `$latestHttpResponse`, `$currentSession`, `$currentUser`, `$currentDeviceType`.
3636
* Nanoflows are not run inside a transaction. So, if an error occurs in a nanoflow, it will not roll back any previous changes.
3737
* <a id="list-changes-in-sub-nanoflows"></a>Changes done to the lists in a sub-nanoflow are not reflected in the original nanoflow.
38-
* In nanoflows, when retrieving an `empty` attribute of an object, an empty string (`''`) is returned.

0 commit comments

Comments
 (0)