지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Status Rules

Status rules let you apply restrictions to a CSR while it is in a particular status, such as the queue(s) that it can belong to, whether objects can be added or locked on a CSR and what environments objects associated with the CSR can be migrated to. For Oracle Applications, you can also limit the environments that can have patches applied to them.

To define a status rule:
1
In the Workflow Template window, right-click on the graphic representing the status you want. Then in the pop-up menu, select Status Rule.
Stat opens the Status Rules window for the selected status.
2
If you want to limit the queues that a CSR can belong to while in the selected status, select the queues you want in the Available Queues field.
If you do not select a queue, the CSR can belong to any queue in the list.
3
If the workflow involves migrations and you want to limit the environments that objects can be migrated to while the associated CSR is in the selected status, select the environments you want in the Environments Available for Migration field.
If you select {None}, no migrations can take place while the CSR is in the particular status. If you do not select an environment, the objects can be migrated to any of the environments in the list.
4
If you want to limit the environments in which archive sets can be created while the CSR is in the selected status, select the environments you want in the Environments Available for Archiving field.
If you select {None}, no archive sets can be created while the CSR is in the particular status. If you do not select an environment, archive sets can be created in any of the environments in the list.
5
If you want to prevent users to add objects to a CSR, select the option Disable Add Object.
6
If you want to require that developers enter a resolution in the Resolution tab of the CSR before transferring the status, select the Require Resolution option.
By default, users are required to enter a resolution whenever a CSR enters into a closed-type status. However, in certain cases it may be desirable that the resolution of the CSR be documented before it is closed. With this option, you can require that the resolution of the CSR is documented before the CSR changes from the selected status to any connected status in the workflow.
7
If you are defining a status rule for a workflow in the Oracle Applications module and you want to limit the environments that can have patches applied to them while the associated CSR is in the selected status, select the environments you want in the Environments Available for Patch Application field.
If you select {None}, no patches can be applied while the CSR is in the particular status. If you do not select an environment, a patch can be applied to any of the environments in the list. The patch application option is not used for workflows in the PeopleSoft and generic applications modules.
* 
CAUTION: Make sure your status rules and transfer rules are consistent. For example, if you define a status rule that says a CSR must belong to the Mgmt queue, do not define a transfer rule that does not allow a CSR to belong to the Mgmt queue.
8
Click OK or Apply to save your work.
In the workflow diagram, an asterisk is displayed next to the graphic representing the status, indicating the presence of a status rule.

Copying Workflows

If you want to copy a workflow to another service domain, associate a workflow to more than one CSR type, or if you want to create a new workflow that closely resembles an existing workflow, you can make a copy of that workflow and then modify it as needed.

You can associate a copied workflow with a different CSR type. However, you must associate it with a CSR type that is associated with same CSR statuses as the original CSR type. To copy a workflow to another service domain, the target service domain must include a CSR type that is associated with the same set of CSR statuses as the CSR type in the original workflow.

When copying a workflow, you can also select a different module and migration path. However, if you select a different migration path, this may conflict with any workflow rules you copy that require migrations to specific environments. When this is the case, you can either remove the migration requirements from the copied workflow rules, or you can update the copied workflow rules by referencing the new environments.

To copy a workflow:
1
In the Workflow Maintenance window, select the workflow that you want to copy and click Copy Template.
Stat opens the Copy Template window.
2
If you are copying the workflow to another service domain, select the service domain in service domain field.
The CSR Type field lists all the CSR types in the selected service domain that are associated with the same set of CSR statuses as the CSR type in the original workflow. If there are no matching CSR types, the CSR Type field is blank and you cannot copy the workflow to the selected service domain.
3
In the CSR Type field, select the CSR type you want to base the copied workflow on.
You can assign a different migration path to the copied workflow. You can select any migration path in any change management module you have access to. Be aware, however, that if the transfer and status rules of the original workflow require migrations to specific environments, you must do one of the following to successfully copy the workflow:
•
Opt not to copy the transfer and copy rules from the original workflow, or to exclude rules that specify migration environments, in which case the copied workflow will not require migrations to specific environments
•
Map the environments in the original workflow to environments in the migration path of the copied workflow. This way, status and transfer rules copied from the original workflow will be automatically updated with the different migration environments.
4
(Optional) If you want to assign to the copied workflow a migration path that is defined for a different change management module, select that module in the Module field.
5
(Optional) In the Migration Path field, select the migration path you want to assign to the workflow.
6
Type a name for the workflow in the Workflow Name field.
* 
NOTE: You may want to use the same name as the original workflow if all you are doing is assigning the copied workflow to a different CSR type in the same service domain.
7
Deselect the Copy Status Rules or Copy Transfer Rules options if you do not want to copy either the status rules or transfer rules.
8
Deselect the Exclude Migr. Env option if you want to copy status and transfer rules that require migrations to specific environments.
At this point, if you are copying rules that require migrations to specific environments but have assigned a different migration path to the copied workflow, Stat displays the Transfer Migration DB window which prompts you to map the environments in the original workflow to the environments in the copied workflow.
9
Map a new environment to each environment in the original workflow
10
Click OK when done.
The copied workflow is displayed in the Workflow Maintenance table. If you copied the workflow to a different service domain, select that service domain in the Domain field to see the copied workflow. At this point, you can open the workflow in the Workflow Template window and modify the template diagram and workflow rules as needed.

Configuring the Stat Central Agent

•
Starting and Stopping the Stat Central Agent
•
Defining Agent Jobs
•
Stat Central Agent Printers
•
Monitoring the Stat Central Agent
•
Customizing the What’s New Tab in Stat Web
•
Customizing Field Labels for the Stat Web Client

Starting and Stopping the Stat Central Agent

The Stat Central Agent is responsible for automating necessary but time-consuming work, such as generating and printing reports, sending email messages, archiving objects, and maintaining specific database parameters.

The Stat Central Agent is designed to run behind-the-scenes with minimal supervision on the part of system administrators. However, you can manually start and stop the Stat Central Agent when circumstances demand it.

You can run the Stat Central Agent on either a Windows or a Unix platform. If configured properly, the Stat Central Agent can also be run as a Windows Service. For information, see Stat Install Notes.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택