Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

VBD KPI's & Views not being packaged while exporting



The Visual Business Director's Key Performance Indicators (KPIs) and Views are not being packaged whilst creating a package for distribution.
When the package is imported into a new environments, they are not present.

Error Messages

No error message.

Steps to Reproduce

1. Create KPI's in VBD using the path Designer Studio > Decisioning > Monitoring > Visual Business Director > Key performance indicators.
2. Open VBD and save some views.
3. Create a distribution package using the path Designer Studio > Distribution > Package, from source or development environment.
4. Import distribution package using the path Designer Studio > Distribution > Import, into test environment.
5. Check Visual Business Director's Key performance indicators and Views using the path Designer Studio > Decisioning > Monitoring > Visual Business Director.

Root Cause

The explanation why the VBD KPIs and Views were not exported is that these items are not rules while the Application Package wizard defaults to including rules only.

The VBD KPIs and Views are instead stored as instances of data classes. KPIs are in Data-Decision-Outcome-KPIDefinition and Views are in Data-Decision-VBD-Applet-View.

Since the Applicaton Package wizard creates a Product rule for the application, you are able to edit the product rule directly to include these data classes if desired.

Using the list of product rules with the path Records > SysAdmin > Product, one can open the product rule just created and specify the two Data-Decision classes under either "Class instances to include" or "Individual instances to include" based on your requirements. 


Adding Data-Decision-Outcome-KPIDefinition and Data-Decision-VBD-Applet-View to the "Class instances to include" section led to the VBD KPIs and Views being included in the package and in the new environment upon import.

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us