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


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

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.

What is the different between Dynamic Web Services, Web Service and WS Inbound Activities ?

What is... This is a short answer and question category.Web Service

To invoke a Web service, you must have a Web Services Description Language(WSDL) document that provides the necessary information for accessing the service. The custom parameters for Web Service activities identify the WSDL document and the XML content to send to the service. They also specify how to handle the response from the Web service.

Web Service
Activity Inspector – Web Service Properties

Web Services activities differ from the other integration activities in two key ways:

  • The content that you send to the Web service must be a well-formed XML file that is namespace self-sufficient.
  • Web services respond to messages sent to them, so the activity needs to be able to handle a response.

WS Inbound Step / Initiate

Web Service Inbound creates a new web services end-point for an activity that needs to provide an integration point and a WSDL to an external system.

In the Process First option, you define the port and operation and the system creates a WSDL from the process definition. The system creates one WSDL for a process, with a section for each Web Service Inbound activity contained within it. The Content Based Correlation enable the system to correlate messages based on the correlations set.

Web Services Inbound Step
Activity Inspector – inbound Properties

In the WSDL First option, you specify an existing WSDL for the system to use in the process.

The WS Security UserName Token authentication provides credential-based access to the activity or process (when used in an initiate activity). Once enabled, all client requests to this activity must contain the same credentials in the request header (in structure defined by WS-Security schema for UserTokens) to be granted access to the activity or process.

The Message Transmission and Optimization Mechanism (MTOM) enable the system to optimize any attachments while sending the response.

Dynamic Web Services

Activities based on this template run a web service operation. Unlike the Web Service template, this activity template enables you to interactively map data between business process attributes and the web services parameters. This activity template supports both secure and non-secure web services.
Non-secure web activities: WSDL File
Dynamic Web Services
Activity Inspector – Web Service Configuration Properties
Secure web activities:

  • HTTP proxy support
    To access a web service that is located outside the firewall, through a HTTP proxy server, you must configure the HTTP proxy parameters.
  • HTTP basic authentication
    web service protected by HTTP authentication
  • SOAP header-based authentication
    web service protected by SOAP header authentication
  • Secure Socket Layer authentication
    web service that is secured by Secure Socket Layer (SSL)
  • DFS (Documentum Foundation Services) services from Process Builder



Understanding Process Data

Understanding Process Data

xCP 1.x compatible

There are three kind of process data used in Process Builder:

  • Package attributes are the metadata associated with the object
  • Process variables can be single attributes or a complex hierarchy of attributes named Structured Data Types (SDT)
  • Process parameters are predefined values used in all instances


Packages are metadata associated with the Documentum object which is passed between activities in an existing process. Package data is persistent.

Process variables

Process variables are not persistent. This kind of variables must be mapped in the Process Data Mapping Activity to a package attribute if the value of the variable should persist beyond the life of the process instance.

Structured Data Types are not persistent. They are global and can be used by any process.
It is not possible to delete or modify used SDT attributes. New attributes to an existing SDT can be added. SDT should be used to group logically related business data.
SDTs are more lightweight than object attributes and are better for performance and scalability. Replace as many process variables as possible with SDT attributes (xCP Performance Tuning Guide).

Process parameters

Process parameters are fixed values defined in the process template and available for all process instances. Administrators can change process parameters without uninstalling the process. The changed parameter value is used in all process instances after saving the value.

Any changes to the data model require uninstalling, saving and reinstalling the form and process templates. 
Example: to change a SDT or SDT attribute after implementing you must break the data binding in Forms Builder and rebind the renamed SDT.

Updating process data

To modifying an SDT  – variable it brings a lot of trouble in your environment.
To change the SDT properties you must delete the selected SDT from the environment and recreate the SDT including the old properties and the changed properties.


  • remove an attribute from the SDT
  • decrease the length of a string value (increase the length can be done at any time)
  • change the type of an attribute
  • change from repeating to non-repeating