This page (revision-54) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
54 26-Nov-2021 10:22 12 KB Kevin Higgs to previous
53 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
52 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
51 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
50 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
49 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
48 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
47 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
46 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
45 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
44 26-Nov-2021 10:22 12 KB kparrott to previous | to last
43 26-Nov-2021 10:22 12 KB kparrott to previous | to last
42 26-Nov-2021 10:22 12 KB kparrott to previous | to last
41 26-Nov-2021 10:22 12 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
IMWA
IMWA

Version management

Difference between version and

At line 1 added one line
[{TableOfContents }]
At line 3 removed 2 lines
[{TableOfContents }]
At line 9 changed one line
The data for IMWA is defined on the [P2K_AM_WORK_FLOW_ACTIONS] and [P2K_AM_WORK_FLOW_LOGS] tables.
The data for IMWA is defined on the [P2K_AM_WORK_FLOW_ACTIONS] and [P2K_AM_WORK_FLOW_LOGS] tables
At line 11 changed one line
;[Action|EVENT_CODE]:Action is a user-defined code that uniquely identifies the workflow action item. Action is tied to the database column Event_Code which is a 16 character alphanumeric mandatory field that must be manually entered. It is through the event code that the workflow action is referenced in a workflow UserCalc.
;[Action|EVENT_CODE]:Action is a user-defined code that uniquely identifies the workflow action item. Action is tied to the database column Event_Code which is a 16 character alphanumeric mandatory field that must be manually enter. It is through the event code that the workflow action is referenced in a workflow UserCalc.
At line 15 changed one line
%%information Only the workflow actions that have a status of 'In Production' are available to be added to [UserCalcs|USERCALC]. But once they are included in a UserCalc just changing their status will NOT stop them from being used.%% \\ \\
%%information Only the workflow actions that have a status of 'In Production' are available to be added to [UserCalcs|USERCALC]. But once they are included in a UserCalc just changing their status will NOT stop them from being used.%%
At line 17 changed one line
;[Triggered In Product|WORKFLOW PRODUCTS]:This field defines the table that contains the workflow triggers. See overview for list of tables available.
;[Triggered In Product|WORKFLOW PRODUCTS]:This field specifies the table that contains workflow triggers. See overview for list of tables available.
At line 21 changed one line
%%information With respect to emails, it is important to have the email addresses set up on the appropriate screens in order for the system to use the address when issuing the email.%% \\ \\
%%information With respect to emails, it is important to have set up the email addresses on the appropriate screens in order for the system to use the address when issuing the email.%%
At line 23 changed one line
For both 'Employee' and 'Manager' these can only be used from tables with a link to the [P2K_HR_EMPLOYMENTS] table.
For both 'Employee' and 'Manager' these can only be used from tables with a hook to the [P2K_HR_EMPLOYMENTS] table.
At line 25 changed one line
;[Category|EVENT_CATEGORY]: This is a user-defined field that uniquely identifies the category the workflow action belongs. This field is for information purposes only and has no functionality behind it. There is only one supplied option (Not Specified) to select from, however, users can create new lexicon values accordingly.
;[Category|EVENT_CATEGORY]: This is a user-defined field that uniquely identifies the category to which the workflow action belongs. This field is for information purposes only and has no functionality behind it. There is only one supplied option (Not Specified) to select from; however, users can create new lexicon values accordingly.
At line 27 changed one line
;[Type|EVENT_MEDIA]: This field defines the type of media that is to be used to communicate the event action. There are several types of media to choose from.
;[Type|EVENT_MEDIA]: This field indicates the type of media that is to be used to communicate the event action. There are several types of media to choose from.
At line 31 changed one line
;[Report Parm Set]: The LOV contains a list of all [parameter sets|PARAMETER SETS] that were created. For example, if the type is set to Reports, the report is for [USPA], and a user has created a specific parameter set for [USPA], then that parameter set can be defined.
;Report Parm Set: The LOV contains a list of all [parameter sets|PARAMETER SETS] that were created. For example, if the type is set to Reports, the report is for [USPA], and a user has created a specific parameter set for [USPA], then that parameter set can be specified.
At line 33 changed 2 lines
;[Process by RMWF with like Actions|EVENT_BATCHED]: If this toggle is checked, the workflow action event is batched and will only be sent when the [RMWF] process is run. Example: in order to prevent a user from being bombarded with emails each time a workflow action occurs, this toggle is turned on so that the emails are sent to the user only once, when the [RMWF] process is run. This allows users to run the process at a specific time. The workflow action items are sent only once after this process is run. This toggle is used only with Emails or Reports types.\\
%%warning Note: __Action Directed__ to ''Department Co-ordinator'' cannot be batched together.%% \\ \\
;[Process by RMWF with like Actions|EVENT_BATCHED]: If this toggle is checked, the workflow action event is batched and will only be sent when the [RMWF] process is run. For example, in order to prevent a user from being bombarded with emails each time a workflow action occurs, this toggle is turned on so that the emails are sent to the user only once, when the [RMWF] process is run. This allows you to run the process at a specific time. The workflow action items are sent only once after this process is run. This toggle is used only with Emails or Reports types.
%%warning
Note that __Action Directed__ to ''Department Co-ordinator'' cannot be batched together.
%%
At line 36 changed one line
;[Process Until Marked as Completed|RESPONSE_REQUIRED]: This toggle can be used in conjunction with the toggle above and a completion clause to keep sending an email out every time the [RMWF] is run until the completion clause is satisfied. See section below on [Nagging Workflow Log Emails|CONTINUOUS WORKFLOW LOG EMAILS].
;[Process Until Marked as Completed|RESPONSE_REQUIRED]: This toggle can be used in conjunction with the toggle above and a completion clause to keep sending an email out every time the [RMWF] is run until the completion clause is satisfied. See section below on [Nagging Workflow Log Emails|NAGGING WORKFLOW LOG EMAILS|CONTINUOUS WORKFLOW LOG EMAILS].
At line 42 changed one line
This tab provides the user with the ability to enter an SQL select statement for the completion clause.
The tab provides the user with the ability to enter an SQL select statement for the completion clause.
At line 44 changed 2 lines
;[Text|EVENT_TEXT]:A completion clause is required in order to close the workflow loop. An SQL select statement can be entered here, if the value in the select statement is returned, the workflow action is complete. If no value is returned, then the workflow action item remains incomplete. \\ \\%%information Note: The value is arbitrary BUT must be only one single value (or column).%% \\
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. \\ \\
;[Text|EVENT_TEXT]:A completion clause is required in order to close the workflow loop. An SQL select statement can be entered here such that if the value in the select statement is returned, the workflow action is complete. If no value is returned, then the workflow action item remains incomplete. %%information Note that the value is arbitrary BUT must be only one single value (or column).%%
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.
At line 54 changed one line
If a user presses OK to this message, the record is saved. If this message appears, users should copy the SQL script that is being entering in IMWA and execute it in SQLPlus to see if there are any errors. \\ \\Once you have a clean SQL script, copy it into IMWA. Users should not receive the error messages previously noted. \\ \\
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.
At line 56 changed one line
To use a completion clause, users only have the ID for the record that triggered the log to be written. This ID MUST be used in the clause. Example: A completion clause for WF_RAP would need to use ":RAP_ID" in the completion clause.
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.
At line 60 changed one line
Users cannot 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. Example:
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:
At line 70 changed one line
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. \\ \\
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.
At line 72 changed one line
%%warning This tab is for viewing purposes only. Users cannot edit the data.%% \\ \\
%%warning This tab is for viewing purposes only; you may not edit the data.%%
At line 78 changed one line
* Cancelled - Indicates that the workflow action has been cancelled.
* Cancelled - Indicates that the workflow action has been canceled.
At line 80 changed one line
;[Assigned on|ACTION_ASSIGNED_DATE]: This field indicates the date the event action was assigned. Example: If a candidate applied for a posting on February 1st, then the workflow action event was fired on February 1st. Therefore, February 1st will populate this field.
;[Assigned on|ACTION_ASSIGNED_DATE]: This field indicates the date on which the event action was assigned. For example, if a candidate applied for a posting on February 1st then the workflow action event was fired at that moment. Therefore, in our example this is the date that will populate this field.
At line 82 changed 2 lines
;[Completed On|ACTION_COMPLETION_DATE]: Indicates the date the workflow action was completed.
;[Assigned To|DRV_RECIPIENT]: This field corresponds to the recipient of the workflow action. \\ \\
;[Completed On|ACTION_COMPLETION_DATE]: Indicates the date on which the workflow action was completed.
;[Assigned To|DRV_RECIPIENT]: This field corresponds to the recipient of the workflow action.
At line 85 changed one line
%%warning NOTE: Assigned To will not populate when the Action Directed to is set to a People List%% \\ \\
%%Assigned To will not populate when the Action Directed to is set to People List%%
At line 89 changed one line
If the workflow is for sending emails, then the address(es) it was sent to will be added to the bottom of the Reference Info after it has been sent.
If the workflow is for sending emails then the address(es) it was sent to will be added to the bottom of the Reference Info after it has been sent.
At line 92 changed one line
If a Workflow email cannot be sent because either a FROM or TO email address cannot be found or is invalid, the Workflow log will be marked as 'Cancelled' with the completed date filled in. This prevents the system from repeatedly trying to process a workflow log that cannot be processed.
If an Workflow email cannot be sent because either a FROM or TO email address cannot be found or is invalid, the Workflow log will now be marked as 'Canceled' with the completed date filled in. This will prevent the system from repeatedly trying to process a workflow log that cannot be processed.
At line 97 changed one line
The 'Used In' tab maintains a list of the User Calcs that this workflow is referenced in. \\
The 'Used In' tab maintains a list of the User Calcs that this workflow is referenced in.
At line 99 changed one line
%%warning This tab is for viewing purposes only. Users cannot not edit the data.%%\\ \\
%%warning This tab is for viewing purposes only; you may not edit the data.%%
At line 104 changed 6 lines
* 00: Under Construction – the user calc has not been completed and therefore will not be published
* 10: Pre-compiled
* 20: Being Tested
* 30: To Be Published – The user calc is ready to be published
* 40: In Production – The user calc has been published and is in use
* 99: Compiling
* 00-Under Construction – the user calc has not been completed and therefore will not be published
* 10-Pre-compiled
* 20-Being Tested
* 30-To Be Published – The user calc is ready to be published
* 40-In Production – The user calc has been published and is in use
* 99-Compiling
At line 111 changed 6 lines
;[Usage|USER_CALC_USAGE]: This field defines how the user calc is to be used in the application. Values are:
* 00: Not Specified
* 01: Disbursement Message – The user calc will be executed for each disbursement record when [UPDISB] is run.
* 02: Secondary WF - This selection is used for workflow user calcs which will not be fired from the trigger directly and must be called from another user calc.
* 03: Pro-Active WF – The user calc will be executed when [UMPWF] is run.
;[Line|USER_CALC_LINE]: This defines the line in user calc that the workflow is referenced in.
;[Usage|USER_CALC_USAGE]: This field specifies how the user calc is to be used in the application. Values are:
* 00-Not Specified
* 01-Disbursement Message – The user calc will be executed for each disbursement record when [UPDISB] is run.
* 02-Secondary WF - This selection is used for workflow user calcs which will not be fired from the trigger directly and must be called from another user calc.
* 03-Pro-Active WF – The user calc will be executed when the [UMPWF] is run.
;[Line|USER_CALC_LINE]: This is identifies the line in user calc that the workflow is reference in.
At line 121 changed one line
The 'Attachments' tab is used to maintain the names of the files (attachments) that are linked to the workflow. The attachments can be entered with a Start and End date, which will allow the files to be picked up only during this timeframe.
The 'Attachments' tab is used to maintain the names of the files (attachments) that are linked to the workflow.
At line 124 added 2 lines
The attachments can be entered with a Start and End date, which will allow the files to be picked up only during this timeframe.
At line 127 changed one line
With the addition of the new tab contents for an attachment, the use in a workflow email does not change. The workflow is built in the same manner as normal, the Description on the Act line is still the body of the email.
With the addition of the new tab contents for an attachment, the use in a work flow email does not change. The work flow is built in the same manner as normal, the Description on the Act line is still the body of the email.
At line 132 changed 3 lines
;[Start Date|START_DATE]: This field defines the start date of when the attachment file will be available for the workflow.
;[End Date|END_DATE]: This field defines the end date for when the attachment file will no longer be available of the workflow.
;[Attached|ATTACHMENT]: This field holds the name of the file that is to be attached to the workflow. The file can be added or removed from this field as needed.
;[Start Date|START_DATE]: This field identifies the start date of when the attachment file will be available for the workflow.
;[End Date|END_DATE]: This field identifies the end date for when the attachment file will no longer be available of the workflow.
;[Attached|ATTACHMENT]: This field holds the name of the file that is to be attached to the work flow. The file can be added or removed from this field as needed.
At line 136 changed one line
;[Mime Type|MIME_TYPE]: This field is used to identify the data type of the attached file. Example: The mime type can be a docx, txt, pdf, jpg, etc.
;[Mime Type|MIME_TYPE]: This field is used to identify the type data of the attached file. For example, the mime type can be a docx, txt, pdf, jpg, etc.
This page (revision-54) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop