Skip to content

Overview and General Information#

ACCE (Automation Change Control Expert) is a third-party tool hosted by OIT that provides functionality for migrating AutoSys job definitions. It provides a way to allow for AutoSys job changes in a controlled manner with auditing and separation of duties.

ACCE Login page

How it's used here at the U#

An ACCE Change Request, shorthand CR, will be created to migrate AutoSys job definitions from TST, to QAT*, and finally to PRD.

ACCE is not used to create or modify jobs - only migrate jobs between instances in one direction - TST>QAT>PRD.

ACCE allows for configuration to enforce rules on values chosen for AutoSys job definitions. And, it allows for generating rules to automatically convert AutoSys job field values as things migrate. For example, convert the phrase cstst to csqat in a file path.

Whenever you need an AutoSys job definition changed (or newly created) the JST team will do the work for you per your TDX ticket request. Then, either you or JST can create the ACCE Change Request to have the jobs moved from TST to QAT, and finally to PRD. In general, JST wants to avoid making changes directly to jobs in Production.

* Informatica jobs only have a TST and PRD instance, no QAT.

Access#

There are three roles in our implementation of ACCE:

  • Requester: Lowest level of access. Requester is allowed to create a new change request to request migration of a list of AutoSys jobs out of TST. A requester cannot review/approve or migrate CRs. They will only be able to add jobs to the CR if the job begins with the same characters corresponding to their business unit.
  • Reviewer: A reviewer can review and approve CRs, but not migrate or create a CR.
  • Migrator: The JST team will be responsible for all migrations of approved CRs.

Getting Access#

Access to ACCE is controlled by adding a user's internet ID into a business unit's Autosys Grouper group(s). See this article for granting users access to be able to create ACCE change requests and for reviewing change requests.

If a person is included in both the Dept Users and Reviewer Users groups for a business unit they will be able to create a CR and review/approve their own CR. JST leaves the decision of what staff belong to which AD group, and hence ACCE role, up to each business unit.

Here is a current list of valid business units set up in ACCE:

  • SCHD (Production Scheduling)
  • CSAD (CS Admissions)
  • CSSF (CS Student Finance)
  • CSSR (CS Student Records)
  • CSSA (CS Academic Advising)
  • CSFA (CS Financial Aid)
  • HRMS (HR Human Resources)
  • FS (FS Financial Services)
  • CSCC (CS Campus Community)
  • CSMS (CS Measurement Services)
  • CSGS (CS Grad School)
  • INFI (Integrations Team)
  • IHPT (IH Portal)
  • ITSA (OIT PeopleSoft Security or System Administration)

High-level Change Request cross-functional diagram#

In the diagram below, yellow boxes are actions taken via button clicks. Blue boxes are resulting CR status values.

See Change Request - How To for more details on how to create a change request in ACCE.

High-level Change Request cross-functional diagram