Workflow - action not working properly

[SanchoDavid35 (Sancho David)]

Hello all ,
I have been working on Workflows currently , while performing compare string operator it , but it always end ups in false value in either test cases .
Does anyone have any idea on it ?

[sisvanthkumar (Sisvanth Kumar S)]

Hi @SanchoDavid35 ,
I have also been facing the similar issue

The operator always results in negative value .
Kindly refer to this link , they said that they will be raising a ticket for that issue

Workflows - Compare Strings Contains Operator Not working

I was able to replicate the issue. I was able to get a False when I removed the pipe but when I added it back it is showing as true. @colin_mckibben, Is it a known issue?

@colin_mckibbenbaby any idea on this ?

[SanchoDavid35 (Sancho David)]

Will see to it thanks @sisvanthkumar

[GOKUL_ANANTH_M]

Hi @SanchoDavid35 and @sisvanthkumar ,

I am assuming that, you are using “contains” operator inside “compare strings”.

Yes, I too faced the same issue. But it is resolved by replacing it by “Verify Data Type”. As, compare strings is to make comparission between two strings.

Also, take a look at the below post, you may get an idea:

Workflow : Compare string Operator - Contains

Hello Team, I am using workflow action as “Get Account” and the get account is returning the accounts related to specific identity after that I am validating that the user having "demo " account or not, to validate that I am using “Compare String Operator Contains method” (Below are the values for compare string) Value 1 = $.getAccount.accounts[*].sourceName - [“demo”,“demo1”,“demo2”] operator = contains Value2 demo but the condition always goes to false even if the array contains “demo”. @…

Thanks!

[sisvanthkumar (Sisvanth Kumar S)]

Hi @GOKUL_ANANTH_M ,
FYI i have been using equals operator within the compare string

I see that the JSON Path value returns an array instead of string . That may be the problem .
Correct me if i am wrong .

Thanks!!

[GOKUL_ANANTH_M]

Hi @sisvanthkumar ,

yeah, it may be.

See the above attachement, I am getting the string value and comparing it with another. This is working fine.

So, I suggest you to check the values which are returned by $.defineVariable.newValue and oldValue.

Thanks!

[sisvanthkumar (Sisvanth Kumar S)]

Sure will check on it @GOKUL_ANANTH_M