A new workflow custom function called P2K_CF_GET_DAPR_COMMENT was created for use in the workflow products such as WF_AAL, WF_SPA, etc. to look for any approval records that are tied to the subject record being changed and return the comment column.
Currently of the 23 approval areas only 12 have workflow products available. See chart below.
Approval Areas and Workflow Product Cross Reference
Value | Displayed | WF Product | WF Product Description | |
---|---|---|---|---|
01 | Disabled | |||
02 | Pay Trans Batches | WF_PBT | Work Flow – Batches | |
03 | Pay Header Batches | WF_PBT | Work Flow – Batches | |
04 | Performance Reviews | WF_SRV | Work Flow – Reviews | |
05 | Personnel Actions | WF_SPA | Work Flow – Personnel Actions | |
07 | Job Requisitions | WF_RPO | Work Flow – Postings | |
08 | Applicant Hires | WF_RAP | Work Flow – Applications | |
09 | Development Programs | |||
10 | Development Activity | |||
11 | Courses | |||
12 | Class Schedules | |||
13 | Training Resources | |||
14 | Benefit Elections | WF_BEL | Work Flow – BE Elections | |
15 | Assessments | |||
16 | Class Registration | WF_CRSE | Work Flow – Class Registrations | |
17 | Time Sheets | WF_PTS | Work Flow – Time Sheets | |
19 | Leave Lines | WF_AAL | Work Flow – Leave Lines | |
20 | Clock Entries ((Authorize) | WF_TCE | Work Flow – Clock Entries | |
21 | Education | |||
22 | References | |||
23 | Work History | |||
24 | Open Enrollment EEs | WF_BOEE | Work Flow – Open Enrollment EE | |
25 | Positions | |||
26 | Time Sheet Entries (Authorize) |
There could be multiple approval records out there for a subject record at any point in time, so records with the following approval statuses will be bypassed:
From there we will sort the records by the change date descending to ensure that the most recent change will be the one that triggered this.
In the example above, there is a check to see if the PA status has changed before anything is done. Then in this example, we are only dealing with Declined/Not Approved PA’s so we want to ensure that the status is for that. The actual custom function is called and the value of the found comment field is returned into the variable dapr_comment created. If the comment is left blank, an email is not sent. In this case, you may want to have one action line (email content) for when a comment is supplied and a different one for when a comment is not supplied.
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation