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

• 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.

• Backward compatibility was broken on the BuildWhere method of the AbstractFilter class in K2 4.6.9.

• 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.

• When multiple stored procedures are executed simultaneously, deadlocks are experienced on cServerLog.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’

• When moving K2 databases from one environment to another and running a reconfigure via the installer, a ‘Symmetric Key Invalid’ error is received.

• 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

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 ‘Tobject 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.

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.

Forms:

• Out of the box pages fail to render correctly when run on a SharePoint site that contains branding or custom master pages.

• 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’.

• 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.

• 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.