User Attribute Check fails to generate unique email

[nvachhani]

We are using the user attributes table to perform addition uniqueness check on creating new user emails. The email generation rule has a basic config:

Rule1 -

firstname

.

lastname

customstring

Rule2 - 

firstname

.

lastname

AutoIncrement - 1

customstring

I can see the logs fail to continue the autoincrement once the additional email address is found in the user_attributes table:

"2024-03-02T19:14:51.441+00:00","ecm","services.WorkflowService","http-nio-8080-exec-4-vt2jx","DEBUG","userattribute email check hql = Select new Map(count(ua.data) as total) from UserAttributes ua where data=:email "
"2024-03-02T19:14:51.443+00:00","ecm","services.WorkflowService","http-nio-8080-exec-4-vt2jx","DEBUG","Email userfirst.test2@xxxstage.com exists in user attributes so ignoring rule ( concat(users.firstname , substring('.',1,1) , users.lastname , substring('~1',1,1) , substring('@xxxstage.com',1,16)) ) "
"2024-03-02T19:14:51.443+00:00","ecm","services.WorkflowService","http-nio-8080-exec-4-vt2jx","DEBUG","All rules exausted. Unable to generate email"

Full logs are attached. Is there something wrong with the check against the user_attributes table? 

[sudeshjaiswal]

Hello @nvachhani,

Can you please share the screenshot of the rules.

Thanks.

[nvachhani]

Screenshots are attached.

   

[sudeshjaiswal]

Hello @nvachhani,

You can use the email generation rule with two rules using the basic config to achieve this requirement(please refer to the below screenshots). 
or else you can use also use the advanced query as well.

please refer to the below screenshots.

Rule1 :

Rule 2:

Thanks.

[nvachhani]

Hi, this is what I am using already above. But the rule fails to continue the autoincrement once the additional email address is found in the user_attributes table