Idea: Option to Have No Parameter in Microflow/Nanoflow #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added documentation.
It is now also possible to show the element when the Microflow returns 'false'
Bugfixed showing the element in the 'false' condition.
Added two functions: resetSubscriptions and updateRendering. The widget now refreshes on every refresh of your entity.
In previous versions, the widget was never hidden at a refresh. This does now work thanks to an improvement in the update function.
In the modeler, you can now hide elements inside the parent on true or false by providing their classname. This does require add the class 'hiddenByWidget' to your CSS. The stylesheet should hide the element when this class is applied.
Updated version number
commented logger.debug causing widget to break in Mx 7.14.1 and up
Mx 7.14.1 fix
Added option to select nanoflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, a parameter is required in the microflow. However, if not required, we could use the same microflow/widget across pages with different page parameters. This would allow for more reusability and less rework of microflows. Would be a minor convenience to have.
The use case is that we are checking an object attached to a user's account for an attribute, so the passed in parameter is irrelevant for the show by condition.