With release 9.3.1, changes were made to support Designer Express and Designer Staker functionality. The following upgrades are necessary only if you wish to implement Designer Express or Designer Staker.

These instructions are intended for GIS administrators who currently are in production with Workflow Manager and who want to upgrade to the most recent release of the ArcFM Solution. This document does not apply if you are not currently using Workflow Manager and will be implementing it with the most recent version of the ArcFM Solution (i.e., you are new to ArcFM and are starting with the most recent release). If this is the case, refer to Set Up Workflow Manager.

If you are upgrading your Process Framework, you may also need to use the Process Framework Database Upgrade tool.

Designer Express

The following changes are necessary only if you wish to implement Designer Express.

Create Role

The Role must be spelled and capitalized exactly as shown below. However, the Role Name is how it appears in the user interface and can be any name you'd like. Assign this role to any user that will access the Cost Item Library Manager.

Role: EXPRESS_POWER_USER (must be spelled and capitalized exactly as shown)

Extensions: MMWorkflowManager

Create Transitions

ExpressSendToGIS

Database: Enterprise

Transition Name: Send Express Design to GIS

Node Type: Design

Roles: Assign roles as appropriate

From States: <None> and In Design

To State: As-Built Editing

KeepInAsBuilt

Database: Enterprise

Transition Name: Keep in As-Built Phase

Node Type: Design

Roles: Designer

From States: <None> and As-Built Editing

To State: As-Built Editing

Create Tasks

Create Express Design

Creates a design for use with Designer Express.

Database: Enterprise

Node Type: Work Request

Transition: Design Work Request

Assign Subtasks: (in order as shown)

Create Design

Set to Express Design

Open Express Design

Opens a design for use with Designer Express.

Database: Enterprise

Node Type: Design

Roles: Designer

Assign Subtasks: (in order as shown)

Open Express Design

Open Express Design for As-Built Editing

Opens an Express design for as-built editing.

Database: Enterprise

Node Type: Design

Transition: Keep in As-Built Phase

Assign Subtasks: (in order as shown)

Open Express Design for As-Builts

Close Express Design

Closes the currently open Express design.

Database: Enterprise

Node Type: Design

Roles: Designer

Assign Subtasks:

Close Express Design (to close an express design without submitting it to the Geodatabase Manager)
or
Close Express Design with GDBM (to submit an express design to the geodatabase manager while closing it.)

Send to GIS

Sends the selected express design to the GIS and converts it to a regular design.

Database: Enterprise

Node Type: Design

Transition: Send Express Design to GIS

Assign Subtasks: No subtasks are required, but they can be assigned. For example, Change Owner, Is Express Design (recommended).

Update Deleter

On the Node Types tab, update the following node type to use the Express Deleter.

Node Type: Design
Deleter: Express Deleter

Configuration Values

On the Configuration tab, add the following configuration values.

ExpressEstimateStylesheet: Used by Designer Express. This value provides a path to the XSL stylesheet used when exporting the Design Estimate report to Excel or a web browser (as HTML). Enter the path and file name. If you do not enter a value, the Design Estimate report will be exported into the default stylesheet included with Designer Express.
ExpressEstimateOpenWith: Used by Designer Express. This value determines in what format the Design Estimate report is exported. There are three valid options for this config value:

Browser: Export the Design Estimate report to a web browser as HTML. This uses the stylesheet indicated by the ExpressEstimateStylesheet value.

Excel: Export the Design Estimate report to Excel. This uses the stylesheet indicated by the ExpressEstimateStylesheet value.

Excelxmlmap: Export the Design Estimate report to an Excel template with an embedded map. This uses the Excel file indicated by the ExpressEstimateWorkbook value and the workbook within that file indicated by the ExpressEstimateExcelXmlMap value.

ExpressEstimateWorkbook: Used by Designer Express. This value provides a path to the Excel template to be used when exporting the Design Estimate report to an Excel spreadsheet that contains and embedded map. This value is only necessary if the ExpressEstimateOpenWith config value is set to Excelxmlmap.
ExpressEstimateExcelXmlMap: Used by Designer Express. This value provides the name of the workbook that contains the embedded map. This value is only necessary if the ExpressEstimateOpenWith config value is set to Excelxmlmap.

Designer Staker

The following changes are necessary only if you wish to implement Designer Staker.

Edit Existing Transitions

ConstructWorkRequest

Database: Field

Select Transition: ConstructWorkRequest

Enable (check) From State: In Construction

Node Type: Work Request

SubmitAsBuiltDesign

Database: Field

Select Transition: SubmitAsBuiltDesign

Enable (check) From State: As-Built Editing

Node Type: Design

Create Tasks

Construct Work Request

You must name this task "Construct Work Request" in the field Workflow Manager database. This task executes on a work request that contains a staking design in the field. It sets the work request's state using the Construct Work Request transition.

Database: Field

Node Type: Work Request

Transition: Construct Work Request

Task Roles: These are disabled but will default to Designer and Design Approval Officer

Visible in Task Tool?: Unselected

Assign Subtasks: There are no assigned subtasks

Open Staking Design

You must name this task "Open Staking Design" in the Enterprise Workflow Manager database. This task opens the selected stake job.

Database: Enterprise

Node Type: Design

Transition: None

Assign Subtasks: (in order as shown)

Open Staking Design

Create Stake Job

You must name this task "Create Stake Job" in both the field and Enterprise Workflow Manager databases. This task creates a new stake job. Tasks created in both the field and Enterprise databases should always be named the same in both places.

Database: Enterprise and Field

Node Type: Work Request

Transition: Design Work Request

Assign Subtasks: (in order as shown)

Create Design

Set to Stake Job

Send Staker Design to Enterprise

You must name this task "Send Staker Design to Enterprise" in the field Workflow Manager database. This task sends a staking design to the Enterprise from a field machine.

Database: Field

Node Type: Design

Transition: Submit As-built Design

Assign Subtasks: (in order as shown)

Is Mobile Solution Enabled?

Does user own work request or design node?

Transition Stake Job to Enterprise

Send to Enterprise

Delete Stake Job

This task deletes a stake job.

Database: Field

Node Type: Work Request

Assign Subtasks: (in order as shown)

Confirm Delete Staking Job

Delete

Edit Existing Tasks

Submit As-Built Design

Database: Field

Node Type: Design

Remove this task from the field database.

Configuration Values

On the Configuration tab, add the following configuration values.

StakingSheetStylesheet: Used by Designer Staker. This value provides a path to be used when opening the staking sheet in Excel or a web browser (as HTML). Enter the path and file name. If you do not enter a value, the staking sheet will be exported into the default stylesheet included with Designer Staker.
StakingSheetOpenWith: This value determines the format to be used by the staking sheet. Enter browser or Excel.