Good morning all,
New to BPMs here, so please exercise restraint with the ridicule and shame! (jk)
I am attempting to put in place a pre-processing method directive that throws an error if there is no input to the Expected Close field of the quote header. At first, the input shown below seems to work fine. The problem is that after that initial save, any subsequent changes to the quote form are throwing the error and the changes can’t be saved. Any advice is greatly appreciated!
If you are trying to make the Expected Close field required when creating a new quote it would be better to mark the field required in extended properties.
No BPM required.
What about multi-company situations? Where only one company requires the field to be required.
I imagine you would need a BPM?
Extended Properties are not company specific right?
I’m not super familiar with the kinetic version of BPMs, but I believe you are connected to the false side of that condition block. If you’re condition(s) test true, then it goes out the left side. If they test false, they go out the right.
The classic version of those are more intuitive.
Edit: and working through the weird double negative logic I guess should work?
It might not be null though, it might be empty string.
Not sure that is why I asked. Hoping someone could confirm.
Unfortunately (at least in 2024.1) if you save the BPM, close it and reopen it the arrows in the GUI will likely not be where they were before. I have given up on BPMs in the Kinetic screen and continue to launch those in Classic because even if the arrows are right and it works, I can’t easily see that and my OCD kind of kicks in with how I have things structured and I just can’t.
Correcting the Condition:Exception connection in Client and changing the condition to “equal to null”, along with changing the variable type to String, seems to have it working correctly.
Thank you all for your assistance! 
