Awesome! You also can assign the value of these toggles as something like "this toggle is no", instead of assigning them manually. That way, if the current toggle's value is no, it will become yes, and vice-versa. All in one workflow haha!
Splendid ! Simple and Elegant solution. So the Shortlisted constraint enables only when Toggle State is Yes and disables when Toggle State is empty. If I were building this, I'd def overcomplicate it, try to change DB Shortlisted Field to No at Candidate thing creation, etc...yay!
Awesome!
You also can assign the value of these toggles as something like "this toggle is no", instead of assigning them manually. That way, if the current toggle's value is no, it will become yes, and vice-versa. All in one workflow haha!
Perfect lesson
Is there a difference in creating two workflows with constraints or one workflow with two steps having the constraints?
Splendid ! Simple and Elegant solution.
So the Shortlisted constraint enables only when Toggle State is Yes and disables when Toggle State is empty.
If I were building this, I'd def overcomplicate it, try to change DB Shortlisted Field to No at Candidate thing creation, etc...yay!
is there any reason that you attach the toggle state to the company page? Or can you attach it to any element?
It's more or less like a best practice to attach custom states to the page element or popup elements.
Hello why not using a toggle icon directly ? The native plugin library has one. Or a Ionic toggle for more modern design
For educational purposes. I wanted to demonstrate how to build them and create this kind of logic using groups. By all means, use a plugin as well.