WORKFLOW

Run report

Use a Run report object to start report generation when the event defined in the Event rule occurs. The objects found by the Event rule will be used as the context when the report is generated.

In the Run report configuration you can specify where the report should be stored and/or to whom it should be sent.

Corporater BMP prioritizes the generation and distribution of reports. Report requests that originate from the Web take priority over reports that originate from Configuration Studio. In turn, report requests that originate from Configuration Studio take priority over scheduled and workflow-generated reports.

Configuring a Run report object

Create an Run report object by right clicking an Event schedule or Follow-up schedule and choosing Add -> Action -> Run report.

Properties

General

Name - the name of the object; "Run report" is generated automatically but it may be changed
Description - an optional text describing the object

Configuration

Report - the report that is to be generated; click the icon to the right to choose a report that already exists in Reporter
Report name - the name of the report to be distributed. The name may contain a token string, a function that results in a number, and/or a date function. By default it is made up of the elements below but you may change it. Click the icon on the right to choose other elements, e.g. organization name.
- ${report.name} - the name the report object has been given
- ${this.eop.long} - the period the report is generated for (Reporting period) written in long format

File type - choose the file type in which to store the report
- Microsoft Office format
- PDF format
Resource category - click the icon to the right button to the right to select the category in Resources where the report should be stored. The category must already exist. If nothing is entered, the report will not be stored.
Include all results in one report - when checked and more than one object meets the conditions in the Event rule, all results will be included in one report per recipient

The model object that the Event rule finds will be set for the report and used as filtering reference in Resource lists. If the Event rule finds three objects, three reports will be generated, each with its own reference. If Include all results in one report is selected, only one report will be created, with the first object found as reference.

Multiple Excel sheets or Presentations cannot be combined in one file. So when Excel files or Presentations are generated with the Include all results in one report selected, a single e-mail with an attachment for each file will be made.

Recipients

E-mail Users/Groups - click the icon on the right and choose the user(s) and/or group(s) who should receive the e-mail
Referred recipients - here you will see a list of properties that belong to the object type selected in Event rule and that contain users, e.g.
- Responsible - the user(s) who are responsible for the object(s) found by the rule
- Modified by - the user who last modified the object
- Created by - the user who created the object originally

Object owner is not available as a Referred recipient.

E-mail addresses - a comma-separated list of recipients you wish to send the e-mail to. The list may consist of e-mail addresses or refer to fields on the queried objects to supply the e-mails or both. Click to the right to open a new panel. When you select the context variables to include, dynamic tags containing them will be added to the list, e.g. ${this.user.EMail}. Remember that the result must be a comma-separated list.

Tags should not contain white spaces, especially between $ and {.

E.g. $ { this.object.id } could be misinterpreted. The correct syntax is ${this.object.id}.

Content

Subject - the text to be displayed in the e-mail's Subject field
Message - the content of the e-mail that will be sent.

Enter any text you want in the text area of these two fields, or click on the to the right to bring up a new panel containing a rich text editor where you can enter text and select dynamic (token) tags to include in the text. Reporter Token tags such as ${repeat}, ${endRepeat}, and ${url} are also available.

Tags should not contain white spaces, especially between $ and {.

E.g. $ { this.object.id} could be misinterpreted. The correct syntax is ${this.object.id}.

Audit

Modified by - the name of the last user to make changes to the object.
Last modified - the date and time when the object was last changed.
Created by - the name of the user who created the object.
Created - the date and time when the object was created.

Advanced

ID - a unique ID for the object.

By default, Corporater BMP assigns consecutive numbers to new objects.

You can change the ID to a value of choice that can include either letters or letter and number combinations.

The ID mustn't contain only numbers, include special characters such as ) ( . * } { + < > [ ], or match the name of a default object type in Corporater BMP.

Access control

Read accessors - click the Edit button () and authorize one or more users and user groups to view the object on Web.
Add accessors - click the Edit button() and authorize one or more users and user groups to add new objects to the object on Web.
Write accessors - click the Edit button() and authorize one or more users and user groups to edit the object on Web.
Delete accessors - click the Edit button() and authorize one or more users and user groups to delete the object on Web.
Ownership - click the Edit button () and grant ownership of the object to one or more users and user groups.

Users and user groups who own the object have full access rights to it.
Override access profile - select for the object's access control setting to outrank the object's corresponding access settings in profiles.