Currently, workflow triggers have been implemented on the following tables. Also noted here is whether you currently can access the Identity pointed to on an Employee's Prime Assignment ||Product || Table ||Access to Employee Supervisor | WF_AAL | [P2K_AT_LEAVE_LINES] | Yes | WF_BEL | [P2K_BE_ELECTIONS] | Yes | WF_CCCU | [P2K_CP_COMPETENCE_USAGES] | Yes | WF_CRSE | [P2K_CP_CLASS_REGISTRATIONS] | Yes | WF_DAP | [P2K_CM_APPROVAL_LOGS] | No | WF_DAPR | [P2K_CM_APPROVAL_RECORDS] | No | WF_EAS | [P2K_HR_ASSIGNMENTS] | Yes | WF_EASD | [P2K_HR_ASSIGNMENT_DETAILS] | Yes | WF_EEM | [P2K_HR_EMPLOYMENTS] | Yes | WF_EID | [P2K_HR_IDENTITIES] | Yes | WF_EPS | [P2K_HR_PERSONALS] | Yes | WF_HIN | [P2K_SH_INCIDENTS] | Yes | WF_LDA | [P2K_LR_DISCIPLINARY_ACTIVITIES] | Yes [1] | WF_LDI | [P2K_LR_DISCIPLINARY_ISSUES] | Yes | WF_MEX | [P2K_AM_EXECUTIONS] | No | WF_MRE | [P2K_AM_REQUESTS] | No [2] | WF_PPRC | [P2K_PR_CDN_PAY_RULES] | No | WF_PPRD | [P2K_PR_PAYMENT_RULE_DETAILS] | No | WF_PPRU | [P2K_PR_US_PAY_RULES] | No | WF_PTS | [P2K_PR_TIME_SHEETS] | Yes | WF_RAP | [P2K_RE_APPLICATIONS] | No | WF_RASE | [P2K_RE_ASSESSMENT_EVENTS] | No | WF_RCA | [P2K_RE_CANDIDATES] | No | WF_RPO | [P2K_RE_POSTINGS] | No | WF_RQL | [P2K_RE_QUALIFICATIONS] | No | WF_SPA | [P2K_SA_PERSONNEL_ACTIONS] | Yes | WF_TCE | [P2K_TS_CLOCK_ENTRIES] | Yes | WF_TRE | [P2K_TS_WORK_RESTRICTIONS] | No | WF_TTX | [P2K_TS_TIME_EXCEPTION] | Yes [#1] P2K_LR_DISCIPLINARY_ACTIVITIES uses the Employee linked through the Disciplinary Issue for ALL Employee related information rather than the "Reviewer" of the Activity. [#2] P2K_AM_REQUESTS uses the EID table to access the information on the person the request is coming from and the EID_SUP table to access the information on the person the request is going to.