Latest News

For Fall 2022, the user-initiated mass process services offered to campus will require the submission of a separate College, School, Unit (CSU) approval form via DocuSign along with each submitted processing request.

To support the university’s efforts to recruit and retain talent, approved Flexible Work Arrangements (FWA) can now be documented, tracked, and viewed within Workday.

Beginning April 21, Recruiters and Recruiting Coordinators will be able to create, manage, and send offer letters to candidates from within Workday with a built-in connection to DocuSign, allowing you also to collect signatures without printing and scanning.

If your office manages Academic Graduate Students (AGS) employees, remember that the AGS Mass Termination Process runs at the beginning of each semester. Be sure to extend any continuing AGS employees before the CSU processing deadline. 

Remember to check out the resources below, as you begin preparing for this year’s Performance Appraisals. Resources include materials for both employees and managers. Those who hold HR roles in Workday should make any necessary updates to the responsibilities on a position before launching a performance review by referring to the Updating the Responsibilities on a Position for Performance Appraisals Workday Instructional Guide (WIG)

We commonly use the terms Job and Position interchangeably, but there is a technical difference. Positions are separate business objects that we can create and modify without the necessity of a worker in the position. This distinction means that Positions may be unfilled, filled, or closed. Jobs, however, must always have a worker.

On February 7, the University Headcount – D0001 visualization in Tableau will become available. eBITS and IQ developed the new tool for viewing the unduplicated count of people in each supervisory organization at The University of Texas at Austin via the UT Data Hub in partnership with the Data to Insights initiative.

In Workday, people may be represented by three similar records. While these records may share some information, each has a different function within the system. Let’s illustrate this by following someone through the recruiting and hire cycle.

A transaction is a group of information that makes up an accounting entry. Some information is required on every UT accounting entry (i.e., account number, object class code, amount, etc.).  Some information is optional (i.e., DTN or *DEFINE codes, etc.).