• The CHRS Library - Security Page provides a full list of Dynamic roles, Baseline CHRS Security roles and the CHRS Security Plan and Requirements for review.
• Majority of the roles for Absence Management will begin with CHR_AM
• There are four dynamic roles available for Absence Management.  These roles will be automatically provisioned (assigned) and deprovisioned to employees who meet the predefined criteria set by CHRS. 

• Determine users on your campus who are responsible for the various AM tasks and work with the security team to have the applicable security roles assigned to them.
  • Configuration
  • Payroll
  • Approver
  • Timekeeper

Each campus will have their own holiday schedule converted over from the 9.0 system. There will be a standard "NONE" schedule that contains no holidays that can be assigned to student employees or other groups that are not eligible for holidays. 

It is the campuses responsibility to 

• Confirm the converted Holiday Schedule follows the standard CHRS naming convention.
• Include any current, and future (if applicable) holidays that where not included in conversion.

Job Aid - Holiday Schedule Setup

Schedules can be assigned to an employee using either a predefined work schedule or a personal schedule. 

Job Aid - Assign Work Schedules

Off work periods are defined by pay group (for example: academic year workers). A single year can have multiple non-working periods.

Job Aid- No Leave Taken (NLT) Non-Working Period Setup

• Campuses that use the reports-to chain for absence and time approvals must delegate approvals when the approver is away for an extended time or during critical time management periods.
• Only an Administrator can delegate approvals to a different approver during a specified time period.

• During the specified time period, all transactions that require approval are automatically routed to the proxy approver.

Job Aid - Delegate Absence Approvals (Administrator)

Open a ServiceNow ticket using the example campus configuration document, update for your the template with your campus information based on what should be migrated from each pass through MTP. 

When submitting the ticket: 

• Type: Request

• Category: CMS-CHRS

• Subcategory: Absence Management

• Ticket Short Description: 

  • In the ticket short description, indicate that the campus name, the module, and the Pass/MTP this is requested for. (Example: CHI - AM Config - MTP)

• Description: 

  • The description section should include the following:

    • Database Name (Example: HACHRSIT to HCHRPRD)

    • Reason (Example:  Conversion from Pass C  to MTP)

    • Pages to migrate

    • Attachment Title

• Attachments:

  • Include an attachment with all the details of what your campus needs to have migrated. The attachment should look similar to the example below.