Multiuser capabilities

IBM® Safer Payments is designed for many concurrent users.

It locks viewed and edited content for a minimum amount of time to ensure maximum productivity. Different lock mechanisms are used for different parts of IBM Safer Payments.

Administrative functions

Most administration pages have a table that lists existing items. A New item button is displayed to users with edit privileges so they can create new items. Clicking an entity opens an entry. Save and Delete buttons are displayed to users with edit privileges.

To avoid multiple users from editing the same item at the same time, the first user that opens an item in editable form implicitly reserves the item. Each other user that clicks the item in the table, opens the form in noneditable mode. The reservation is kept until the first user finishes editing the form, or the first user logs out, or the first user's session is timed out. The Session timeout is defined in Administration > System Configuration > Application Programming Interface.

Because all items' name must be unique, the uniqueness of the item name is checked within the JavaScript code in the form. However, in rare situations that two users simultaneously create two items with the same name, IBM Safer Payments makes a second check for name doublets when the item properties are saved.

Decision model maintenance

For more information about how revisions are locked, see the online help topic for Revision Control.

Case investigation

If a case is under investigation by a user, its status in the Investigation Cases table shows a Investigated by [user name] since [time] message. Other users can view case, but case investigation actions are disabled for them while the first user is investigating the case.