Under Consideration

Case sensitive evolution in JO calculated fields

  • 17 December 2020
  • 5 replies
  • 53 views

Userlevel 4
Badge +2

Hi Team,

Currently when we use the email values in the calculated fields it is not handling the case sensitive values . Can we take this up as enhancement and implement it to handle the case sensitive values.


5 replies

Userlevel 7
Badge +2

@tejkumar Thanks for sharing this here! I have changed this to idea and redirecting this to our product team. 

If it is a customer request, you can tag here for a reference. 

Userlevel 7

@tejkumar For your use-case, do you want it to be case sensitive or case insensitive?

Userlevel 7
Badge +2

@tejkumar For your use-case, do you want it to be case sensitive or case insensitive?

@tejkumar need your inputs here.

Userlevel 4
Badge +2

@nitisha_rathi @sai_ram 

want it to be case insensitive.

example: source from participant: abc@gmail.com

target :Abc@gmail.com

Which is not matching expected to match in the calculated field.

Userlevel 7

Hello @tejkumar 
We will take this up as part of redesign. Thanks for bringing this up.

Reply