REPORT WORKFLOW ACTIONS#

Report Processing Information#

There are a several purposes for running the RMWF report:

1. To report on the Workflow Actions,
2. To launch reports that were toggle to be run by RMWF,
3. To send emails that are now due to be sent, or
4. To send batched emails.

If you have need of any of points 2 through 4 then you will probably want to schedule the RMWF report to run everyday automatically.

Since "Batched" workflow actions are not processed until RMWF has been run, they will remain as "incomplete" in the workflow logs. They will only be indicated as completed after RMWF has been processed.

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.

IF no email address is found for the recipient then the report output will go to a file in the working directory named with the recipient information (exactly what depends on the recipient type) and the workflow action log id number.

The RMWF process should be scheduled to run periodically. Whether that is once per day or more or less will depend upon your business requirements.

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.

These emails will be concatenated together into one single email IF the following three conditions are all met:

1. They must be for the same workflow action (thus they have the same subject),
2. They are all to the same recipient (id), and
3. They are all coming from the same email address. This can be assured by using the From Email feature.

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.

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#

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.

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

---

Notes #

Click to create a new notes page