Assignments
In a typical session life cycle, Session Manager moves the session through an editing and approval stage prior to posting the edits to the default version of your GIS data. The mechanism that Editor XI uses to do this is called Assignments. Assignments are akin to states from the ArcFM 10.x series and accompany the session throughout its journey. Administrators decide if your organization uses a two-state or three-state workflow.
The out-of-the-box (OOTB) Assignments that get created within ArcFM Editor XI (two-state workflow) walk through a typical life cycle as described below:
-
When a session is created, an Edit assignment is created.
-
When a session is sent for approval, an Approval assignment is created.
-
When a session is rejected, the Edit assignment is reopened.
-
When a session is approved, a new Approval assignment is created.
The out-of-the-box (OOTB) Assignments that get created within ArcFM Editor XI (three-state workflow) walk through a typical life cycle as described below:
-
When a session is created, an Edit assignment is created.
-
When a session is sent for approval, a Review assignment is created.
-
When a session is rejected, the Edit assignment is reopened.
-
When a session is sent for approval again, a new Review assignment is created.
-
When a session is approved, a new Approval assignment is created.
Notice that when a session is rejected, the Edit assignment is reopened. However, when that session is re-sent for approval or review, a new Approval or Review assignment is created rather than reopening the old Approval or Review assignment. This is intentional design that allows for the retention of session history. If preferred, reopening an old Approval or Review assignment is possible by customizing the Session Manager workflow. When considering making a change such as this, assess the impacts upon session history.