Stat 6.1 - System Administration Guide

Pre Migration Steps

The Pre Migration Steps Maintenance table defines actions that should be taken before an archive set is migrated. Like post migration steps, pre migration steps are either manual or automatic, meaning they are performed either by users or by Stat.

You can associate pre migration steps with object types and with target environments (unlike post migration steps, which are only associated with object types). This means that pre migration steps are triggered whenever users migrate an archive set that includes an associated object type, or when they migrate an archive set to an associated environment.

NOTE: You can define pre migration steps that are not associated with either an object type or an environment. In this case, the step is triggered for all migrations.

When defining a pre migration step, you can specify it should be run only once for a particular CSR, migration, or target environment. This way, you can prevent a step from being run multiple times when it should be run only once (e.g., a step that executes a script against a particular database).

Pre migration steps security is controlled by the following user class rights:

The Pre Migration Steps Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Pre Migration Steps.

Release Management Maintenance

The Release Management Maintenance table defines major and minor release labels that users can assign to archive sets. This gives users the ability to upgrade their applications or roll back to previous versions by mass migrating archive sets based on application release number. For more information on mass migrating archive sets based on application release labels, see the “Object Migrations” sections in the change management chapters of the book, Stat User Guide.

Application releases are based on a branching concept by which minor releases reference their immediate parent releases. This way, when a user mass migrates archive sets based on a minor release label, for example, 2.1, any archive set assigned its parent release label, 2.0, are migrated as well.

Application release security is controlled by the following user class rights:

The Release Management Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Release Management.

Application release numbers are specific to service domain and change management module.

NOTE: When assigning a release label to an archive set, Stat concatenates the name of a minor release with the name of its parent releases, separated by decimal points. For example, if you name a minor release “2”, and its parent major release “1”, Stat displays the value as “1.2” when assigning an archive set a release label. This is also true for minor releases of minor releases.

NOTE: You can use the same name for a major and a minor release, but you cannot use the same name for two releases defined on the same level. This includes names that use leading or trailing spaces.

Template Maintenance

Template Maintenance tables define text templates that are placed in the Description and Resolution tabs of a CSR. Templates are triggered by CSR type and application codes. When a user working on a CSR selects a type or application associated with a template, Stat automatically inserts that template into the text field of the tab that it has been defined for. You can define a separate template for each application and CSR type in a service domain. If a template exists for both the selected CSR type and application, Stat displays the type template above the application template.

Although templates are optional, they are strongly recommended to get the most out of your Stat system.

Template security is controlled by the following user class rights:

The Application Template Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Templates | Application Templates.

The CSR Type Template Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Templates | CSR Type Templates.

The following table defines the fields (columns) in the both the Application Template Maintenance window and the CSR Type Template Maintenance window.

The Edit Template Window

After you have defined a new template record, click Apply to save your work. Then click Template.... Stat opens the Edit Template window. Here you can specify the information that a user is required or recommended to enter in the Description or Resolution tab of a CSR. The Edit Template window features the same rich text editing capabilities supported in the Description and Resolution tabs, including a Formatting toolbar. For more information on rich text editing, see the book, Stat User Guide, Chapter 3, “Change/Service Requests.”

To create a template, type a short description of each piece of information that the user is required or recommended to enter. For recommended information, follow the description with angle brackets: <>. For required information, use double angle brackets: <<>>. In the example above, the sample template specifies recommended information, including User ID and Description of the Request.

NOTE: Make sure the template definition does not contain carriage returns at the end of its text, which results in random characters being added to the Description and Resolution tabs in CSRs that use the template.

If you want to see a graphic representation of a template, right-click on a template and then select Print from the right-click menu. This prints a template report which displays information concerning font changes, such as size, color, and italics.

After defining the template, click OK or Apply to save your work.