Stat 6.0 - System Administration Guide


	TIP: The icon background appears blue when selected and changes to gray when other fields or action buttons are activated. As long as the background of the operator icon is blue or gray, then approver groups and other operators can be attached to the operator.

In the Approver Type field, select the approver group you want to add to the list.

Options include User, User Class, and Queue.

When adding approvers, be aware of the following:

•

Adding individual users to approval lists could create problems if those same users are later inactivated or have their service domain and environment access restricted. For this reason, it is recommended that you add user classes to approval lists rather than individual users whenever possible.

•

Users assigned to a transfer approval list must have the user class rights to operate in the same change management module in which the status transfer takes place. Also, you can assign user class rights that enable users to change CSR statuses regardless of approval status and also to approve status transfers on the behalf of other users.

In the Approver Name field, select the name of the user, user class, or queue you want to add.

In the Required field, select Required if the approval is required or Optional if it is not required.

The Required option means that the individual user and every member of the user class or queue must approve the status transfer. Optional means that the individual user’s approval is not required, whereas for user classes and queues, it means that the approval of only a specified minimum number of users within that class or queue are required.

If you selected User Class or Queue in the Approver Type field and Optional in the Required field, specify the minimum number of users in that class or queue who must approve the transfer in the Number field.

Click Add.

The approver is added to the tree structure under its approver group label and the initial AND or OR operator. Required approvers are displayed in bold.

At this point, how you proceed depends on the different approver groups you want to add to the list and how you want to define the relationships between these groups using AND and OR operators.

(Optional) Do the following to add additional AND or OR operators to your approval list:

Depending on the relationship between approver groups in your list, select the operator icon to which you want to attach additional operators.

Click AND or OR.

Repeat as necessary to add more operator icons to the approval diagram.

(Optional) To add additional user class or queue approver groups, select the appropriate operator icon in the approval diagram and repeat steps 3 through 7.

When you the first add an individual user to an approval list, Stat automatically creates the ad hoc group “users” in the approval diagram and attaches it to the appropriate operator icon. All subsequent users you add to the list must belong to this group.


	TIP: In a scenario in which you want to create approval relationships between multiple user approver groups, you may consider adding users to new user classes or queues created expressly for this purpose.

(Optional) To add additional users, select the “users” group and repeat steps 3 through 7.

(Optional) Do any of the following to edit the diagram as needed:

•

To change an operator from AND to OR or from OR to AND, right-click on the icon.

•

To change the Required status of an approver, right click on it in the diagram. This changes required user classes and queues to optional with 1 required user.

•

To change the minimum number of user approvals in an optional user class or queue, double-click on the group label and specify the minimum number of user approvals you want.

•

To move approver groups or entire operator relationships, click and hold on the group label or operator icon and drag and drop to a different operator icon in the diagram.

•

To delete approver groups or entire operator relationships, click and hold on the group label or operator icon and drag and drop to the Trash Can icon.

Click OK or Apply.


	NOTE: The Required Approvals option on the Transfer Rules tab cannot be de-selected once a workflow has been saved with required approvers. To de-select the Required Approvals option after a workflow has been saved, you must first delete all the approvers in the Approval List and click Apply. At this point, you can de-select the Required Approvals option.

(Optional) To have Stat automatically transfer the status, right click on the transfer rule on the workflow diagram and select Auto Advance.

The Auto Advance option is only available on transfer rules that have approval lists applied to them. All transfer rules must be completed for an auto-advance to take place.

Also, be aware that setting the Auto Advance option on the two transfer rules from the same status (A>B and A>C) could create a conflict where both rules are satisfied at the same time the CSR is saved. When this is the case, Stat does not automatically transfer the status because it is not clear which transfer has precedence.

Click OK or Apply.

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:

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.

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.

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.

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.

If the Obj Control option has been selected for the workflow in the Workflow Maintenance table and you want to allow users to add and lock objects on a CSR while it is in selected status, select the option Allow Object Add/Lock.

If you do not select this option, users will not be able to add or lock new objects on a CSR while it is in the selected status. Object reservations that were in place when the CSR was transferred to the selected status, however, are converted into locks when the objects become available, as they would be normally.

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.

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.

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:

In the Workflow Maintenance window, select the workflow that you want to copy and click Copy Template.

Stat opens the Copy Template window.

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.

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.

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

(Optional) In the Migration Path field, select the migration path you want to assign to the workflow.

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.