A workflow action is the result of a key event. Some key events can include a salary/wage increase or hiring/terminating an employee. These events require specific actions to occur, thereby driving the workflow process.
The workflow event action is defined in the Define Workflow Actions (IMWA) screen.
For both 'Employee' and 'Manager' these can only be used from tables with a hook to the P2K_HR_EMPLOYMENTS table.
Under Construction Indicates that the workflow action is being created and is not yet complete.
User | If this recipient type is used, ensure that the user has been set up properly in IMUS with the email address stated there (for workflow actions that are issuing emails). If the email address on the IMUS record is blank then IF there is a person filled in on the IMUS record the system will try to retrieve the email address from the "Employee". |
Employee, Manager, Current Identity or Specific Identity | If one of these recipient types is used, then ensure that the email address is stated on the person's Prime assignment record (IEAS). When an email is issued and this recipient type is used, the system will go to the employee's IEAS screen and read the email address from there. If there is no email address on the employee's Prime assignment, the system will go to their Personal Information (IEPI) to retrieve the email address. If their IEPI record does not have an email address, no email will be sent. |
Business Contact | If this recipient type is used, ensure that the contact has been set up on IECI with the email address stated there. It is important that the business contact have a contact type value of "Business Contact" for their IECI record in order to select the contact as the recipient type in the UserCalc. |
Candidate | If this recipient type is used, ensure that the email address is stated on the candidate's profile record IRCA. |
People List | If this recipient type is used; ensure that the email address is stated on the person's assignment record that the people list detail record points to. Again if no address is found on that assignment record, the person's information record will be checked for one. |
Reports | Launches a report. When this value is used the report that is specified is launched automatically (i.e. USPA) |
Forms | Launches an screen form (i.e. IEPI). |
Oracle Discoverer | Creates a list of subjects that Discoverer could report on. |
Message | Creates a task that is displayed on the Workflow Tasks Screen. |
Allows for emails to be issued from within the application. | |
ODBC | Creates a list of subjects that an ODBC link could merge from. When this event media type is used, a record is created with ties to the following views in the database: P2K_AM_VMWF_CONTACTS, P2K_AM_VMWF_IDENTITIES and P2K_AM_VMWF_USERS. These are views and the data within these can be reported on using Discoverer. |
Type Value for Field | |
---|---|
Reports | Report Function Name |
Forms | Form Function Name |
Oracle Discoverer | Discoverer Report |
Message | Leave blank |
From Email Address | |
ODBC | Leave blank |
For Forms, the value stored in this field will be the name of the function you are referencing. For example, if the intent of the workflow action is to navigate to the IPRLU screen then the field should be set to "IPRLU".
For Emails, If this column is filled in, then that is what will be used as the From Email address when the WorkFlow log is sent as an email. If this is left blank it works as follows:
The tab provides the user with the ability to enter an SQL select statement for the Completion Clause.
The exceptions to this are found in the example of an email being sent. In this case, no completion clause is provided, yet the workflow action is marked with a status of 'Completed' or in the case of just wanting to launch a form or report.
SQL statements can be difficult to write therefore we recommend that a person with SQL knowledge along with familiarity of the various tables within the database be responsible for writing these statements.
When entering a 'Completion Clause' on IMWA, if the SQL script is invalid or has error the following message will be shown:
"Event Text Error = ORA-00942: table or view does not exist ORA-06512: at P2k.P2k_SMREFCUR", line 8"If you then press OK to this message, the record is saved. If this message should appear take the SQL script you are entering in IMWA and execute it in SQLPlus to see if there are any errors. Once you have a clean SQL script, put this into the IMWA and then you will not receive the error messages previously noted.
To use a completion clause you only have one piece of information from the workflow log available to use and it MUST be used in the clause. That piece of information is the ID for the record that triggered the log to be written. For example, a completion clause for WF_RAP would need to use ":RAP_ID" in the completion clause.
SELECT 1 FROM P2K_RE_APPLICATIONS WHERE ID = :RAP_ID AND APPLICATION_STATUS = '80'
Due to changes in the Oracle9i Database, you can no longer specify "*" as the value in the select as in SELECT * FROM …. The value selected is arbitrary and not used for anything so it can be a column or a constant value BUT can only be a single value. For example:
SELECT 1 FROM …will work in every completion clause.
The 'Logs' tab maintains a history of the workflow actions and also provides the user the ability to view the workflow action in more detail.
An important note to remember is that every time a workflow action event takes place, a log is created. Therefore, reviewing the 'Logs' tab will indicate how many times the action event was fired. It is also a good place to review for testing purposes to ensure that the workflow action actually took place.
This tab is for viewing purposes only; you may not edit the data.There is no page called 'WF Emails That Cannot Be Sent'. Would you like to create it?
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