Upgrade Session Manager to 9.0.1

Use these upgrade instructions if you are:

  • Using a version of Session Manager older than 9.0.1

  • Upgrading to a version of Session Manager that is 9.0.1 or higher

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

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

Upgrade to 9.0.1

With release 9.0.1, tools were added to Session Manager to support Mobile functionality. The following roles, states, transitions, and tasks are necessary only if you wish to use ArcFM Solution in the field.

Roles

The following must appear in the Roles column exactly as they appear below. Any Role Name may be assigned.

  • SESSION_ALWAYS_MOBILE_USER

  • SESSION_MOBILE_USER

States

Add the following state to the States tab:

State

Node Type

State Name

Description

Control Prog ID

8

Session

Mobile

Indicates the session is ready for field editing. You can enter any description in this field.

mmSessionManager.clsSessionUI

Transitions

Add the following transitions on the Transitions tab. The value in the Transition field must appear exactly as shown below. You can enter any Transition Name and Description.

  • SessionMobilize

    • From States: In Progress

    • To State: Mobile

  • SessionDemobilize

    • From States: Mobile

    • To State: In Progress

Tasks

You will need to create the following tasks using the Process Framework Administration Tool. The Task Name must appear exactly as shown in bold below.

The following tasks should be added to the Session Manager database on the Enterprise server (e.g., SessionManager.mdb).

  • After Session Import

    Node Type: session

    Assign Subtasks: (in order as shown)

    • Re-send Session to Field

  • Import Mobile Session Features

    Node Type: session

    Assign Subtasks: (in order as shown)

    • Is Mobile Solution enabled?

    • Does user own session node?

    • Is session open?

    • Import Mobile Features

  • Send Sesson To Current Field Owner

    Node Type: session

    Assign Subtasks: (in order as shown)

    • Send Session to Field

  • Send Session to Field

    This task requires that the SessionMobilize transition exist.

    • Node Type: session
    • Assign Subtasks: (in order as shown)
    • Is Mobile Solution enabled?

    • Change Session Owner To Mobile

    • Send Session to Field

  • Send/Receive Mobile Data

Node Type: all Session filters (AllSessionsFilter, UserSessionsFilter, UserStatusSessionsFilter)

Assign Subtasks: (in order as shown)

  • Is Mobile Solution enabled?

    • Is Enterprise Disk Full?

    • Mobile Synchronize

    • Update Enterprise

    • Mobile Synchronize

The following task should be added to the field Session Manager database (e.g., Field SessionManager.mdb).

  • Send Session to Enterprise

    Node Type: session

    Assign Subtasks: (in order as shown)

    • Does user own session node?

    • Is Mobile Solution enabled?

    • Change Owner All Session

    • Send Session To Enterprise

  • Send/Receive Mobile Data

    Node Type: all Session filters (AllSessionsFilter, UserSessionsFilter, UserStatusSessionsFilter)

    Assign Subtasks: (in order as shown)

    • Is Mobile Solution enabled?

    • Mobile Synchronize

    • Mobile Update

QR code for this page

Was this helpful?