| |
Identity Management system infrastructure
Description: |
It is best to have the Identity Management system as separated as possible from the other systems within the IT infrastructure. For example, in a Windows environment, it is better that the system will reside on its own domain.
|
| |
Free Text Vs. Dropdown
Description: |
Avoid using free text in workflow forms unless there is no alternative. For example, It is OK to have a "Comments" field as free text, but for State or other well defined parameters, try to use a dropdown list.
|
| |
Go-Live data
Author: Nitai nitaia@idfocus.com Description: |
Corrupt or "dirty" data is a sure cause for a "Go- Live" failure. Before going live make sure to spend enough time going over the data to be uploaded.It is common to find missing, corrupt or unnecessary data.
|
| |
Corrupt User data
Description: |
Even with flawless workflow logic, technical problems may still corrupt users data. It is important to constantly monitor users data and catch data problems before they become Help Desk tickets.
|
| |
Self-Service notifications
Author: Yuval yuvaln@idfocus.com Description: |
When linking between a Self-Service front end system and a User Provisioning system, remember that the user request may be processed on the background, and the user will not get an immediate answer. If so, consider possible ways to convey the new information to the user (an email for example).
|
| |