Designing processes - EMC Community Network

Prototyping Business Activity Monitor dashboards
Figure 17
After
Including Business Data in your prototype
In a typical deployment of BAM groups of process instances can be analyzed over time. Trend reports
that capture the behavior of processes over time, like the one shown below, is a common dashboard
requirement. This report calculates the number of process instances that are started each day during the
last week. This type of calculation requires process data to be aggregated by BAM over the course
of a week. But when building a dashboard prototype, a week’s worth of data will not be available.
In addition, the simplified, mock process does not carry any content, so how are reports that include
business data (in this case, SDT attribute values) supposed to be included in a prototype dashboard
The answer is to use a series of processes that each carry an SDT. SDTs are used to enter data values
directly and treat them as if they were daily summaries.
Prototypes are designed so that each report in the dashboard is populated with data from its own
process. Each process contains two activities, one manual and one automatic. The automated activity
is completed by a no-op method, and the manual activity is completed by a user. During the manual
step, values to be displayed in the report are entered as process variables. Once the processes are run,
the reports can be designed in PRS.
This approach gives the illusion that all of the business data reports are derived from the simplified
process (in this case, the New Account Applications process) when in fact they are completely separate.
EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 125