If you need to enter more than the allowed number of appointments that can have the same appointment number and appear on the same Appointment Notification, they will need to process the first set of appointments and then return to the appointment data entry page to process the additional appointments.

Depending on where the appointment is in the workflow, you will need to coordinator with the correct individual to have the appointment fully canceled. Once the appointment is fully canceled, you will be able to resubmit the transaction.

Depending on where the appointment is in the workflow, you will need to coordinator with the correct individual to have the appointment fully canceled. Once the appointment is fully canceled, you will be able to resubmit the transaction.

At this point the module does not review nor confirm enrollment eligibility, it is up to the campus to verify the eligibility before entering the record into the mod.

If the same Final Approver approves multiple transactions for different EE Groups within 7 minutes, the different EE Groups will appear on the same Load to Job Report that appears after the Final Approver approves.

If the Final Approver approves a transaction that has the “~Manual Load to Job” option in the Other Action field and then approves other transactions, within a 7 minute window, the Action/Reason will appear blank for the transaction that had the “~Manual Load to Job” option in the Other Action field on the Load to Job Report that appears after the Final Approver approves.

It is recommended that the final approver review all fields on the My Approval page before loading the transaction to job.

Data Entry users will be unable to enter a transaction for an employee that does not have a BUSN email address provisioned. Campuses will want to make sure that they are working with their provisioning team, to ensure that rehires and new hires (i.e., Future Hire POI’s) are able to access CHRS prior to being entered into Job Data, otherwise the employee will be unable to acknowldge their notification. (Example: Email, Single Sign on)

Campuses will want to make sure that they are working with their provisioning team, to ensure that rehires and new hires (i.e., Future Hire POI’s) are able to access CHRS prior to being entered into Job Data, otherwise the employee will be unable to acknowldge their notification. (Example: Email, Single Sign on)

 It is recommended that campuses edit the Workflow Steps for the existing workflow unless the changes they are making involve differentiating between job codes and departments. When the change involves adding a step to the workflow, users will need to add the step at the end of the workflow and relabel the prior steps.

You should delete all the steps in the inactive workflow except for the originator step, then create a new workflow that is at least the month higher than the original workflow inactivated. 

Yes. 

 Submit a ServiceNow Ticket with your new logo attached.

Values on the table are never removed, only inactivated due to the standardization of the table. Although the table is standardized each campus has their own version under their campus business unit that can be modified by submitting a ServiceNow ticket.

Values on the table are standardized and would require a Change Control to be submitted to have new values added.