No ratings

K2 4.6.10 Release Notes

 

K2 4.6.10 Release Notes

LEGACY/ARCHIVED CONTENT
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.

 

Introduction

In this scheduled release, we've updated K2 components with new and improved functionality and important bug fixes. The K2 4.6.10 release consists of the following updated components:

  • K2 blackpearl 4.6.10  (4.12060.1690.2)
  • K2 smartforms 4.6.10 (4.12165.1700.2)
  • K2 smartforms Control Pack 4.6.10 (4.13180.1710.2)
  • K2 for SharePoint 4.6.10 (4.13350.1720.2)
  • K2 Language Pack 4.6.10 (Preview) (4.13500.0.1)

 

 

Downloads

The various K2 4.6.10 installers can be downloaded from the  K2 Partner and Customer Portal. Use the table below to determine which installer you need.

K2 4.6.10
Current Version K2 Installation Package K2 Update K2 blackpearl K2 smartforms K2 Control Pack K2 for SharePoint (2013) K2 Language Pack (Preview)
No K2

 check

          Optional
K2 4.6.9 (Any of the following components: blackpearl, smartforms, smartforms Control Pack, K2 for SharePoint)  

 check

        Optional
K2 4.6.8 or earlier (blackpearl, smartforms, smartforms Control Pack, K2 for SharePoint)

 check

           
K2 blackpearl 4.6.8 or earlier    

 check

       
K2 blackpearl and Smartforms 4.6.8 or earlier    

 check

 check

Optional    
The black selection check above suggests the recommended installer for each scenario.
Note: The K2 4.6.10 update includes the hotfixes included in previous K2 4.6 Updates, so there is no need to install the previous updates.

 

 

What’s New in this release

There are several new features and enhancements available in this release.

K2 blackpearl

Features Descriptions Documentation
Comments and Attachments View Flow:  The ability to see comments and attachments related to a specific workflow in the view flow. 
Context Browser: The ability to work with comments and attachments in the workflow designers through the context browser.
Inline Function: A new inline function named Get File from Process Attachment has been added.
Comments and Attachments Enhancements.pdf (176 KB)
Broker  OData Endpoint: A dynamic endpoint broker for integrating with OData services.
Docusign: The ability to register a service instance for Docusign has been added as out the box functionality.
OData Endpoint Service Broker
Integration DocuSign: Includes SmartWizards for Create Envelope, Delete Envelope, Send Envelope, Resend Envelope, Void Envelope, Move Envelope to Folder, Add Recipient, Remove Recipient, Add Document, and Create Tab in K2 Studio and K2 Designer for Visual Studio. DocuSign Integration.pdf (4156 KB)
Enhancements Descriptions Documentation
API Custom SmartWizards: The breadcrumb control and the Date/Time picker functionality has been added to the code used to create custom smartwizards. Custom K2 SmartWizards
Installer K2 Update Package: In this release K2 is introducing the K2 Update Package. This installer makes it easier and quicker to update your environment by adding new files and only updating files that have changed. The K2 Update Package updates all the K2 components (blackpearl, smartforms, Control Pack, K2 for SharePoint) so you do not need to download and run multiple install files. The option to run the installer as an unattended install is also available. Note: The K2 Update Package can only be used to upgrade K2 4.6.9 or later environments. If K2 4.6.9 is not installed, you will need to run the full installation package for 4.6.10 to upgrade your K2 environment to 4.6.10. K2 Update Manager.pdf (198 KB)
Package and Deployment Validation: Improved validation messages. Package and Deployment.pdf (1328 KB)
Software Support Descriptions Documentation
Integration Docusign (version - Enterprise)
SSRS 2014
 

K2 smartforms

Features Descriptions Documentation
Offline Forms Ability to use application mode parameter to set up different rule sets for online vs offline form. Offline Forms.pdf (197 KB)
Management New features page: A new page to allow for activating integration features as part of the new K2 Management site and the Management node in the category tree in SmartForms. For example, activating integration with DocuSign will be done via this page, which will turn on the service instance, create SmartObjects and turn on the SmartWizards. Features
Integration DocuSign: Includes SmartWizards for Create Envelope, Delete Envelope, Send Envelope, Resend Envelope, Void Envelope, Move Envelope to Folder, Add Recipient, Remove Recipient, Add Document, and Create Tab in K2 Designer. DocuSign Integration.pdf (4156 KB)
Enhancements Descriptions Documentation
API Custom Controls: Added Obfuscation Methods only for custom controls. Considerations and Best Practices for Custom Controls
Views Anonymous Views: Gives the designer the ability to mark a View as anonymous, which will allow anyone to execute the View or subview on a Form as the application pool account. Anonymous Views/Forms
Installer K2 Update Package: In this release K2 is introducing the K2 Update Package. This installer makes it easier and quicker to update your environment by adding new files and only updating files that have changed. The K2 Update Package updates all the K2 components (blackpearl, smartforms, Control pack, K2 for SharePoint) so you do not need to download and run multiple install files. The option to run the installer as an unattended install is also available. Note: The K2 Update Package can only be used to upgrade K2 4.6.9 or later environments. If K2 4.6.9 is not installed, you will need to run the full installation package for 4.6.10 to upgrade your K2 environment to 4.6.10. K2 Update Manager.pdf (198 KB)
Software Support Descriptions Documentation
Browser version support The following browser versions are supported in K2 smartforms 4.6.10:
Internet Explorer 9
Internet Explorer 10
Internet Explorer 11
Chrome 43.0.2357.124 m
Firefox 38.0.5
Safari 7.0.6 or greater (Windows support deprecated. Latest Safari version is only supported on Mac)
 

K2 smartforms Control Pack

Features Descriptions Documentation
Controls ListBox: A control for displaying and selecting a list of items.
Location Based Services: A control that can retrieve a user's current location.
ListBox Control
Location Based Services Control
Installer K2 Update Package: In this release K2 is introducing the K2 Update Package. This installer makes it easier and quicker to update your environment by adding new files and only updating files that have changed. The K2 Update Package updates all the K2 components (blackpearl, smartforms, Control pack, K2 for SharePoint) so you do not need to download and run multiple install files. The option to run the installer as an unattended install is also available. Note: The K2 Update Package can only be used to upgrade K2 4.6.9 or later environments. If K2 4.6.9 is not installed, you will need to run the full installation package for 4.6.10 to upgrade your K2 environment to 4.6.10. K2 Update Manager.pdf (198 KB)

K2 for SharePoint

Features Descriptions Documentation
Package and Deployment Ability to package SmartBox data in SharePoint Package and Deployment UI. Package and Deployment.pdf (1328 KB)
Integration DocuSign: Includes SmartWizards for Create Envelope, Delete Envelope, Send Envelope, Resend Envelope, Void Envelope, Move Envelope to Folder, Add Recipient, Remove Recipient, Add Document, and Create Tab. DocuSign Integration.pdf (4156 KB)
Enhancements Descriptions Documentation
Package and Deployment Validation: Improved validation messages. Package and Deployment.pdf (1328 KB)
Installer K2 Update Package: In this release K2 is introducing the K2 Update Package. This installer makes it easier and quicker to update your environment by adding new files and only updating files that have changed. The K2 Update Package updates all the K2 components (blackpearl, smartforms, Control pack, K2 for SharePoint) so you do not need to download and run multiple install files. The option to run the installer as an unattended install is also available. Note: The K2 Update Package can only be used to upgrade K2 4.6.9 or later environments. If K2 4.6.9 is not installed, you will need to run the full installation package for 4.6.10 to upgrade your K2 environment to 4.6.10. K2 Update Manager.pdf (198 KB)
Unattended Installer Ability to perform an unattended install without having to run through the installer manually for the first time to generate the xml schema. Unattended Installer for App Deployment.pdf (82 KB)

K2 Language Pack (Preview)

Features Descriptions
SmartForms Control Pack Translations have been added for the new controls available in Control Pack 4.6.10.

 

 

What’s been fixed in this release

K2 4.6.10 includes a number of bug fixes. Below is a list of the resolved issues by component. 

K2 blackpearl

SmartObject Services:

  • When executing a JSON type method SmartObject, the method does not return the requested JSON format.
  • Requested implementation of ORDERBY Information has been added.
  • After upgrading to K2 4.6.8 from K2 4.6.6 a Stored Procedure would return a Decimal type as a Number type.
  • An ‘Input String was not in a correct format’ error would be received when small Decimal values are returned when using a Stored Procedure.
  • When filtering a user on Nested Groups, no results would be returned.
  • When executing a method on a Main Group with Nested Groups, not all the details were returned.
  • When updating the Account Management Service via the SmartObject Tester Tool a ‘Root Element Missing’ error is received.

Smart Actions:

  • When a SmartAction is actioned by a user from a Trusted domain, the response is not processed.

Identity Service:

  • Permissions of SharePoint users were being removed via the K2SPUserGroups.asmx due to Identity being unable to distinguish users with ASCII characters.
Package and Deployment:
  • When deploying a Package with a referenced DLL, the deployment would fail due to the wrong version of the DLL being referenced.
  • When a package is converted to 4.6.9, Default Environment Fields are not referenced after deployment.
  • Displayed error messages have been changed when attempting to package a workflow that has not yet been deployed.
K2 API:
  • Backward compatibility was broken on the BuildWhere method of the AbstractFilter class in K2 4.6.9.
Security:
  • SAML2SecurityToken error is received when trying to access the K2 Application due to the rejection of the Token because the SAML2: Assertion’s NotOnOrAfter condition is not satisfied.
Stored Procedures:
  • When multiple stored procedures are executed simultaneously, deadlocks are experienced on [ServerLog.LogBatch]
  • When a filter on a Stored Procedure is specified and the GETLIST method is executed the following error occurs: ‘Must Declare the Scalar Variable’
Database:
  • When moving K2 databases from one environment to another and running a reconfigure via the installer, a ‘Symmetric Key Invalid’ error is received.
Workspace:
  • In Workspace, in the Error Profile page, if the page of errors extends to more than one page, the buttons for, back to the first, the previous, the next and the last page are not visible. If the Browser is resized, the buttons are visible.

K2 smartforms

Authentication:

  • When Multi Auth and Authorization rules are implemented and access is provided to specific users, 401 errors persist when attempting to login via the Login screen in SmartForms.

Runtime:

  • At Runtime a control’s tooltip would display the HTML, even though the controls property was set to Literal.
  • A Radio Button with static values on a View, at Runtime would result in an infinite spinner.
  • When a Close Subview or Subform action is executed at runtime, the actions no longer executes successfully.
  • When a Form contains three of the same Views and an “If Form passes Validation” condition is applied to controls on these Views, the Form only validates the first View on the Form at runtime.
  • When closing a nested Subform at Runtime an ‘Uncaught TypeError: Cannot read property ‘controls’ of undefined’ error would occur.
  • The Picker Controls value would display as blank after editing a List Item at runtime after upgrading from SmartForms 1.0.4 to 1.0.7.
  • At runtime, a Form’s columns would not work as expected when a fixed width is set for the columns.
  • When using a Stored Procedure on a List View to download files, the functionality to download files broke.
  • When a Drop-Down or Radio Button List Control is used with the ‘YesNo’ data type, the incorrect value is displayed after the data from a SmartObject is populated.
  • When a server call action is set to execute asynchronously and a server execution error occurs during the execution of this action, a JavaScript console error is shown instead of the correct error handling.
  • When running SharePoint 2010 or SharePoint 2013 in SharePoint 2010 mode and K2 4.6.9 with Internet Explorer in IE=8 document mode, an issue would occur whereby the K2 Forms Viewer web part will no longer render the form as expected and an error message or infinite spinner will persist. See KB001704 for details of the resolution available in K2 4.6.10.

Design Time:

  • When editing expressions which contain an equals operator mappings for Boolean, the values would change to 0 for False and -1 for True in Internet Explorer.
  • After removing a View’s dependencies and attempting to delete the View, the following error message would be displayed ‘One or more items may not be deleted as they are in use’.

Controls:

  • The ability to transfer Empty Text to a Data Label Control after upgrading from SmartForms 1.0.4 to 1.0.7 ceased to function as expected.
  • When using the Date Control with the new date SmartObject data type, the values do not populate correctly.
  • An issue persisted whereby after upgrading SmartForms from K2 4.6.8 to 4.6.9, a Form which contained a Text Area Control would cause rendering issues.
  • When a page has multiple tabs which are hidden and the Save as PDF Control is executed, the page is duplicated in the generated PDF.

Expressions:

  • When using the Week Number Operator in an expression within an environment with French locale settings, the operator returns the incorrect value.

Forms:

  • When transferring a forms name to a Text Box via an initialize rule that transfers the Forms name to the control, the control would display ‘[object Object]’.

Integration:

  • When creating an Item Reference in a SmartForms Integration Event and expanding the Context Browser to select a Form, an ‘Object reference not set to an instance of an object’ error would occur.

SmartObject:

  • When changing a Text Box control’s data type from Memo to Text in the SmartObject Designer the datatype would not change accordingly.
  • When a subview attempts to call a SmartObject method using Anonymous Runtime the following error is displayed ‘Cannot access SmartObject item 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' anonymously’.

Security:

  • Functionality has been changed regarding the execution of SmartObject methods which are being used by an anonymous Form. SmartObject Methods which are not used on a Form are no longer able to be executed on a Form using Anonymous Access.

Themes:

  • When using the Lithium Theme on a Subview, the subview’s background color did not inherit the View’s background color.
  • When the Lithium Theme is set as the default theme on a Form, hidden Data Label controls would be visible at runtime.

Views:

  • When a View parameter has the same name as a SmartObject method parameter an issue would occur when configuring an action to execute a View’s method.

K2 smartforms Control Pack

Performance:

  • When running a Form with an Activity Instances Chart Control, the control would execute in two loading phases.

Controls:

  • When changing the control type to Auto Complete would cause the Designer to become unresponsive.
  • When switching between the HTML, Design and Preview options in the Rich Text Control, the cursor would display in the border instead of the content area.

K2 for SharePoint

Forms:

  • Out of the box pages fail to render correctly when run on a SharePoint site that contains branding or custom master pages.
App Registration:
  • When attempting to register the K2 App on a sub-site and entering a relevant URL, the App registration fails when clicking the ‘Next’ button and the following error is displayed: ‘Form cannot be found or not checked in’.
SmartObject:
  • When executing the ‘Get Documents’ method of a SharePoint Document Library SmartObject with a user that has ‘View Only’ permissions an ‘Access Denied’ error would occur.

 

 

Known Issues

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

K2 blackpearl

  • At runtime when uploading a large file to DocuSign could result in error that states "The data cannot be converted." In most cases this is a result of network performance. The following link is a guideline to the file size that Docusign can accept, https://www.docusign.com/p/RESTAPIGuide/Content/GettingStarted/File%20Size%20Limitations.htm.
    Workaround: Check network Performance and ensure the document is within the acceptable limit before trying to upload the document.
  • When trying to register a service through the OData broker an error is received as a result of an OData issue with conflicting namespaces.
    Workaround: Use an alternate metadata service configuration or name the service instance to be the same as the conflicting namespace.
  • An unauthorized error occurs in K2 Studio when the SharePoint 2013 wizards are dragged onto the canvas. The error only occurs on a clean install when the user has not yet signed into SharePoint. An example of the error message would be: "Wizards Error
    Service: dc_east_east_local_800
    Service Guid: 3b1ea6ae-32a2-4040-a979-0312adf97a7c
    Severity: Error
    Error Message: The remote server returned an error: (401) Unauthorized.Failed to initialize the Context:..."
    Workaround: Close K2 Studio.
    Log into SharePoint.
    Open K2 Studio and drag on a SharePoint 2013 wizard.
  • DocuSign Move Folder Wizard: The DocuSign Move Folder wizard currently allows a user to select the Inbox and Draft folders as an option to move the envelope to, however DocuSign do not allow envelopes to be moved to or from the Draft or Inbox folders. The workflow will pass in runtime without any errors and will complete successfully if you select to move an envelope to or from these folders, but the envelopes are not actually moved in runtime as this is not permitted by DocuSign.
    Workaround: Select an alternative folder to the Inbox or Draft folders in the wizard dropdown.
  • DocuSign Move Folder Wizard: DocuSign does not permit an envelope in a "Draft" state to be moved at all. However the Move Folder wizard will allow the user to attempt to move a draft envelope. The result will be that the workflow seems to complete successfully in runtime although nothing is actually moved in DocuSign and there are no errors to inform the user that it is not possible to move a draft envelope in DocuSign.
    Workaround: Do not select an envelope in a draft state to be moved to a folder.

K2 smartforms

  • If a listing control’s populate rule is moved under a condition in the rule designer and a property is changed on the control a duplicate populate action will be added in the View initialize event. Controls affected include Drop Down, Radio Button List, Check box List, List Display, Lookup and Choice.
    Workaround: Edit the view’s initialize event and remove the duplicated action.
  • At runtime when uploading a large file to DocuSign could result in error that states "The data cannot be converted." In most cases this is a result of network performance. The following link is a guideline to the file size that Docusign can accept, https://www.docusign.com/p/RESTAPIGuide/Content/GettingStarted/File%20Size%20Limitations.htm.
    Workaround: Check network Performance and ensure the document is within the acceptable limit before trying to upload the document.
  • In Firefox when opening certain popup windows such as the configuration screen for output mappings, fields appear to be missing. Clicking on the missing fields or dragging values into the fields results in unexpected behavior such as the values in the fields displaying incorrectly. However this does not affect the functionality or the popups in any way and the values are saved correctly.
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • A validation warning message appears when a DocuSign Create Envelope is added to an activity in web designers such as K2 Designer when there are multiple templates in DocuSign. This warning message is invalid
    Workaround: Click OK on the warning message and continue.
  • Templates fail to populate in any of the Template Choice Columns when there are multiple templates to select from. In the web designers when there is only one template available in a dropdown it is automatically selected. However, when there is more than one template available none are selected by default so the dropdown fails to have a selected value at the time.
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • The workflow designer will not function when opened in Chrome 42 or higher. A "Something went wrong..." error displays on the web page. This is due to Chrome's deprecated support for Silverlight.
    Workaround: Enable NPAPI in Chrome. For detailed steps see the troubleshooting topic in the K2 smartforms product documentation.
  • In certain circumstances in Internet Explorer 11 when clicking on the i(help) button on the K2 smartforms screen the default Help Home page will be opened rather than the exact help page related to the button.
    Workaround: Open the K2 Designer in a different browser to Internet Explore and click on the i button to open the correct help page.
  • DocuSign Move Folder Wizard: The DocuSign Move Folder wizard currently allows a user to select the Inbox and Draft folders as an option to move the envelope to, however DocuSign do not allow envelopes to be moved to or from the Draft or Inbox folders. The workflow will pass in runtime without any errors and will complete successfully if you select to move an envelope to or from these folders, but the envelopes are not actually moved in runtime as this is not permitted by DocuSign.
    Workaround: Select an alternative folder to the Inbox or Draft folders in the wizard dropdown.
  • DocuSign Move Folder Wizard: DocuSign does not permit an envelope in a "Draft" state to be moved at all. However the Move Folder wizard will allow the user to attempt to move a draft envelope. The result will be that the workflow seems to complete successfully in runtime although nothing is actually moved in DocuSign and there are no errors to inform the user that it is not possible to move a draft envelope in DocuSign.
    Workaround: Do not select an envelope in a draft state to be moved to a folder.

K2 smartforms Control Pack

  • Location Services Control: At runtime no data is returned in the Location Services Control when using a Samsung Galaxy tab 2. All values are also returned as 0 rather than blank values. This affects the following properties:
    Latitude
    Longitude
    Altitude
    Altitude Accuracy
    Header
    Speed
    Time Stamp
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • Location Services Control: When using the Location Services the [execute the control's stop watching] method does not execute during Runtime on View and Form Level when Firefox is the browser.
    Workaround: Use a different Browser at runtime when a Form or View contains the Location Service Control.
  • Rich Text Control: If you had customized the Toolbar to only show certain items for the Rich Text Control in Control Pack 1.0.1 by using the Toolbar items properties setting, when upgrading to K2 4.6.10 the setting will be overwritten with the default properties and all the Toolbar items will be displayed again.
    Workaround: Open the View or Form containing the control and re-configure the Toolbar item setting.

K2 for SharePoint

  • When trying to access K2 for SharePoint for the first time using Firefox you will be presented with a security warning.
    Workaround: See KB001683 for the workaround.
  • Changing a property on a listing control on certain SharePoint generated Views will add an extra populate action for the control in the View initialize event. If the SmartObject method that this control is bound to has required properties then this View will not work correctly at runtime. Controls affected include Drop Down, Radio Button List, Check box List, List Display, Lookup and Choice.
    Workaround: Edit the View’s initialize event and remove the duplicated action.
  • At runtime when uploading a large file to DocuSign could result in error that states "The data cannot be converted." In most cases this is a result of network performance. The following link is a guideline to the file size that Docusign can accept, https://www.docusign.com/p/RESTAPIGuide/Content/GettingStarted/File%20Size%20Limitations.htm.
    Workaround: Check network Performance and ensure the document is within the acceptable limit before trying to upload the document.
  • A validation warning message appears when a DocuSign Create Envelope is added to an activity in web designers such as K2 Designer when there are multiple templates in DocuSign. This warning message is invalid
    Workaround: Click OK on the warning message and continue.
  • Templates fail to populate in any of the Template Choice Columns when there are multiple templates to select from. In the web designers when there is only one template available in a dropdown it is automatically selected. However, when there is more than one template available none are selected by default so the dropdown fails to have a selected value at the time.
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • The workflow designer will not function when opened in Chrome 42 or higher. A "Something went wrong..." error displays on the web page. This is due to Chrome's depreciated support for Silverlight.
    Workaround: Enable NPAPI in Chrome. For detailed steps see the troubleshooting topic in the K2 smartforms product documentation.
  • Creating a package of the K2 artefacts in a SharePoint List or Library that has the SharePoint Share Feature activated will fail when deployed to a new List or Library that does not have the feature activated and enabled. This is expected as the new List or Library should resemble the SharePoint List or Library before deployment.
    Workaround: The administrator must activate the Share Feature on the List or Library.
    The Share button will then display at the top of the List or Library. Click on the Share Button.
    Once the Share screen opens click on the cancel button, this will enable the feature. Now deploy the K2 package.
  • An unauthorized error occurs in K2 Studio when the SharePoint 2013 wizards are dragged onto the canvas. The error only occurs on a clean install when the user has not yet signed into SharePoint. An example of the error message would be: "Wizards Error
    Service: dc_east_east_local_800
    Service Guid: 3b1ea6ae-32a2-4040-a979-0312adf97a7c
    Severity: Error
    Error Message: The remote server returned an error: (401) Unauthorized.Failed to initialize the Context:..."
    Workaround: Close K2 Studio.
    Log into SharePoint.
    Open K2 Studio and drag on a SharePoint 2013 wizard.
  • When deleting a SharePoint List that was integrated with K2 and then creating a new list with the same name but of a different type will result in newly created SmartObjects, Forms and Workflows based on the new list template as well as the previous SmartObjects, Forms and Workflows of the original list template.
    Workaround: Delete the SmartObjects, Forms and Workflow from the original list that is no longer needed.
    Update the Start Rule on the newly created Workflow. Then edit each wizard in the workflow that might have a reference to the old artefacts and remap them to the new artefacts.
    Update any workflows to use the new SmartObjects, Views and Forms.
  • Deleting a SharePoint List that was integrated with K2 and then creating a new SharePoint Library with the same name and adding the K2 for SharePoint App will not function.
    Workaround: At the time of this version’s release date, there was no known workaround for this issue.
  • DocuSign Move Folder Wizard: The DocuSign Move Folder wizard currently allows a user to select the Inbox and Draft folders as an option to move the envelope to, however DocuSign do not allow envelopes to be moved to or from the Draft or Inbox folders. The workflow will pass in runtime without any errors and will complete successfully if you select to move an envelope to or from these folders, but the envelopes are not actually moved in runtime as this is not permitted by DocuSign.
    Workaround: Select an alternative folder to the Inbox or Draft folders in the wizard dropdown.
  • DocuSign Move Folder Wizard: DocuSign does not permit an envelope in a "Draft" state to be moved at all. However the Move Folder wizard will allow the user to attempt to move a draft envelope. The result will be that the workflow seems to complete successfully in runtime although nothing is actually moved in DocuSign and there are no errors to inform the user that it is not possible to move a draft envelope in DocuSign.
    Workaround: Do not select an envelope in a draft state to be moved to a folder.
  • Package and Deployment: A workflow validation error stating that the Form is invalid will occur after deploying a package containing a Form based workflow on a Document Library with a lookup list. The issue occurs when the lookup list does not exist on the target environment and is created from the column mapping screen in Package and Deployment. Once the missing reference is resolved the deployment will complete. On opening the Form based Workflow post deployment the error is displayed.
    Workaround 1:
    1. Click OK to close the validation popup
    2. Edit the Start Event
    3. Notice the Warning in the Context Browser: The selected Form is either not valid or checked out by another user.
    4. Click on the ellipses next to the Form to start the Workflow.
    5. Notice the Form is not selected post deployment.
    6. Select the Form
    7. Now SmartForm shows in the Context Browser
    8. Complete the wizard
    9. Deploy the Workflow
    Workaround 2:
    Re-Deploy the package on the Document Library in the target environment.

K2 Language Pack (Preview)

  • An error is displayed at design time when the Tab Index property of a control is reduced to a value less than 1. The Tab Index property starts reducing automatically in a loop.
    Workaround: Set the browsers language to English to configure the Tab Index property. Once configured set the browser back to the original language.

 

 

Important Considerations and Breaking Changes

K2 blackpearl

  1. K2 Setup Manager: .NET Framework 4.5 is required for the K2 installer to run, ensure that this version is installed on all machines on which the installer will be run.
  2. K2 Setup Manager: PowerShell 2 or higher is required on the K2 Server by the Setup Manager in order to make connection with Microsoft Exchange.
  3. Unattended Installer: In order to implement new features and resolve bugs new variables have been added to the installer in the 4.6.9 release. It is therefore required that any unattended files must be regenerated in this release to ensure that the full set of features and functionality gets installed.
  4. Non AD installations: The K2 Administrator account needs to have a SQL Server login and have public role membership on the SQL Server. This is to ensure that the SCSSOKey is created for the server, which is used for encryption and security. For existing Non-AD environments the public role needs to be added to the User Database Mappings before upgrading to K2 blackpearl 4.6.10.
  5. Legacy databases: K2 recommends that if you are still running on multiple databases (legacy databases) that you consider consolidating your databases in this release or in the near future. In order to upgrade to a future Update, you will be required to be on a single database. An important note has been added to the K2 Setup Manager that will remind you to consider consolidating your databases if it detects legacy databases. For more information, see KB001628 (http://help.k2.com/KB001628).
  6. Behavioral Change: Deploying a K2 4.6.8 package created in MMC that contains Forms Based Workflows or Event Based Workflows to a new subsite or site collection will result in the workflow being deployed to the new subsite/site collection (not the subsite to which the package is being deployed) because it does not have a unique name. This has been fixed for future packages, in K2 4.6.8 the workflow definition would have been "List/List1 workflow" and now in K2 4.6.10, the workflow name will be stored as "[SiteName] List/List1 workflow" in order to ensure that the workflow name is unique over sites, subsites and site collections on the same SharePoint server.
  7. In blackpearl certain components, such as View Flow and K2 for SharePoint (2010) require Silverlight to function. In Chrome 42 the NPAPI setting for Silverlight is disabled by default which will cause issues when using these components. It is possible to enable the NPAPI setting which will allow Silverlight to function again. To enable the setting follow the steps in the troubleshooting topic.

K2 smartforms

  1. In SmartForms the Workflow and SmartObject Designer requires Silverlight to function. In Chrome 42 the NPAPI setting for Silverlight is disabled by default which will cause issues in the designer while creating a workflow. It is possible to enable the NPAPI setting which will allow Silverlight to function again. To enable the setting follow the steps in the SmartForms troubleshooting topic.
  2. In K2 4.6.9 error handling for asynchronous actions did not function as expected when the actions were executed and the error messaging was supressed. Instead of displaying the error in a popup it incorrectly displayed in a JavaScript console error. Often users would not even be aware that there were errors on a Form as they were not presented with the error message. Certain controls such as the Picker Control would have been affected by this issue as they use asynchronous actions. In K2 4.6.10 the issue has been resolved which will result in more error popups being displayed than in K2 4.6.9. This is the correct behavior and will allow you to fix the errors as needed.

K2 for SharePoint

  1. Prior to K2 for SharePoint 4.6.9, if Forms were created for a List in a SharePoint Online environment, the resulting SmartForms would display outside of SharePoint context (in other word, the forms would show as a stand-alone page and not be hosted inside a SharePoint frame). The Common Consent changes introduced in K2 for SharePoint 4.6.9 allows Forms for Lists in SharePoint Online to be rendered inside SharePoint. To make use of this new functionality, use the New > Generate SmartObjects and New > Generate Forms options in the K2 Application elements page to re-generate the Data and Forms for the List. The regenerated Forms will then show inside of SharePoint, as opposed to stand-alone pages outside of SharePoint.
    Important: Re-generating Forms will reset any customizations you may have made previously. If you had customized the generated Forms for the List, you will need to re-apply the customizations after regenerating the Forms.
  2. When deploying a SharePoint 2013 integrated workflow from K2 Studio or K2 Designer for Visual Studio that is configured to start manually, the K2 Service account must be granted start rights to the workflow. The same applies to workflows that are exported from the Workflow Designer (as*.kprx) in K2 for SharePoint, modified in the thick clients and redeployed, in this case the rights between thin client and thick client are not transferred in the export. No error is encountered if the rights are not granted, but the workflow will not be started.

K2 Language Pack (Preview)

  1. The Language Pack only applies to K2 smartforms and K2 View Flow.
  2. Runtime exception messages originating from the K2 blackpearl Server will still be displayed in English.
  3. Localization support for the Design time is limited and areas of the Design time experience will still display in English after the K2 Language Pack has been installed.
  4. If a multi-language Form is required, the Form and the Form Views must be designed in one language then copied and modified for each of the other languages you wish to support. Direct the user to the Form in the user’s language choice. During installation of the K2 Language Pack, select all the required languages to ensure that the required resource files are installed for the languages you wish to support.

 

 

Installation

Refer to the Installation and Configuration guides available on help.k2.com for the prerequisites and steps needed to install the various components. Before installing any of the K2 4.6.10 components, ensure the correct prerequisite software has been installed in your environment.

When installing K2 4.6.10 using the full installation package the following install order is required.

  1. K2 blackpearl 4.6.10  (4.12060.1690.2)
  2. K2 smartforms 4.6.10 (4.12165.1700.2)
  3. K2 smartforms Control Pack 4.6.10 (4.13180.1710.2)
  4. K2 for SharePoint 4.6.10 (4.13350.1720.2)
  5. K2 Language Pack 4.6.10 (Preview) (4.13500.0.1)

Prerequisites:

See the K2 installation and configuration documentation for a full list of prerequisites. In this release the following prerequisites have been added or changed:

  • PowerShell 3 or greater is required.
  • SharePoint Online Management Shell (K2 will automatically install this for you when you run the K2 for SharePoint 2013 installer or the K2 Update Package).

Upgrades:

In this release K2 is introducing the K2 Update Package. This installer makes it easier and quicker to update your environment by adding new files and only updating files that have changed. The K2 Update Package updates all the K2 components (blackpearl, smartforms, Control pack, K2 for SharePoint) so you do not need to download and run multiple install files.

Refer to the table in the Download section or to the compatibility matrix to see if your current K2 version can be upgraded to K2 4.6.10.

The K2 Update Package automatically identifies what components are installed in your environment and will then update the components.

Note: If you are on a K2 version prior to K2 4.6.9 you must use the K2 Installation Package to upgrade your environment.

Update Step: Run the K2 Update Package on each machine (e.g. servers, web servers and client machines) where K2 components are installed. The K2 Server must be updated first, then update all the other servers in the environment. If K2 for SharePoint 2010 or K2 for SharePoint 2013 in 2010 mode is being used, the K2 for SharePoint Configuration wizard needs to be run. The Finish Panel will display the link to launch the K2 for SharePoint Configuration Wizard

For more information see the K2 Update Manager topic in the product documentation. 

Additional information:

  • If you are upgrading from a version prior to K2 4.6.9 and you use K2 for SharePoint 2010, you will need to run through the K2 for SharePoint Configuration Wizard. If K2 for SharePoint 2013 is being used, the K2 App will need to be re-deployed to the SharePoint App Catalog by running the Appdeployment.exe.
  • If your environment is using impersonation and Kerberos manual configuration is required when upgrading or setting up your environment. For more information see KB001607 – Delegation Settings to Allow Impersonation with Kerberos.
  • .NET 4.5 required by the K2 Setup Manager.
  • If you are currently on Windows Server 2008 R2 you will require Windows Server 2008 R2 Service Pack 1 when upgrading.
  • The K2 Server (Host Server) requires .NET Framework 4.5. Ensure that you have .NET 4.5 installed on the server before upgrading or installing.
  • PowerShell 3 or higher is required by the K2 Setup Manager.
  • Refer to the Important Considerations section above before installing or upgrading.
  • Ensure that you have the correct permissions to run the install to avoid installation issues. For the correct installation permissions refer to the installation and setup guides.

 

Labels: (1)
Version history
Last update:
‎05-20-2021 05:51 AM
Updated by:
Contributors