User already exists

weblike

Hi,

does anyone know if it could be implemented a function like in gmail for example?
When a new user is added in the form, interactively an alert message appears that the "user already exists".

BenHayat

This would require to be able to attach a rule to an attribute, so when attribute is changed, it would trigger the rule where the it can check the uniqueness.

Ability to attach rules to attribute can help in many areas too.

Powerm

You can find that rule on the CRM app too, something like :

If Customer IS NEW AND EXISTS Customer WHERE (Customer.EMail=ThisCustomer.Email AND Customer.ID<>ThisCustomer.ID) Then
REPORT ERROR ' USER ALREADY EXISTS 🙂 '

BenHayat

Powerm wrote
You can find that rule on the CRM app too, something like :

If Customer IS NEW AND EXISTS Customer WHERE (Customer.EMail=ThisCustomer.Email AND Customer.ID<>ThisCustomer.ID) Then
REPORT ERROR ' USER ALREADY EXISTS 🙂 '

What he is asking is an AJAX validation as soon as he enters the name BEFORE submitting the whole object.

Powerm

As far I know you will have to develop a script for that....

weblike

BenHayat wrote
What he is asking is an AJAX validation as soon as he enters the name BEFORE submitting the whole object.

Yes this what I meant.
REPORT ERROR is ok if you want to check the form on the end of editing, but if you have a huge form it's annoying to complete the hole form and in the end you get the message "duplicate record".

Powerm wrote
As far I know you will have to develop a script for that....

Do you mean a plugin, right?
Daes anyone have such a plugin? Could be shared on the community as a paid plugin...

BenHayat

weblike wrote
Do you mean a plugin, right?
Daes anyone have such a plugin? Could be shared on the community as a paid plugin...

No, not a plugin. What he is suggesting is "advance Scripting", which I doubt it would do it, unless you want to change to HTML Input rather than Aware Input.

As I said, this needs to be done inside Aware, where we can attach a rule to an attribute and have that rule execute when the attribute is changed and not the whole object. I had done that in other platform using AJAX, but I wish Aware had this feature.

weblike

Thanks guys for sharing your thoughts,

So, this would be a nice feature ....
Support could you consider looking on this, to have what Ben says?

thank you.

weblike

Hi,

No need of plugin or advanced script.
Just found a simple way to do this:

In BO create an attribute BO.AlreadyExist (Yes/No, calculated, default='No')
In BO create this dynamic rule:

If EXISTS SystemUser WHERE (SystemUser.LoginName=ThisBOUser.LoginName AND SystemUser.ID<>ThisBOUser.ID) Then
BOUser.AlreadyExist='Yes'
ELSE
BOUser.AlreadyExist='No'

To make this looking great inside the form, add a HTML cell and use: <<IF BOUser.AlreadyExist='Yes' THEN SHOW 'Message'>>...

This should do the trick. 🙂
Cheers,

Powerm

But your Rule means they have to save the Form first....

BenHayat

weblike wrote
Hi,

No need of plugin or advanced script.
Just found a simple way to do this:

In BO create an attribute BO.AlreadyExist (Yes/No, calculated, default='No')

In BO create this dynamic rule:

If EXISTS SystemUser WHERE (SystemUser.LoginName=ThisBOUser.LoginName AND SystemUser.ID<>ThisBOUser.ID) Then
BOUser.AlreadyExist='Yes'
ELSE
BOUser.AlreadyExist='No'

To make this looking great inside the form, add a HTML cell and use: <<IF BOUser.AlreadyExist='Yes' THEN SHOW 'Message'>>...

This should do the trick. 🙂
Cheers,

But that rule doesn't get executed until the Object is submitted, which not what you were asking. hat message in HTML cell only shows when you try to save. Unless I'm missing something.

weblike

Hi PowerM,

You are right about the HTML (just tested).. but the rule is executed and the BOUser.AlreadyExist is marked as YES...

The question now is how this is executed dynamically <<IF BOUser.AlreadyExist='Yes' THEN SHOW SECTION_START>> Message<<SECTION_END>> ???????

Powerm

That's the point....I have not seen anyone having implemented that dynamic piece 🙁
You could build a Wizard like Form , BO saved with they click on the Next button and show a different message if the USerName exists or not...just an idea.

weblike

Hi,

For the moment I did it with this workaround:

Inside the form :
1.Insert Separator Row with condition : "Not present when BOUser.AlreadyExist='No' " ...

It's true is not so elegant, but does the concept....It hides/shows the message accordingly.

If could use dynamically "THEN SHOW SECTION_START....SECTION_END"...would be great....

hpl123

George,
Here are some thoughts on a solution that ALMOST works like the Gmail one.

Create an attribute called "DuplicateMessage"

Create a rule (Initialization rule):

If UserDup.Username IS DEFINED AND EXISTS UserDup WHERE (UserDup.Username=ThisUserDup.Username) Then
 UserDup.DuplicateMessage='<font style=font-weight:bold;color:red;>Username not available</font>'
ELSE
If UserDup.Username IS DEFINED AND NOT(EXISTS UserDup WHERE (UserDup.Username=ThisUserDup.Username)) Then
 UserDup.DuplicateMessage='<font style=font-weight:bold;color:green;>Username available</font>'

On your form, create 2 html cells:
Button cell:

<button type="button" onclick="AwareApp.recalculateObject2(this)">Username Available?</button>

Message cell:

<<UserDup.DuplicateMessage>>

This solution enables you to check if a username is available BEFORE saving the form i.e. the user can do it when typing in information on the form. I have attached some screenshots below and I haven´t cleaned up the form or maked it look good. I just wanted to show you the result.

hpl123

Forgot to add, this can also be made kind of dynamic i.e. so you don´t need the button. If you follow my instructions in my last post, remove the button and make the rule "Dynamic recalc", as soon as the user moves to the next attribute on the form, the rule would execute and the user would see if the username was available.

hpl123

Another thing, as part of the rule you might have to check the ID i.e.

If UserDup.Username IS DEFINED AND EXISTS UserDup WHERE (UserDup.ID<>ThisUserDup.ID AND UserDup.Username=ThisUserDup.Username) Then
 UserDup.DuplicateMessage='<font style=font-weight:bold;color:red;>Username not available</font>'
ELSE
If UserDup.Username IS DEFINED AND NOT(EXISTS UserDup WHERE (UserDup.ID<>ThisUserDup.ID AND UserDup.Username=ThisUserDup.Username)) Then
 UserDup.DuplicateMessage='<font style=font-weight:bold;color:green;>Username available</font>'

Not sure, test it.

crisg0112

hpl123 wrote

Another thing, as part of the rule you might have to check the ID i.e.

If UserDup.Username IS DEFINED AND EXISTS UserDup WHERE (UserDup.ID<>ThisUserDup.ID AND UserDup.Username=ThisUserDup.Username) Then
 UserDup.DuplicateMessage='<font style=font-weight:bold;color:red;>Username not available</font>'
ELSE
If UserDup.Username IS DEFINED AND NOT(EXISTS UserDup WHERE (UserDup.ID<>ThisUserDup.ID AND UserDup.Username=ThisUserDup.Username)) Then
 UserDup.DuplicateMessage='<font style=font-weight:bold;color:green;>Username available</font>'

Not sure, test it.

Hi,

I am assuming this is a GUEST login and a registration form, BUT shouldn't the validation be done on the RegularUser Business object ??

or am i not understanding at all (which happens a few times without coffee)

hpl123

Chris,
I created a BO just for this problem (UserDup) but yes, this solution would be implemented in for example the RegularUser BO and could be part of a Guest to Registered process.