< class="prominent-subhead ">

Code Fix: An Escalation error occurs when migrating from K2.net 2003 to K2 blackpearl

This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. 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.


When a project is migrated/exported from K2.net 2003 and certain K2 contexts like the EscalationRuleContext and/or the EscalationActionContext are used to refer back to the containing ActivityInstance object, an "’ActivityInstance’ is not a member of ’SourceCode.KO.EscalationRuleContext’" exception may occur.

Error Scenario Steps

Note: The steps below describe one scenario under which these errors may occur. These steps are simplified and not all steps are shown or described.
  1. Create a process in K2.net 2003 that have a modified Activity Escalation Rule (or the Activity Escalation Action) where you make use of the "ActivityInstance" object on the Rule Context.
  2. Export it to the K2 blackpearl server.
  3. Start a new Instance.

Error Messages

The following error message applies to this article:

  • "’ActivityInstance’ is not a member of ’SourceCode.KO.escalationRuleContext’"

Error Resolution

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