How to create a single drill-down report

In this case I defined two simple reports, one as a target (contains the data to be shown in addition of the base report’s data) and the other as a base report (contains the data to be improved by the data from the target report) thereby following the best practice to design the target report first and the base report afterwards. The base report is defined as a table chart type and the target report is defined as a pie chart type.

Defining the reports

1. In Process Reporting Services define a simple report which is supposed to be the target report.

Creating a new simple report

 2. Select a data source

Data Sources are selected by pulling items from the palette area on the left side into the white area in the middle. After pulling the items there one can select how to query the items and how to treat them  in the report.The different items selected and processed here influence what is usable in the next step.

3. Select either Pie, Bar, or Table as the chart type.

Process Reporting Services offers Table by default. Attention: The selection made in step 2 influences what is displayed here. Depending on what you selected before you get different information messages (red text in this screenshot saying: “no data available”)

There are combinations of items that are not compatible with every chart type. In this case an error message is issued warning against the compatibility problem.

If you get error messages there – e.g. “y-axis must be numeric value” -, you will have to change that within Chart Data. There you can steer which data belongs to the different axes. If everything works fine, it should look as follows:

The drill-down itself

First create another simple report which will be the base report. For this follow steps 1 – 3. For a better visualization I chose table type as chart type.

4. Within the Chart Data tab locate the series or column for which you are defining a drill-down report.

Click in the Drilldown field. To find it you must open the columns first:

5. To define a drill-down to another report:

a. Select the Report radio button.

  1. b. Browse to and select a target report.

The report selected here is the one created in steps 1-3. It can be selected from a picklist after creation.

 

 

 

 

The column the drill-down has been designed for changes in color. So the link to the target report is shown. Clicking on the coloured items take the user to the target report.

 

 

 

 

 

c. Click the Filter button(to be found under the drill-down button) to define a filter expression.

 

 

 

 

 

 

d. Select a filter tab and filter tree item and move it to the Filter Expression field by double-clicking.

 

e. Place your cursor within the single quotes and press the Ctrl and spacebar keys on your keyboard simultaneously. This provides a list of dynamic filter values.

f. Double-click a dynamic filter value and click Ok to close the Filter window.

6. To define a drill-down to a URL, select the URL radio button and enter a URL in the field

provided.

Note: The URL must be absolute and specify the location of a web page in full. For example:

http://www.siteaddress.com.

The result of a functioning drill-down looks as follows: clicking on the changed columns directly takes the user to the drill-down target report. If the drill-down works, it shows in the header like this: base report > target report.

27. September 2012Permalink

What is a drill-down report?

Drill-down is used for navigation in hierarchically organized data (OLAP). Drill-down describes an increasing granularity in the management of data. E. g., one can zoom into an address. The process of zooming out (decreasing granularity) is called roll-up or drill-up. The drill-down’s increasing granularity is shown with the help of an address example that develops from the country (low granularity) to the real address (high granularity).The drill-up or roll-up is the opposite of a drill-down. It makes use of a decreasing granularity showing things more globally.

Following the items in the picture from top to down you can see the increasing granularity of the drill-down whereas the down to top direction shows the decreasing granularity of a roll-up / drill-up.

Documentum differentiates between two kinds of drill-down reports:

Single Drill-down Multi Drill-down
relation between a base report and a target report: base report is updated based on target report Link a base report to other reports: relation results in an updateBut one of the surrounding dashlets not one of the contents of the base report (E20-120 exam)
Built in one phase:
use Process Reporting Services to implement relation between base and target
Built in two phases:
1. use PRS to build the hyperlinks
2. use Task Space dashboard manager to implement the connection between the dashboards to be updated and the source

Single- and multi drill-down reports are configured with a source (base) report and a target report. It is best practice to design the target report first, so that it is available on picklists when the source (base) report is designed.

Relevant products: Business Activity Monitor , Process Reporting Service

29. August 2012Permalink

WF vs Lifecycle

Here you can find a short overview of two of the automation features that documentum offers. It helps you keep in mind the most important differences. In combination with aliases they even can be transferred from one repository to another. For further information please refer to the corresponding documentation.

LifecycleWorkflow
A lifecycle is what happens to an object.A workflow is what people do to an object.
A lifecycle is a set of linearly connected states.A workflow is a network of activities.
artifact in a Documentum project, to be installed or uninstallednot implemented as a project. Using Project builder WFs can be changed using a checkin / checkout function.
Documentum ComposerWorkflow manager and Process Builder, but not in Documentum Composer.
instance of dm_policyinstance of dm_process
without run-time instanceswith run-time instances (When a user starts a workflow, the server uses the definition in the dm_process object to
create a runtime instance of the workflow. Runtime instances of a workflow are stored
in dm_workflow objects for the duration of the workflow. )
definition states: draft, validated, installed (states that have absolutely nothing to do with the states in the LC which are stored in attributes i_state_no, state_* and others in dm_policy object)definition states: draft, validated, installed
16. Juli 2012Permalink