Stat 6.3 - User Guide

Transfer Rules

Transfer rules define conditions which must be met before you can move a CSR from one status to another. A transfer rule can stipulate the following:

NOTE: The user class right, Status Transfer Override, enables users to perform status changes even if the transfer rules are incomplete.

In the diagram, status icons are connected by lines with arrows that indicate the direction or sequence in which you can change the CSR from one status to another. A hollow arrow signifies the transfer is set to be auto-advanced if all required approvals and other conditions of the rule are met, while a two-tone arrow signifies that it is advanced by the user. A square at the tip of an arrow indicates the presence of transfer rules. A hollow square indicates that the transfer rule is incomplete, while a solid square means all transfer rules are completed. The color of the arrow works similar to a traffic light. Red means the transfer cannot occur; green means transfer can occur. Black means that the transfer has no rule or it is not yet to be processed.

To view the details of the transfer rules, double-click on the arrow. This opens the Transfer Rules Status window.

The Transfer Rules tab displays a summary of the rules defined for the transfer. It also shows whether the conditions of the rules are complete. The tab displays the words “In Process” until all the rules are marked complete and any approvals have been granted. When all the conditions for the transfer have been met, the tab displays “Complete.”

Transfer Approval Lists

If the transfer requires user approval, the second tab of the window, Approval List, displays the name of each user who can approve the transfer. The list can include individual users, entire user classes, queues, or a combination of the three. Also, the approval of any user, user class, or queue can be either required or optional. Required approvers are displayed in bold.

A green check mark indicates that the user has approved the status transfer, whereas a red X indicates that the user has rejected the status transfer, thereby preventing the status transfer from taking place until the rejection status has been resolved.

NOTE: A status transfer cannot go forward if just one approver rejects the status transfer, even if that user’s approval is not otherwise required. Before the status transfer can occur, either the user or another user authorized to override status transfer 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:

TIP: You can also approve status transfers in the Status Transfer Approvals window. For more information, see Approving Status Transfers .

System administrators can configure workflow rules so that requests to approve a status transfer are not generated until all the other rules defined for the status transfer (if any) have been marked as complete. This ensures that a status is ready to be transferred before users are asked to approve it and reduces the number of approval requests open at any one time.

If the delayed approvals option has been selected, the Approval List tab for a particular status will be empty until all the other transfer rules are completed. Once status is ready to be transferred, a user can generate the approval requests either by transferring the status using drag-drop, (as described in the section, Transferring Statuses ) or by opening the Transfer Rules Status window. Users with proper security rights can override the delayed approvals configuration and generate approval requests by clicking Generate. This button is only enabled for users that have been assigned the user class right, Status Transfer Approval Generate.

NOTE: Once the approval list has been generated, the Generate button changes to Regenerate.

If you want to notify users about status transfers 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, class, or queue 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 or queue. 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 status transfer 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 status transfer. 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 will be automatically populated and the Update By field will display the value, Via Email.

Approval notification reminder messages can also be sent for migrations and Oracle Apps patch applications. For more information, see the Stat System Administration Guide, Chapter 7, “Email Configuration.”

Occasionally one of the classes or queues designated to approve status transfers needs to be updated, either because new users have been added to the class or queue or existing users have been removed. When this is the case, you can update the approved users list based on class or queue by clicking Regenerate. This removes obsolete users belonging to a class or queue from the list and adds new ones. It also resets approval statuses to Pending.

NOTE: Clicking the Regenerate button only affects users belonging to classes or queues and is enabled only for users that have been assigned the user class right, Status Transfer Approval Refresh.

A log entry is generated each time a status transfer is rejected. Click View Log to view any log history for the status transfer. The Approver Name column records the actual person who did the approval, not the person the approval was originally assigned to. The log records if the actual approver is not the designated approver, i.e., when a user with the override security right rejects a status transfer on behalf of someone else.

Transfer History

In the Transfer History tab, you can view the time and date a transfer occurred between two statuses, as well as the ID of the user who performed the transfer. If the connection between the two statuses in the workflow is bi-directional, meaning that the CSR can go to one status and then back again, a separate record is kept each time the transfer takes place, as indicated in the Seq No column.

If a transfer required user approvals, you can view a transfer approval history from the Transfer History tab. To view the approval history for a transfer, right-click on the transfer and in the pop-up menu, select View Transfer Approvals. This opens the Approval Rules History window, which displays a list of all the users who approved the transfer and when their approvals were made.

Status Rules

Status rules apply restrictions to a CSR while it is in a particular status, such as what queue(s) it can belong to, to what environments you can migrate the objects associated with the CSR, and for the Oracle Applications only, to what environments you can apply a patch.

In a workflow diagram, the presence of a status rule is indicated by an asterisk displayed next to the name of the graphic representing the status. To view the details of status rules, double-click on the graphic. This opens the Status Rules window.