Stat 6.2 - User Guide

Approving Migrations

Before you can migrate an archive set into a PeopleSoft environment, you may need to get the migration approved by users authorized to approve migrations into that environment. Conversely, if you have been designated as a migration approver for a particular environment by your system administrator, other users may need your approval before they can migrate archive sets into that environment. Migration approvals are environment-specific. They provide a way for users (typically managers and development leaders) to monitor and control migrations into environments containing sensitive information, such as object definitions that should not be modified or overwritten.

Approval lists can be either required or optional and can include individual users, entire user classes, or a combination of the two. Although system administrators can add any user or class to an approval list, be aware that only users that have access to an environment (as determined by system administrators in the User Maintenance table) will be able to approve a migration into that environment or receive email notifications regarding their pending approval. If an approver does not have access to the environment, the migration cannot be approved until either the user is granted access to the environment or the migration’s approval requirements are overridden by another user with proper security rights.


	TIP: To check whether migrations into a particular environment require approvals or not, see the Approval Required column in the environment table of the Target Environments window.

For more information on migration approvals, see the Stat System Administration Guide, Chapter 4, “General Maintenance Tables.”

To approve a migration:

Select Migration Management | Migration Approvals.

Stat opens the Migration Approvals window.

The first tab, My Open Approvals, shows all the pending migrations (if any) that are still waiting your approval. The data is grouped by CSR in a tree view, along with archive ID and target environment. Open the tree to see the approval status of specific pending migrations. A green check mark indicates that the approval requirements for the migration have already been satisfied by other users, whereas a red X indicates that one or more users have rejected the migration, thereby preventing the migration from running until the rejection status has been resolved.


	IMPORTANT: A migration cannot go forward if just one approver rejects the migration, even if that user’s approval is not otherwise required. Before the migration can occur, either the user or another user authorized to override migration approvals must change their approval status from Rejected to Approved or to Pending.

Your approval can be made either as an individual or as the member of a user class. Also, approvals are either required or optional:

•

If required, Stat cannot perform the migration until you approve it. With a required user class approval, every user in the class must approve the migration.

•

If optional, then you are one out of a number of users authorized to approve the migration. Whenever an approval is marked as optional, the Min Approval column displays the minimum number of optional users who must approve the migration.


	TIP: Double-click an approval record to open its associated CSR.

The second tab, All Open Approvals, shows the same information as the My Open Approvals tab, except it shows the approval records for all users for each pending migration. This tab is for informational purposes only unless you have the user class right to override migration approvals, in which case you can approve migrations for other users and change approvals they previously made. Each user’s approval record is displayed until the migration has taken place.

In the My Open Approvals tab, select Approved in the Status column for each migration that you want to approve. If you do not approve the migration, select Rejected.

Click OK or Apply to save your changes.

If you selected Rejected, the approval record stays on the My Open Approvals tab until you change it to Approved, or the migration approval is overridden, or the archive set is changed so that it is no longer ready to migrate.

(Optional) Do the following if you have the right to override migration approvals:

Open the All Open Approvals tab and approve or reject migrations for other users or change the migration approval status other users as needed.


	TIP: With proper security rights, you can also change the status of your own migration approvals.

If you change a migration approval status for yourself or another user, Stat prompts you to document your reasons for doing so.

If prompted, document the reasons why you are changing your own or another user’s migration approval.

Click OK or Apply to save your changes.

A record of the approval remains on the All Open Approvals tab until the migration takes place.

You can also approve the migration of an archive set in the Target Environments window of the CSR.

To approve a migration in the Target Environments window:

Open the CSR to which the archive set belongs. Then follow the instructions for opening the Target Environments window for the archive set as described in the preceding section.

In the table on the right side of the window, select the target environment of the archive set. Then click Approval Lists.

This opens the Approval List for Target Environment window, which displays all the optional and required approvals that are still pending for the migration of the archive set.

Double-click your corresponding row. Then in the popup menu, select Approved.

Click OK or Apply.


	TIP: With proper security rights, you can make approvals for other users. You can also unapprove all approvals by clicking Unapprove All. This allows you to deselect the Ready to Migrate check box for the target environment. When you override another user’s approval, Stat records you as the approver, not the user originally assigned to make the approval.

You can view records of migration approvals from the Migration Details window. For more information, see Documenting Migrations (PeopleSoft) .

Approval Request Notifications

If you want to notify users about migrations that are still pending their approval, you can email a message predefined by system administrators. In the tree list of approvers, select the node representing the user or class that you want to notify and click Email. An email job request is sent to the Stat Central Agent, which processes the request and sends an email to the user you selected or to each member of the selected class. A “@” sign is displayed for that approver node in the Envelope field of the Approval List tab.


	NOTE: The Email button is disabled once the approval requirements of a migration have been satisfied.

System administrators can also configure the Stat Central Agent to include links in the reminder message that the recipient can click to approve or reject the migration. This sends an email back to the Stat Central Agent, which processes the response email and changes the approval status to Approve or Reject, depending on which link the approver selected.


	NOTE: When an approval status is changed by responding to a reminder message, the Update Date field in the Approval List window will be automatically populated and the Update By field will display the value, Via Email.

Approval notification reminder messages can also be sent for workflow status transfers. For more information, see the book Stat System Administration, Chapter 7, “Email Configuration”.

Mass Migrating Objects

If you need to migrate several archive sets to the same environment, rather than migrate them one at a time, you can perform a mass migration. There are two types of mass migration supported by Stat:

•

Using the Ready to Migrate method, you can include as many archive sets from different CSRs in a mass migration as you want, even if the objects are assigned to different developers and come from different source environments.

•

Mass migrating archive sets based on an application release label allows you to quickly update a target environment with the latest version of objects or roll back to earlier versions.

Because mass migrations can include objects assigned to different users and belonging to different CSRs, it is recommended that a limited number of users be allowed to perform mass migrations. With proper security, users can perform mass migrations that override workflow rules and approval requirements. In addition, Stat features the Release Recovery window, which allows users to perform application release mass migrations that override workflow rules, approval requirements, and object locks. For more information, see Release Recovery Window .

To perform a mass migration:

Mark each archive set for a migration, as described earlier in this chapter.

Select Migration Management | Mass Migration.

Stat opens the Mass Migration window.


	TIP: You can resize the window and the panels as needed to view the complete listing of archive sets and objects.

(Optional) If you want the Stat Central Agent to process the migration job at some later time, enter the date and time in the Migration Date field.

The field defaults to the current date and time. You can schedule the migration up to 90 days in the future.

(Optional) In the Description field, enter a unique description of the migration.

The field defaults to “Mass Migration”.

(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.

System administrators may set this option to be selected or de-selected by default.

In the Module field select PeopleSoft.


	TIP: You can set a default value to be displayed in the Module field. To do this, select User Options \| Stat Options. Then in the Stat User Options window, select the value you want in the Default Module field.

In the Service Domain field, select the service domain associated with the migration path containing the target environment you want.

The service domain you select filters the list of target environments as well as the list of release labels if you opt to mass migrate objects assigned the same release label.

In the Target field select the environment to which you want to migrate the archive sets.

If using the Ready to Migrate method, Stat displays a list of each archive set that has been marked as Ready to Migrate into the selected environment.

In the Type field select one of the following:

•

Select Ready to Migrate if you want to mass migrate archive sets that have been individually marked for migration

•

Select Migration by Release if you want to mass migrate archive sets that have been assigned the same application release label. When you select this option, the Release field is displayed. Then in the Release field select the release label you want. Release labels can be minor or major and are defined by system administrators. After you select a release label, Stat displays a list of archive sets that have been assigned that label.


	NOTE: A Minor release is considered a branch of its parent release. This means that when you mass migrate archive sets based on a minor release label, Stat migrates all the archive sets assigned the parent release labels as well. For example, using a typical version sequence, if you mass migrate archive sets labeled release 2.2.1, Stat also migrates archive sets assigned its parent release labels, 2.2 and 2.0. When the same object is found in archive sets with different release labels, Stat migrates the object with the latest release label.

(Optional) In the Sources section, deselect Migrate for each archive set that you do not want to include in the mass migration.

By default, this check box is selected for each archive set that has met migration approval requirements.


	NOTE: Using the Ready to Migrate method, if the same object exists in two or more archive sets, Stat displays a message box prompting you to select which object you want to migrate.

(Optional) In the Archive Migr Order column, change the order in which selected archive sets will be migrated.

By default, Stat assigns archive sets a migration order number. The first archive set is assigned the order number 1, the second 2, and so on. You can change this order by assigning your own order numbers. Lower order numbers are migrated first.

With the proper security rights, you can exclude certain object classes from the migration. You can also exclude individual objects. If the same object is contained in more than one archive set, the most recently archived version is selected by default in the Migrate column. You can override this selection by selecting a different version.

(Optional) Deselect the class of objects (file objects or PeopleSoft objects) you do not want to migrate.

(Optional) In the Migrate column, deselect the individual objects you do not want to migrate.

If you are migrating to a distribution environment, the window displays the list of active target environments. By default, each environment in the distribution list is selected as a target. However, with the appropriate security rights, you can exclude certain environments from the migration.

(Optional) If migrating to distribution environment, deselect any environment in the list of active target environments you want to exclude from the migration.

Specify the migration parameters you want in the remaining fields of the Mass Migration window.

These parameters are the same as those that you would otherwise specify in the Migration window if you were running a typical drag and drop migration. For more information, see Running a Migration (PeopleSoft) .


	IMPORTANT: If you opt to use a Stat-defined name for the PeopleSoft project created by Stat during a mass migration, Stat uses the naming convention, “SM######,” as opposed to “ST######.” Also, if you opt to define your own name for the project, the name must be uppercase and no longer than 28 characters. Stat appends the letters “SM” to the beginning of user-defined names to identify mass migration projects.