Introduction

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

Rights and Permissions

  • An “Access Denied” error occurs when trying to create a K2 Application from a SharePoint List after SharePoint was left open in a browser for a long period of time. The error is caused after the OAuth token expired in the time that SharePoint was open in the browser.
    Workaround:

    Close and re open SharePoint.

Forms

  • When the user has not received an OAuth token yet, accessing a page with the Safari browser that contains an App Part, such as the Worklist App Part or the Form Viewer App part, results in the user being redirected back to the page but the user will be inside the frame of the App part instead of the parent page.
    Workaround:
    Ensure the user has an OAuth token assigned.

Workflow

  • On a distributed environment, when dragging and dropping a Get List Item Reference wizard on the design canvas, one of the following errors might occur intermittently:
    • Value cannot be null. Parameter name: s
    • Error Message: SmartObject Server Exception: Inconsistency detected between SmartObject 'CustomList Icon' and Service Object 'My_Lists_CustomList_Icon' during loading of SmartObject Definition. Service Object : 'My_Lists_CustomList_Icon' not found in Service Instance 'sp2013.{domain}.com' Definition.
    Workaround

    At the time of this version’s release date, there was no known workaround for this issue.

SharePoint Integration

  • When deleting repeated item events from a SharePoint Calendar List associated with a K2 workflow, a new workflow instance is started for the deleted event, even if not specified to start the workflow instance.
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • When creating a SharePoint List and saving the list as a template, the template is not available for use in the Create List wizard in the “Template” drop-down.
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • When designing a workflow from a Custom List that contains an Event Content Type, using the Event Content Type in the workflow results in metadata discrepancies when the workflow reaches the step using the Event Content type. The Start date will display as one day earlier than the actual day selected for the event.
    Workaround:

    At the time of this version’s release date, there was no known workaround for this issue.

  • When an Event based workflow is configured to start when an item is added, the workflow fails to start when an item is added to a SharePoint Document Library with columns set as required. No error occurs.
    Workaround:

    At the time of this version’s release date, there was no known workaround for this issue.

Package and Deployment

  • When using the Deploy Package tool to deploy a package in K2 for SharePoint, do not click the Back button in the browser to navigate back. Doing so may result in increased memory usage on the K2 server due to session management. The correct way to cancel out of the Deploy Package screens is to click the Cancel button at the bottom of the screen.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • Unable to create a package in the Web User Interface after removing the Attachments View from a Form. When attempting to package artefacts, the following errors are displayed:
    Image
    Workaround:
    From the source environment:
    • Open the workflow and run through the Start activity.
    • Re-deploy the workflow.
    • The workflow instance ID’s will be updated.
    • Create your package again.
  • When deploying a package created from a K2 Application in a SharePoint Document Library with Content Types enabled, an error occurs when starting a new workflow instance by uploading a new document. The error indicates that the SmartObject or one of its components could not be resolved:
    Image
    Workaround:
    • Edit the Edit [Document] View
    • Edit the When Drop Down Content Type Name is Changed rule
      Image
    • Configure the URL for the Text Box Content Type Form
      Image
    • Update the URL to the correct URL
      Image
  • When creating a deployment package from a SharePoint Document Library with versioning enabled, deploying this package to a SharePoint Document Library without versioning enabled will result in an error when running Forms or workflow instances:
    Image
    Workaround:
    Enable versioning on the SharePoint Document Library in the target environment.