This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
After upgrading to K2 blackpearl 0807 (4.8210.2.450) or (4.8210.3.0) some of the OOB (Out of the Box) Reports might be empty. The problem is a result of logging of instances, as new instances are started new versions need to be logged. After upgrading the existing process versions did not get logged resulting in OOB Reports data being empty for process instances prior to the upgrade.
Error Scenario Steps
|Note: The steps below describe scenarios under which these errors may occur. These steps are simplified and not all steps are shown or described.|
When upgrading to K2 blackpearl 0807 (4.8210.2.450) or (4.8210.3.0) a reporting problem might occur, for more information on KB000450 see here K2 blackpearl 0807 Update (4.8210.2.450)
A symptom of this issue can be the following: When new instances of upgraded processes are started without redeploying the process in KB000450 which previously had data, only some of the data will appear on the reports, however, all new data will display.
Or these OOB reports might be empty for data on instances that ran prior to upgrading:
- Event Instances report
- Activity Instances report
- XML Datafields report
- Datafields report
- Process Overview report
- Activity Statistics report
- Process Information
When an errored process is repaired, in some cases empty activities and no lines will show on the view flow, and in other cases an error like “The given key was not present in the dictionary” will be displayed.
Scenarios are as follow:
- Perform an error repair 3 times in the same activity on different events
- Perform an error retry to newer versions for the same activity on different events
- Perform an error retry to older versions
No error message.
This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error.
The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx