topic Re: Validator behaivng so weirdly in ThingWorx Developers

Validator behaving so weirdly

MA8731174 — Mon, 30 Jun 2025 14:25:42 GMT

I am giving the input false but still validator is taking it as a true. Can anyone has similar experience about it?

MASHUP 1 and from here i am sending the value to another mashup which is false but another mashup is still taking it as a true why?

MASHUP 2 : this validator execute when the value of the mashup parameter will change which i am sending from mashup 1.

Re: Validator behaivng so weirdly

Velkumar — Fri, 26 Apr 2024 06:51:47 GMT

Hi @MA8731174

Uncheck default output value in validator and try

Also use console.log to debug function further

/VR

Re: Validator behaivng so weirdly

MA8731174 — Fri, 26 Apr 2024 08:45:26 GMT

Hi @Velkumar @Rocko I am having very very strange issue. look my validator is working completely fine in the same mashup and on true and false it opens two different mashups and for the output of the validator i am sending through mashup parameter. Strange thing is the true value is always going well but when output is false it just does not appear there in second mashup.

here is my validator from mashup 1

here is my code from the above validator from mashup 1

and here is the validator from second mashup. here when i get false i want to close this mashup but unfortunately i am not able to do it why? can anyone please look at it?

here in this validator when i get false i get nothing in console.log but for true my console.log displays true. thats why i am trying here the null/undefined etc..

i tried this code too
if(input ===false)

output =false;

but no its just does not work

i have tried another thing now. in mashup two directly accessing true or false but same behaviour it just does not get false from mashup 1.

I have tried below thing too. same results.

Re: Validator behaivng so weirdly

Rocko — Fri, 26 Apr 2024 09:34:04 GMT

The events work fine for me.

Try to use Auto Evaluate?

Also, don't use console.log. I thought you learnt that lesson the last time

(there was supposed to be a smiley after this, but it got filtered out)

Re: Validator behaivng so weirdly

MA8731174 — Fri, 26 Apr 2024 09:48:36 GMT

Hey @Rocko I have removed console.log also now. but still it cannot take false value. console.log was for another test actually. can you please share your code for validators. Its still not working for me. If I give hardcoded false then it works but it is not coming from 1st mashup.

Re: Validator behaivng so weirdly

Rocko — Fri, 26 Apr 2024 09:55:15 GMT

Not much to share, I tried "Output=input;" as validator expression, just like you and enabled Auto Evaluate (I'm on TWX 9.5 though).

Most probably this is an order of execution problem.

Reduce the problem to the minimum. Create an empty mashup with a checkbox and a validator, link the output to a label and play with that before you embed this in a larger composition with popups, mashup closing and so on.

Re: Validator behaivng so weirdly

MA8731174 — Fri, 26 Apr 2024 10:01:24 GMT

I have filled the checkbox on the same mashup 1 with this false and send the state of it to second mashup but same issue.

INFO:

With the output false i open another mashup which is mashup 3 and i pass the output to the mashup parameter of mashup 2 so thats an issue may be. but on father mashup i put checkbox and there the output is working completely fine but i am unable to take it through mashup parameters actually.

Re: Validator behaivng so weirdly

MA8731174 — Fri, 26 Apr 2024 10:47:14 GMT

So if i open the mashup 2 again after closing it manually then it gets close means for the first it is not working.

WORKFLOW: i open the mashup 2 then from it i do something to open mashup 3 but onclose function of mashup 3 i send the mashup parameter to mashup 2 to close it but when i close mashup 3 it does not get close means mashup 2 is still open then i close it manually and if i open the mashup 2 again it gets close means now the its closing the mash up 2. how can i fix this execution problem. i dont think so i have much area available to play in thingworx, any idea?