This page (revision-12) was last changed on 26-Nov-2021 10:22 by kparrott

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
12 26-Nov-2021 10:22 3 KB kparrott to previous
11 26-Nov-2021 10:22 3 KB kparrott to previous | to last
10 26-Nov-2021 10:22 3 KB kparrott to previous | to last
9 26-Nov-2021 10:22 3 KB jmyers to previous | to last
8 26-Nov-2021 10:22 3 KB JEscott to previous | to last
7 26-Nov-2021 10:22 2 KB JEscott to previous | to last
6 26-Nov-2021 10:22 2 KB JMyers to previous | to last
5 26-Nov-2021 10:22 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 2 KB JMyers to previous | to last
3 26-Nov-2021 10:22 3 KB Administrator to previous | to last
2 26-Nov-2021 10:22 316 bytes Administrator to previous | to last
1 26-Nov-2021 10:22 305 bytes Administrator to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed 3 lines
!!!REPORT WORKFLOW ACTIONS
!!Report Processing Information
!!!REPORT WORK FLOW ACTIONS
At line 5 changed one line
# To report on the Workflow Actions,
# To report on the Work Flow Actions,
At line 13 changed one line
RMWF can now process ALL report workflow actions. It also now supports 2 of the 3 newer event recipients for email the WF action log report output to. It supports the current identity and the specific identity event recipients. It does not support emailing to a people list. When a Workflow Action for a Report is executed by RMWF it will email the report output back to the recipient designated in the workflow action log.
[{Image src='RMWF.JPG' width='600' align='center' link='attach/RMWF/RMWF.JPG'}]
At line 13 added 2 lines
RMWF can now process ALL report work flow actions. It also now supports 2 of the 3 newer event recipients for email the WF action log report output to. It supports the current identity and the specific identity event recipients. It does not support emailing to a people list. When a Work Flow Action for a Report is executed by RMWF it will email the report output back to the recipient designated in the workflow action log.
At line 19 changed 2 lines
!Emailing Batched Workflow Logs
Workflow logs for workflow actions that have an Event Type of "Email" and the toggle for "Process by RMWF with like Actions" turned on are ONLY sent when the RMWF function is run.
!Report Parameters
At line 22 changed 4 lines
These emails will be concatenated together into one single email IF the following three conditions are all met:
# They must be for the same workflow action (thus they have the same subject),
# They are all to the same recipient (id), and
# They are all coming from the same email address. This can be assured by using the From Email feature.
;Show Action Context: Select Yes if you would like to see the context of the workflow action. If not, then leave blank or select No.
;Process Event Action: Select Yes if you would like to process the workflow action event. If Yes is NOT selected, then the workflow action will not be processed.
;Due From Optional: This is a date field that specifies the due date of the workflow action event. Specifically this field indicates the beginning of a date range.
;Due To Optional: This is a date field that specifies the due date of the workflow action event. Specifically, this field indicates the beginning of a date range.
At line 27 changed one line
When more than one email body is enclosed within an actual email transmission, the subject will have "(+)" added to the end of it. Each email body will be separated by a line of underscores in order to be able to determine where one ends and the next begins.
!Report Filters
At line 29 changed 3 lines
%%information An individual workflow log email body has a maximum size of approximately 4000 characters and the concatenated email will have a maximum of approximately 32,000 characters.%%
----
!!Report Parameters & Filters
;Action: This is a field that is used to specify the workflow action event that is to be queried in the report. Multiple values can be selected for running with.
;Action Directed to: This field corresponds to the recipient type of the workflow action. Multiple values can be selected for running with.
;Type: This field specifies the type of action used for the workflow. Multiple values can be selected for running with
At line 33 changed 5 lines
||Report Parameters||
|Show Action Context|Select Yes if you would like to see the context of the workflow action. If not, then leave blank or select No.
|Process Event Action| Select Yes if you would like to process the workflow action event. If Yes is NOT selected, then the workflow action will not be processed.
|Due From Optional|This is a date field that specifies the due date of the workflow action event. Specifically this field indicates the beginning of a date range.
|Due To Optional|This is a date field that specifies the due date of the workflow action event. Specifically, this field indicates the beginning of a date range.
[{Image src='RMWF_Output.JPG' width='600' align='center' link='attach/RMWF/RMWF_Output.JPG'}]
At line 39 changed 4 lines
||Report Filters||
|Action|This is a field that is used to specify the workflow action event that is to be queried in the report. Multiple values can be selected for running with.
|Action Directed to|This field corresponds to the recipient type of the workflow action. Multiple values can be selected for running with.
|Type|This field specifies the type of action used for the workflow. Multiple values can be selected for running with
!Emailing Batched Work Flow Logs
Work flow logs for work flow actions that have an Event Media of "Email" and the toggle for "Event Batched" turned on are ONLY sent when the RMWF function is run.
At line 44 changed 3 lines
----
![Notes|Edit:Internal.RMWF]
[{InsertPage page='Internal.RMWF' default='Click to create a new notes page'}]
These emails will be concatenated together into 1 single email IF the following 3 conditions are all met:
# They must be for the same WF action (thus they have the same subject),
# They are all to the same recipient (id), and
# They are all coming from the same email address. This can be assured by using the new From Email feature noted above.
When more than 1 email body is enclosed within an actual email transmission the subject will have "(+)" added to the end of it. Each email body will be separated by a line of underscores in order to be able to determine where one ends and the next begins.
An individual Work Flow log email body has a maximum size of approximately 4000 characters and the concatenated email will have a maximum of approximately 32,000 characters.