-
Notifications
You must be signed in to change notification settings - Fork 761
11.5 Studio Pro Release Notes #10371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Conversation
|
|
||
| ### New Features | ||
|
|
||
| - Pages and snippets can now capture and use return values when calling microflows or nanoflows by specifying an [action return value mapping](TODO-LINK-TO-DOCS_BY-WTF). For primitive return values, the value can be assigned to any matching attribute, page variable, or snippet variable. For object return values, select one or more attributes to map to different variables - useful for assigning multiple computed values from a single flow call. Return values can be transformed using expressions before assignment, such as applying formatting when assigning a number to a string variable. This feature enhances microflow and nanoflow reusability by allowing pages to update local values based on flow return values without needing to pass objects containing those attributes to the flow. It also enables changing variables on pages and snippets based on business logic modeled in the flows. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the docs link in question this is the PR for. It still needs a review, once done, we could then add the proper link here. If you need help, let me know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added the link to the doc in the PR, thank you Anca.
|
|
||
| ### Fixes | ||
|
|
||
| - We fixed an issue where a wait-for-timer activity could get stuck when its workflow was upgraded while the activity was active. (Ticket 263288) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be "Timer" instead of wait-for-timer @Yiyun333 ? I see some mentions around the docs that something like this was renamed.
No description provided.