Share via

User Information for Workflow Applications

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

To implement security specific to your workflow applications on the server or Microsoft® SQL Server™ Named Instance, the Workflow Services for SQL Server maintains the workflow application User Directory, which exists as the modUserList table in the modSystem database. It stores information about the Microsoft® Windows® 2000 domain users and groups who have access to the server and the workflow applications. It can include details such as e-mail addresses, telephone numbers, and managers.

The user directory also stores additional data for each user that is useful for scripting e-mail notifications and other functionality in your workflow. Rather than keep separate stores of duplicate information, you can set the user information to be synchronized automatically from your Microsoft® Exchange Server directory or Windows Active Directory, or you can synchronize manually through the Workflow Manager for SQL Server.

When you enable workflow on your database, the Workflow Designer creates a view in the database based on the modUserList table. This modUserList view can be used to make user information available in your application user interface, if desired.

The user information supplied in the user directory makes it possible for you to implement features such as:

  • Sending e-mail notifications to a valid user or group. Use script to notify specific users or groups automatically when events are triggered in the application.
  • Displaying the full name of the person associated with a security account. Stored user information can be queried by the application to display full names of the valid users instead of only their Windows account names.
  • Escalating issues to a manager. Look up a user's manager in the user directory, and send e-mail or assign the issue to the manager.

See Also

Developing the User Interface for SQL Server | The User Directory | Maintaining the User Directory for Workflow Applications | Populating Controls with User Information