Before when using the deprecated alert element, we could toggle the alert using a global variable, that was set via a global workflow.
With the new dialog component we need to use a component workflow to toggle the alert. This works initially using a global workflow, but when we copy the the alert component to another page, the global workflow is broken, because it can’t find the component to execute the component workflow for.
Another flaw in my opnion, is that the new alert element (dialog) has no feature to auto hide, We now need te create an workflow with a delay to close it.
Any thoughts on this?
How can we now create a global alert function using the new dialog Alert element, by just trigger the global workflow on any page we want to use it?
This has been an issue with execute component actions in general for awhile. Components on a different page are technically “different components” so the same workflow in the global workflow doesn’t actually find the correct component.
We’ve got around this with a less than ideal solution but it does work. You need the global workflow to check the current page it’s on then have a multi option action and use condition to check the currentPage then go to each page you need it on and add a new execute component action to that options branch
Not sure if this is what you’re going for, but I have an alert section with a nested modal and toast (enabling the ability to present notifications based on importance) that is reused across pages. We’ll passing in the data from the backend. Anyhoo, I read/learned that by making it a multi-page section I’m able to achieve the outcome without making it a component.
