Activity or Activity codes
A category of tasks and auto tasks. Example: Invoicing or documentation.
A subdivision of a service domain. Example: PeopleSoft or MS Office.
A snapshot of a set of objects that have been grouped together for archiving purposes. There are three types of archive sets: Base, Interim, and Final.
The Stat user who has been assigned to a CSR. Available users depend on the queue selected.
Tasks that Stat automatically adds to a CSR. They are triggered by the selection of Applications, Types, and Statuses.
Base Archive Set
The original snapshot of the objects in the Base environment. Objects in the base archive set always originate in the Base environment. Only one base archive set exists per CSR.
The source environment from which the base archive set originates. All objects in the base archive set are from the Base environment. This is a PeopleSoft environment.
A rule that triggers an email to a distribution list when a CSR corresponds to the user-defined event.
Change Management Module
The change management support modules provided by Stat for PeopleSoft, Oracle Applications, and generic applications.
The recommended number of CSRs that an item can have open at one time. An item can be a user, queue, department, or application. The number is defined by the system administrator. The number appears on an item’s meter in the Enterprise Console.
Stands for Change/Service Request. This a request made by a customer or user that is documented and resolved in Stat. A CSR can belong to only one service domain and can have an unlimited number of tasks defined on it.
The person who reported the request/problem. Customers may or may not be Stat users. Depending on the business environment, customers can be internal or external.
User-defined or third party data sets developed for specific application environments.
The business division or organization to which the customer belongs. This can be an outside company name or an internal department within a business.
The environment in which object development occurs.
A database as well as the file servers and file paths associated with it. Also, a subdivision of an application. Its use is optional by application. Example: A/R for PeopleSoft application or Excel for MS Office application.
File type objects (also called flat files), such as SQL and COBOL files. In Stat, file objects (as well as PeopleSoft proprietary objects) can be included in an archive set and migrated from one PeopleSoft database or generic application environment to another.
Final Archive Set
The final snapshot of all objects taken from the Development environment. The final archive set should be created after all changes have been approved. The final archive set should be migrated to all environments on the migration path so they are all in sync. Only one final archive set exists per CSR.
Any file-based application connected to Stat
A record of value changes maintained by Stat. These values can include transfers of CSR ownership, CSR status transfers, triggering of business and personal rules, and other of changes.
Interim Archive Set
An interim snapshot of objects while they are in the process of being modified. An unlimited number of interim archive sets can be created. Interims should be created from the environments in which objects were modified which would probably be Development. Interim archive sets should be migrated to one or many target environments for testing and evaluation.
A grouping of tabs displayed on the Support Console.
A list of the activity volume for a group of like items on the Enterprise Console.
A term used in Stat to refer to both PeopleSoft proprietary objects and file objects.
PeopleSoft Proprietary Object
An object native to PeopleSoft, such as pages and records. In Stat, PeopleSoft proprietary objects (as well as file objects) can be included in an archive set and migrated from one PeopleSoft environment to another.
A rule that triggers an email to the user who created the rule when a CSR corresponds to the user-defined event. An email generated by a personal rule can only be sent to the creator of the rule.
The level of urgency associated with the CSR. The priority sets the due date of the CSR.
Project (in Stat)
A larger business process that groups an unlimited number of CSRs and tasks from various service domains. A project can be used to track a number of related CSRs from one location.
A group of users that possess a similar skill set. The assigned user must be a member of the current queue. Throughout the life of a CSR, ownership can be transferred to various queues. A queue is associated with a specific service domain. All members of the queue must have access to the associated service domain.
A schema object definition supported by Stat. Stat supports locking, archiving, and migrating schema object definitions on Oracle databases version 9i or higher and on MS SQL Server 2005/2008.
Service domains allow you to divide your business into logical units. CSRs can only belong to one Service domain and cannot be reassigned.
Source File Location
The file server plus the file path where file objects originally reside for an environment.
Stat Central Agent
The Stat component that does the actual processing of many behind-the-scenes activities, such as object locking and creating archive sets.
Stat Oracle Agent
A background daemon that runs on each Oracle Applications server. It receives requests from the Stat Central Agent, processes the requests, and sends resulting information back to the Stat Central Agent.
The current phase of a CSR.
An environment to which interim archive sets are migrated for testing and evaluation purposes. Examples of target environments are QA, Testing, and Training.
An individual step required to complete a CSR. A CSR can include many tasks. A task can be manually or system generated (auto task). Tasks cannot exist outside of a CSR.
A predefined data entry field on the Description tab. Templates are triggered by Applications and Types. They help save time and ensure data consistency.
The categorization of a CSR.
A person who uses Stat. A user can also be a customer.
A security level which determines a user’s access within a Service Domain. A user class is assigned rights. Rights exist for a variety of functions from editing fields on a CSR, creating archive sets, and accessing wizards.
Sets of rules that regulate the sequence and conditions by which CSRs can change from one status to another.
The file servers plus the file paths that are defined for individual users.