KB001638

Introduction

The following issues are currently known for K2 blackpearl and include workarounds where possible.

SharePoint Integration

• When designing a workflow that integrates with a SharePoint 2013 Site Collection, running in SharePoint 2010 compatibility mode, an error occurs when configuring a SharePoint User Manager Event stating: “An exception occurred. exception: There is an error in the XML document (1,5185)”.
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.

SmartObjects and Services

• An error occurs when executing a SmartObject where the name of the SmartObject exceeds the 128 character length. The error will indicate that the name is too long and the maximum length is 128.
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.
• When adding a new Environment Field instead of editing an existing field, the Autodiscover property for this field is set to False by default. This results in the field not showing in the Autodiscover Webservice response.
  Workaround:
  • The first option is to rather edit an existing Environment Field. This will keep the Autodiscover value as True.
  • If a new Environment Field is required, the Autodiscover flag needs to be changed manually in the database. The table to change is [Environment].[Field], search for the [Autodiscover] field and set the value to True.

Forms Authentication

• The following configuration is required if you want to make use of single or multiple logins, that go through the FormsSTS (not using the K2 label Security Provider), and be able to log in to the SmartForms Designer and SmartForms Runtime with or without having to specify a security label for the Security Provider:
  • Navigate to the web.config located in C:Program Files (x86)K2 blackpearlWebServicesIdentityStsForms
  • Add the K2 label to the attribute value:
    Code example:
     

Package and Deployment

• When creating a new Form with a metadata column, deploying this form to a new environment using Package and Deployment, results in the TermSetID and TermStoreID not being updated for the deployed form.
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.
• When deploying a SharePoint List with Lookup columns, associated with a K2 Application, to a new environment, an error occurs when trying to add a new List item. The error states: “The field or property 'OData__x0078_wl2' does not exist.”
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.
• In some instances when creating a new Deployment Package or adding items to a package, not all the items are included if the cache is not cleared.
  Workaround:
  Manually clear the cache and add the items again.
• After deploying a package to a new environment and the package contains a SharePoint List with a managed metadata column, fields are unable to resolve. An error occurs stating: “Specified argument was out of the range of valid values. Parameter name: index”.
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.
• Smartwizards configured in a workflow is not configured correctly after deploying a package to a new environment. For example, subsites are not surfacing lists in the wizard although the subsite is registered.
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.
• When uploading a package for deployment, slow performance is experienced on the Column Remapping screen after clicking the refresh button.
  Workaround:
  At the time of this version’s release date, there was no known workaround for this issue.
• When attempting to deploy a package in MMC after removing the Attachments View from a Form, unresolvable missing references occur. This occurs with K2 blackpearl 4.6.8 packages but is not limited to only this version.
  
  Workaround:
  From the source environment:
  1. Open the workflow and run through the Start activity.
  2. Re-deploy the workflow.
  3. The workflow instance ID’s will be updated.
  4. Deploy your package again.
• When creating a deployment package in MMC before upgrading to K2 blackpearl 4.6.9 and the workflow contains an out of context service instance,for example a List or Document event, the service instance appears as a missing reference when deploying this package after upgrading to K2 blackpearl 4.6.9.
  Workaround:
  1. Double-click the Unknown Service Instance, or right-click and select configure.
  2. Select your SharePoint 2013 Service Instance.
  3. This will remap successfully and resolve the missing reference.
• When deploying a package containing a Remove User from All Groups event in the workflow, the target server is not updated with the new target environment. This results in an error indicating that the server could not be contacted when running a workflow instance.
  Error: 181731","2015-02-24 09:26:22","Error","General","28083","ExtenderExecuteError","ProcessInstance.HandleException","28083 ServerEvent: Message: The server could not be contacted.; ServiceName: Account Management Service; ServiceGuid: cd3804d6-973d-4de4-bf78-8427f6761011; InnerExceptionMessage:
  Workaround:
  Open the wizard and update the event to point to the new environment.