Programming Guides › Programming Guide for C › DMS Workflow API › DMS Workflow API Guidance › DMS Workflow

DMS Workflow

When a user initiates a DMS session, either by requesting self-registration or by entering a DMS administration application, the following SiteMinder objects are located:

• The realm of the requested resource. For self-registration, this is the realm containing the page for which the user is signing up. For DMS administrators, the realm is the location of the DMS Administration servlet. The realm is obtained by the SiteMinder Web Agent when the user requests access.
• The registration scheme associated with the realm. The registration scheme contains the name of the workflow library, if any.

  Because workflow is associated with a realm, it is possible to set up several workflow libraries, depending on the desired DMS event processing for a particular resource. For example, self-registration may be required in order to receive documents on separate sites, but the rules for pre- and postprocessing users for each site may be different.

  For example, it is possible to set up a number of self-registering sites; each may have its own workflow library.

If the registration scheme includes a workflow library name, the library is loaded. The loader checks to see that all the required functions are exported by the library. If the library can not be loaded or a function is missing, session initialization will fail and DMS requests for that realm will not be processed. To correct this situation:

1. Make sure the library has been installed in the correct location, as specified in DMS Workflow API Overview.
2. Ensure that the required functions are exported by the library.
3. If desired, disable the workflow by removing the library name from the registration scheme, using the Administrative UI.

When the workflow library is loaded, it will be called for every DMS event that involves adding, modifying, or deleting entities in the user directory during the session.