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

Version management

Difference between version and

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. 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 that __Action Directed__ to ''Department Co-ordinator'' cannot be batched together.
%%
At line 44 changed one line
;[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).%% \\
;[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).%% \\ \\
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, users 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. 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; users cannot edit the data.%% \\
At line 83 changed one line
;[Assigned To|DRV_RECIPIENT]: This field corresponds to the recipient of the workflow action. \\ \\
;[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%% \\ \\
%%NOTE: Assigned To will not populate when the Action Directed to is set to a People List%%