What the page shows
One card per Solution:- its name, description, version and package;
- whether it is On or Off, and who last changed that and when (times are in UTC);
- What it adds — the flow actions it provides (the ones you pick in a
callnode) and, when it has a console interface, its application, its pages and the places it adds to existing screens: actions, dashboard widgets, settings tabs, table columns and shell elements.
Turning one on
Click Turn on. The change is immediate, and the next flow run can use the Solution’s actions. The page records you as the person who did it, in the same journal the command line writes to.Turning one off
Click Turn off and confirm. From then on:- a flow that reaches one of its actions leaves that node by the error output with the reason
solution_inactive, so the flow can decide what to do; a session already running is not cut off, it takes that route on its next call; - whatever it added to the console disappears;
- its data is kept. Turning it off never deletes anything the Solution stored, and turning it on again brings it back as it was.