The following are known issues associated with this release of the connector:
Bug 7703095
During provisioning, if you set a secondary responsibility but do not select a value from the PrimaryResponsibility lookup field, then the secondary responsibility becomes the primary responsibility on the target system.
During provisioning, if you set the primary responsibility on the process form, then the responsibility is propagated to the child form. However, if you delete the responsibility from the child form, the change is not propagated to the process form. This change is propagated to the process form only after the next reconciliation run with the target system.
Bug 7207232
Some Asian languages use multibyte character sets. If the character limit for the fields in the target system is specified in bytes, then the number of Asian-language characters that you can enter in a particular field may be less than the number of English-language characters that you can enter in the same field. The following example illustrates this limitation:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you have configured the target system for the Japanese language, then you would not be able to enter more than 25 characters in the same field.
Bug 8722540
The connector does not support the failover feature in which multiple Siebel installations are used to ensure uninterrupted service to users.
Bug 12543085
If you run a target system reconciliation for users of type User, the target system reconciliation task fails.
As a workaround, customize the process form and make the Position field optional.
The following are limitations of the target system:
During provisioning, the Set/Reset Password function cannot be run because the target system does not support JDB APIs.
During reconciliation, a user's password cannot be fetched because the target system does not support JDB APIs.
The batched reconciliation feature has not been implemented for this connector because the target system does not support JDB APIs.
During provisioning, the primary position assigned to a user in the target system cannot be removed through Oracle Identity Manager.
The Lock/Unlock and Disable/Enable functions cannot be run because the target system does not support these functions.
On the target system, if you delete a position or responsibility assigned to a user, then this change is not fetched into Oracle Identity Manager during the next incremental reconciliation run. This is because the time stamp of the user record is not updated in response to these events.