Workflow Manager (Classic) system setup

Available with Standard or Advanced license.

The following is an outline of the steps necessary to get a Workflow Manager (Classic) system up and running.

Enterprise database setup

The first step in setting up a new Workflow Manager (Classic) system is to run the Create Workflow Database geoprocessing tool to create Workflow Manager (Classic) system tables in your enterprise database.

This tool also provides options for importing the minimum, quick-start, or custom configuration files, as well as setting the user store to traditional or portal for the Workflow Manager (Classic) database. Once the tool finishes, the current Windows user is registered as a user in Workflow Manager (Classic). This user is also added to the Administrator group and granted Administrative Access to Workflow Manager Administrator. Administrator Access is based on a privilege. For more information, see Privileges.

Specific database preparation recommendations have been outlined in guide books for Oracle and SQL Server.

Workflow Manager (Classic) database connection

Workflow Manager (Classic) applications require database connection information to access job information in the Workflow Manager (Classic) repository. The Create Workflow Database geoprocessing tool also creates the database connection. For more information on manually adding the connection, see Adding a WMX Database connection in the Administrator.

Workflow Manager (Classic) users

Users are a central configuration element in the Workflow Manager (Classic) system. Application authentication, job assignment, and tracking all rely on Workflow Manager (Classic) users. Users, in combination with groups and privileges, control the access privileges and permissions within the Workflow Manager (Classic) system.

Users, groups, and privileges are part of the Workflow Manager (Classic) security module. Together, they grant users access to the system, log actions on jobs, and control application functionality.

Anyone who accesses Workflow Manager (Classic) must be registered with the Workflow Manager (Classic) system. When first configuring Workflow Manager (Classic), you may encounter a message like the following when the Workflow Manager (Classic) client application starts. See Configuring users and groups for more information about adding Workflow Manager (Classic) users.

When the user trying to access Workflow Manager (Classic) hasn't been added as a Workflow Manager (Classic) user, the application displays a message.

Workflow Manager (Classic) configuration for your business

After the initial setup of the Workflow Manager (Classic) repository, you'll be ready to begin configuring Workflow Manager (Classic) to meet your specific needs. A great place to start is with a workflow that represents a process you follow every day, week, or month. The Configuring Workflow Manager (Classic) section covers all the concepts needed to define your business processes within Workflow Manager (Classic), including workflow editing.

The Workflow Manager (Classic) SDK installed with the desktop and server editions includes additional help for customizing the Workflow Manager (Classic) client application, building custom workflow steps, and extending your Workflow Manager (Classic) implementation.

Workflow Manager (Classic) deployment to your users

Once you have your system up and running and are ready for your users to start tracking their work with Workflow Manager (Classic), you'll need to deploy it to them. There are few steps involved with this that are outlined in Workflow Manager (Classic) system deployment.