Previous	Next		Contents	Index	Glossary

• GetRoleUsers

• GetUserRoles

• GetRoleInfo

• GetRoleInfo2

• IsPerformer

• UserActive

• GetUserName

• GetRoleName

• GetRoleDisplayName

• CreateAdHocUser

• CreateAdHocRole

• CreateAdHocRole2

• AddUsersToAdHocRole

• AddUsersToAdHocRole2

• RemoveUsersFromAdHocRole

• SetAdHocUserStatus

• SetAdHocRoleStatus

• SetAdHocUserExpiration

• SetAdHocRoleExpiration

• SetAdHocUserAttr

• SetAdHocRoleAttr

• ChangeLocalUserName

• IsMLSEnabled

Attention: If you implement OID integration, you must maintain your users only through OID. You must not create ad hoc users in the WF_LOCAL_ROLES table, because you risk discrepancies in your user information and unpredictable results if you use any tool other than OID to maintain users after integrating with OID. Consequently, if you implement OID integration, you must not use the CreateAdHocUser( ), SetAdHocUserStatus( ), SetAdHocUserExpiration( ), or SetAdHocUserAttr( ) APIs in the WF_DIRECTORY package.

You can still use ad hoc roles, however, since Workflow roles are not maintained through OID.

Note: Some directory service APIs use PL/SQL table composite datatypes defined in the WF_DIRECTORY package. The following table shows the column datatype definition for each PL/SQL table type.

PL/SQL Table Type	Column Datatype Definition
UserTable	varchar2(320)
RoleTable	varchar2(320)

See Also