Uniqueness of a field

> Option 2 is actually not that hard to implement

With option 2 if the process will be cancelled I'll need a manual rollback deleting the record from the database.

I think Appian is not the best tool to tuning database locking and manual transaction management.

That's correct, it is quite common. However, you usually generate the unique items; in the case of IDs for primary keys, for example, you don't ask the user to enter the unique ID.

I'm guessing you have a requirement for a name to be unique - but my question would be why does it need to be? I'm just curious what the requirement is :)

Appian is quite cabale of implementing locking - optimistic or otherwise - but it does take a bit of work. This might be interesting reading if you've not already seen it: docs.appian.com/.../Database_Schema_Best_Practices.html

It's not yet a real requirement, I'm preparing myself for Designer exam and looking around for general ideas. Simple real requirement I can think of is a list of employees. They can have same first name + second name, but the email should be unique.

> This might be interesting reading if you've not already seen it: docs.appian.com/.../Database_Schema_Best_Practices.html

Oh! Regular JPA @Version.

@sergeiz: Regarding answering to comments. New Appian community site will be released soon and solve this issue.

@stefanh791 Good!