Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How to block a transition if a value in field is missing

I have 2 fields:

- Root cause

- Supplier

Root cause is a mandatory field, Supplier isn't.

When a user selects a root cause of '3rd party system issue' then I want them to always specify the 'Supplier'.

How do I block the ticket from being transitioned to resolved in this case? I can't seem to work out how to do this under the 'Conditions' tab of the workflow.

1 answer

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 23, 2022

Hi @Kara Hopkins,

No, indeed. Conditions are triggered before you even let a user try to execute it. If you want to validate if something is filled out, you should use validators instead.

First of all, make sure you have a screen associated with the specific transition in your workflow that has your mentioned fields on them. Then, add a Field required validator to the transition, where you select the fields that should be mandatory.

If the required fields are not filled out, an error message will appear on your transition screen and the transition will be aborted.

You may find that you cannot make the validation of the supplier field related to the root cause. To work around that, you could add 2 transitions to move from to resolved, using a Value Field condition to enable either option of the root cause field (empty or not empty). More or less like this:

Screenshot 2022-11-23 at 17.02.05.pngBy using opposite conditions, only 1 transition to resolved will be available to your users. One can then have the validator for the supplier field while the other one doesn't.

Hope this helps! 

Thanks, I don't understand from this point onwards:

To work around that, you could add 2 transitions to move from to resolved, using a Value Field condition to enable either option of the root cause field (empty or not empty). More or less like this:

+1 for Kara here. IMO, validators are the wrong choice, as the desired behavior is to direct the allowed transitions based on the field population in order to guide the user, rather than reprimanding the user for a disallowed transition after the fact. 

Suggest an answer

Log in or Sign up to answer