This process is part of the deep dive work the project and Subject Matter Experts (SMEs) will partner to define the business process, ensuring controls.
This business process needs to be defined as there will likely be some similarities because both current and future state use PeopleSoft design and permissions to access records and approve transactions.
Users will have view access to Job Data, so historical rows are visible. Forms are just a front end for adding transactions because UCPath is not allowing edit access to parts of the UCPATH system. The custom pay PayPath component brings together the ability to make Position + Job + Pay updates in one place.
Someone is a lecturer in the Spring January 1 to May 31. The department decides they will also teach July 1-August 30. Instead of terminating their position, the process would be to extend the appointment through August (end date August 30) and then put the employee on a Short Work Break from June 1 to June 30.
The list of Action/Reasons viewable during the demonstration in PayPath may have been limited by the type of employee, the tab being viewed (position or job or pay), and the action chosen.
The list viewed was not the full list which will be available in future transactions. More information about action/reason choices will be provided at a later date.
