Introduction

The following issues are currently known for K2 smartforms Control Pack 4.6.9 and include workarounds where possible.

AutoComplete

  • No support for the Default Value of SmartObject data.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.

Choice

  • All the display types do not have the Borderless property. The borders can still be changed through the Style Builder by selecting "0" px for the border option.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • No support for the Multi-value data type.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • The Choice Control does not have a watermark.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • Multi-Value data type not supported yet.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • No support for the Default Value of SmartObject data.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.

Multi-Select

  • The Multi-Select control does not surface in the Execute a method on a control for values that are in a specific state rule action.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • No support for the Default Value of SmartObject data.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.

Rich Text

  • The Font tab in the Style Builder of the Rich Text control is disabled. The toolbar items on the control can be used instead.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When editing an item with multiple Font/Style types will result in the text defaulting to one Font type. Even if a new item with multiple Font/Style types is saved, the text is displayed as one Font type.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When a user formats HTML from one of the edit modes for the Rich Text control for example <h1>,<h2>,<h3>, the font size will be recorded as 2em, 1.5em etc. This is to allow multi browser support.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • The font MS Sans Serif is not supported. This option is not available in the "Font" options of the Rich Text control formatting toolbar.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When using Internet Explorer 11 and the default is set to Edge, no toolbar is rendered at runtime.
    Workaround:
    Change the Default mode to Internet Explorer 10 to show the toolbar.
  • When using Chrome and selecting to InsertTable at runtime, then editing or running the View or Form produces a JavaScript Error in the Developer Tools console.
    Workaround:
    Close the Developer Tools console.
  • No support for Ctrl+X.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.

Reporting

  • When running the Workflow Instances Grid report the Current Activity column is not displayed.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When configuring the Execute Control method on a reporting control, typing a text value for an input box and saving the method results in the value reverting back to the default value instead of typed value.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When using the Lithium theme and Reporting Chart controls, the headers are not displayed correctly at design time.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.

Tree

  • No support to transfer data from the Tree control to the following list controls:
    • Picker
    • Multi-Select
    • Radio Button List
    • Choice
    • Check Box list

    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • Tree control is not supported in Editable List View.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • The For Each rule conditions do not execute when applied to the Tree control.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When using a GetList method on an Advanced SmartObject as the Tree control's Icon Source, and the SmartObject has multiple List methods, no icons are returned at runtime.
    Workaround:
    Using the SmartObject Designer, change the List method that returns the icons to be the first method in the list of methods.

Worklist

  • Once the layout property on a Worklist control is set to Simple, attempting to change the layout back using the backspace keyboard key, it does not default the layout back to Grid.
    Workaround:
    Change the layout in the pop-up.
  • Redirecting a worklist item to the user himself, removes the item from the worklist.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When the Worklist Control is used in a SharePoint 2013 environment a blue icon is displayed next to each worklist item, hovering over the icon an action pop-up will be displayed to further action work items.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When using a rule to refresh the worklist when a subview or subform is closed, the action to refresh the worklist is not executed.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.

General

  • No keyboard accessibility support for the Tree control.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • When using the Change control feature, and both controls have the same property which is default, the control will be changed. If the source control property can be cleared out, the control will not be changed, but the styles will be applied.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.