Introduction

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

Controls

  • When a control is added to the 'aggregation footer' of a List View and configured to be hidden, the control is not hidden at runtime.
    Workaround
    Make the width of the control 0.
  • Setting the Tab Index to None on the Radio Button Group or Radio Button List control is ignored at runtime in Internet Explorer 8 and 9. Furthermore, when a subview or popup window is opened it is possible to tab to the Radio Button Controls behind the subview or popup in Internet Explorer 8 or 9 even if the tab Index property has been set to None.
    Workaround:
    Set up a rule so that when a subview or popup is opened, the Radio Buttons in the View behind the popup are disabled. When the subview or popup is closed the Radio buttons should be enabled again.
  • The available controls displayed in the Change Control window are inconsistent, resulting in some controls not displaying when they are expected to.
    Workaround: Delete the control and add the correct control type from the toolbox instead.
  • The serializeResources and useWebkit SmartObject Service Instance settings have been added to the PDF Converter SmartObject Service. These settings are turned off by default preserving the previous behavior. To understand how to use this new functionality and to enable error logging see KB001626. The following known issues occur only when the useWebkit setting is turned on and when using the following SmartObject Service Methods “Create PDF From URL” and “Create PDF From HTML or URL” (when passing in a URL and not HTML). Note that none of these issues affect the Save As PDF control.
    • Impersonation issue: The PDF creation will be attempted twice. The first attempt using impersonation will fail with an unsurfaced error message. The second attempt will succeed.
      Workaround:
      Set the service instance authentication mode to “Service Account”.
    • PDF creation issue: The PDF creation will periodically fail with an Unknown WebKit error message. This is as a result of the engine not handling Claims based authentication correctly.
      Workaround:
      This is resolved by duplicating the runtime site folder, creating a new web application in IIS and setting the authentication of the site to use Windows authentication and not Forms authentication.
    • Blank PDF issue: Directly after performing an IIS reset, the generated PDF may appear blank. This is as a result of the engine not handling Claims based authentication correctly.
      Workaround:
      This issue is resolved by duplicating the runtime site folder, creating a new web application in IIS and setting the authentication of the site to use Windows authentication and not Forms authentication. In addition a conversion delay of a few seconds should be set or the site should be warmed up before creating PDF’s after an IIS reset.

    Designers

    • When removing a parameter referenced in a rule, upon editing the rule the specific parameter is displayed as "Unresolved".
      Workaround:
      Remove the unresolved parameter reference.
    • It is possible to delete the validation patterns that are available by default in K2 smartforms. If the pattern is deleted an error occurs after upgrading to the newer version of the software as the installer is unable to find the validation pattern.
      Workaround:
      If you have deleted a default validation pattern run the configuration option available in the K2 smartforms Setup Manager to restore the patterns.
    • When clearing the Styles property field with the backspace or delete key and selecting Yes on the confirmation message box, produces a JavaScript Error.
      Workaround:
      Open the Style Builder and click on Reset.
    • Attempting to change an activity's outcome that will cause a recursive deletion, results in the designer crashing. For example:
      • Step A with outcome linked to step B
      • Step B with outcome linked to step C
      • Trying to change Step A's outcome from B to C will cause the designer to crash.
        Workaround:
        Using the example mentioned above, deleting the activity represented in step B will automatically link step C’s activity to step A.

Integration

  • When deleting the View Initialize rule from a View, after editing the properties of a control on the View, the rule gets added again.
    Workaround:
    Remove the Initialize rule after all control properties have been changed.
  • No multi-language support in K2 smartforms.
    Workaround:
    A multi – language control is available on Market in K2 Community that can be used with SmartForms.

Rule Designer

  • The SmartObject property mapped to a View parameter doesn't save successfully when both the View and the SmartObject property uses the same name.
    Workaround:
    Change the name of the View/Form parameter to be different to the SmartObject property.
  • When the Finish button on the Rules Wizard Configuration is clicked, a disabled View action is enabled on Form level.
    Workaround:
    Disable the action/rule on Form level.
  • When opening the same subview multiple times as part of the same action using If conditions, the subview references are duplicated.
    Workaround:
    Only open the subview once and use a parameter as a flag to determine which action was used to open the subview.
  • When editing a SmartObject and changing the output mapping, the rule mapping is removed instead of being updated.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • No nested For Each conditions functionality available in the rule designer.
    Workaround:
    At the time of this version’s release date, there was no known workaround for this issue.
  • Inconsistency between the behaviour of if conditions and other handlers such as Else or “if an error occurred”. This can be demonstrated by selecting to disable an if condition. Only the condition is disabled, where the condition and all it’s child actions are disabled when selecting the same option for “if an error occurred”.
    Workaround:
    Manually perform the action required.

Runtime

  • When deleting a control that is bound to an expression and then running the Form, an error occurs stating: "Unknown control missing". The Form becomes unusable.
    Workaround: Remove the unresolved control reference in the Expression Builder.
  • If a Radio Button List control is set as borderless, no validation is done when the rule executes.
    Workaround:
    Change the border colour to the same colour as the background so as to create the illusion that the control is borderless.