Chatta subito con l'assistenza
Chat con il supporto

Stat 6.3 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Defining a Custom Command

You can define custom commands for pre and post migration steps. These are operating system commands executed by the Stat Central Agent. Commands can be executed locally where the Central Agent is running or remotely on a migration target server via SSH. All drive mappings and file paths are relative to the server where the Central Agent is running. Commands can be triggered automatically during the migration or manually by the migrator.

1
In the Pre and Post Migration Step Maintenance window, click New and specify the object class and object type of the step you want to create.
4
Select Auto if you want the step to trigger automatically.
8
(Optional) Add Target Environment to trigger a migration step for a specific environment.
9
Click Apply to save your work.
10
Click Define Command.
11
In the Command field, enter the command you want Stat to run.
15
(Optional) In the SSH time-out in seconds field, specify a longer connection timeout amount.

%%yyyy%%

Year

2020

%%yy%%

Year

20

%%MM%%

Month in year

12

%%MMM%%

Month in year

Dec

%%MMMMM%%

Month in year

December

%%dd%%

Day in month

31

%%EEE%%

Day name in week

Tue

%%HH%%

Hour in day

10

%%mm%%

Minute in hour

35

%%ss%%

Second in minute

47

18
Click Apply.

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 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.

Release Level
(Key Value)

A tree view displaying major and minor releases

Active

If selected, activates the value in Stat

Release Name

Name assigned to the release number

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user who last updated this record

1
In the Domain field, select the service domain.
2
In the Module field, select the change management module.
6
Click Apply or OK.

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 for Description/Resolution | Application Templates.

The CSR Type Template Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Templates for Description/Resolution | 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.

Active

If selected, activates the value in stat

Application/
CSR Type
(Key Value)

The application or CSR type that the template is based on

Type
(Key Value)

Determines whether the template is to be used in either the Description or Resolution tab

Description

A 1-35 character description of the template

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user that last updated this record

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 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 required information, use double angle brackets: <<>>. In the example above, the sample template specifies recommended information, including User ID and Description of the Request.

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

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione