Symptoms
Unknown references on the form
Diagnoses
Recently we have upgraded K2 from 4.6.8 to 4.6.9. Now when I tried to create package it shows me error on form. I checked the form rules and there is no rule reference for the error showing in PandD.
Below is the error:
'FormName' Form is referencing the 'ActivityName' Activity that could not be found.
'FormName' Form is referencing the 'FieldId' property on the 'UnknownEnvironmentField' Field that could not be found.
'FormName' Form is referencing the 'UnknownEnvironmentField' Field that could not be found.
Resolution
_1
A coldfix was provided to resolve the missing Activity errors when deploying to a target environment. Instructions for applying the fix is as followed:
1. Copy the coldfix file to the K2 Server. After extracting the file, right click on the assembly > Property if there is an Unblock option, please do so.
2. Stop K2 Blackpearl Service
3. Close K2 Package and Deployment
4. Make a backup of the current assembly and apply the coldfix assembly in location specified below:
File Path: C:Program Files (x86)K2 blackpearlHost ServerBinExtensionsRuntime
File Name: SourceCode.Runtime.Services.Forms.dll
5. Backup the current SQL stored procedure and apply the coldfix SQL Scripts against the K2 Database.
File Name: mProcSearchActivities.proc
File Name: mProcSearchEvents.proc
6. Start K2 Blackpearl Service
7. Open K2 Package and Deployment
8. Clear the Package and Deployment cache and retest
_2
The missing EnvironmentField item is a new Package and Deployment validation implemented in 4.6.9 to inform the user if there is a bad reference so that more compatible packages can be created. This behavior would occurs when an environment field was used and later deleted.
From the package (which is essentially an archive and can be extracted) please edit the form XML in a text/XML editor, then search for the missing environment field reference.
The XML structure containing this reference will indicate which rule the missing reference previously existed in. You will just need to re-run through the "Configure" wizard for these rules in the source environment this should update the form and resolve the missing reference. A new version of this package will now not contain this bad reference.
