KB001629

Introduction
 

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

Known Issues

Choice

• All the display types do not have the Borderless property.  The borders can still be changed through the Style Builder by selecting "0px" for the border option.
• The Choice control does not surface in the "Execute a method on a control for values that are in a specific state" rule action.
• A validation error occurs when selecting ID as the value when binding a data source to the control. This control requires a value of a text or memo data type to be used as the data source value.
• No support for the Multi-value data type.
• The Choice Control does not have a watermark property.

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.
• A validation error occurs when selecting ID as the value when binding a data source to the control. This control requires a value of a text or memo data type to be used as the data source value.

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.
• 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.
• 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.
• The font MS Sans Serif is not supported. This option is not available in the "Font" options of the Rich Text control formatting toolbar.
• There is no validation performed on the HTML in HTML edit mode. Ensure that the HTML is correctly entered to avoid badly formatted HTML.
• When a formatted text with a non-default font size is highlighted in Firefox, the font size of the toolbar menu reverts to the default size of 11px. The text reverts to the correct font once not highligted anymore.
• Order of indentation tool items changed between RC and RTM. In the RC release the order was:
  [X] [Increase Indent] [Decrease Indent] [X] In the RTM release the order will be: [X] [Decrease Indent] [Increase Indent] [X] After upgrading from RC to RTM the existing controls on the Form will not automatically detect this change. Users are recommended to edit the items design time property and save the changes on the Form. No functional issue will be experienced if the edit is not made.
• When the HTML mode is selected in the design time properties of the Rich Text Control for an Editable List View, the control is not accessible at runtime and appears disabled. This is applicable in Internet Explorer and Firefox browsers.

Reporting

• When running the Workflow Instances Grid report the Current Activity column is not displayed.
• 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.

Worklist

• Once the layout property on a Worklist control is set to Simple, attempting to change the layout back using the backspace keyboard key does not change the layout back to Grid.
  Workaround: Change the layout in the pop-up.
• When a border is applied to the Worklist control, the border displays as a double border at design time and runtime.
• Changing any control property removes the control's overflow vertical scrollbar in design time.
• Redirecting a worklist item to the same user, removes the item from the worklist.
• 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.
• When using the Worklist control on a non - English environment and a date filter is created (Activity Start Date, Event Start Date, Workflow Start Date) the refresh button goes into error state.

General

• No keyboard accessibility support.
  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.
• When both of the following values are set to false in the web.config file, the user is presented with a "Uncaught SyntaxError: Unexpected token <" error when trying to open K2 smartforms in design time:
  <add key="Forms.PostRenderCombining.Enabled" value="false" />

  <add key="UseBundledFiles" value="false" />
  Workaround:
  Set both values to true