K2 smartforms 1.0.2 (4.12165.1575.1) Known Issues List

KB001573

SEE ALSO KB001411 - Known Issue: When disabling a View using the Properties section on a Form, all other Views on the Form are subsequently disabled at runtime
KB001412 -Known Issue: “Error 2601, Level 14, State 1, Procedure aCheckOutEvents, Line 121:…” received when checking out a View or Form with subviews or subforms in K2 smartforms 1.0.2

The following issues are currently known for the K2 smartforms 1.0.2 (4.12165.1575.1) and include workarounds where possible.

SmartObjects

• An error occurs when two SmartObject associations are configured using the same SmartObject with a Many to Many relationship.
• An error stating "ManagedRuntimeError System.ArgumentException: [Arg_ArgumentException] Arguments: Debugging resource strings are unavailable..." occurs when scrolling down the page while editing a SmartObject.
• When using Forms Authentication on the environment and creating a PDF from URL with the PDF Converter, the PDF is not rendered properly. This is due to the PDF being created upon load of the page and the login screen is displayed when the page loads
• When using one of the PDF Converter methods in an Advanced SmartObject and exposing the properties through the methods, the required properties for each method might be overridden and cause exceptions at Runtime.
  Workaround: Either create a SmartObject per method or de-select all required properties in the SmartObject Designer

Views

• A List View designed to render Images and files from a SmartObject will not display the image or file when the link is clicked if the bound SmartObject does not have a READ method. In a List View the Image/File properties will not be populated by a List method, but would rather be loaded asynchronously causing a separate call to be made to the SmartObject, to read the contents of the file. The file handler will look for the first READ method on the SmartObject, that returns the relevant File/Image property. If the SmartObject does not have a read method that fits this criteria, the file will not be loaded.
  Workaround: Add a READ method on the SmartObject that returns the File/Image. For example:
  1) This could be by adding the READ method for a table that was generated by the SQL Service.
  2) Create another stored procedure that will return the Image/File for a specific parameter and then add this to the SmartObject. Note: The Service Object method will now be of type LIST, but will need to be mapped to a READ method in the SmartObject, so that it only returns one value.
• Issues that could occur when using the SaveAsPDF control:
  a. When running a View that contains a Save As PDF control and a Silverlight control such as the 'File attachment with Progress' will cause Silverlight to stop functioning. Note that this is an intermittent issue and it is recommended that the PDF Asynchronous method is used when Silverlight controls are added to a Form to prevent this issue from occurring.
  b. When viewing a generated PDF certain display controls such as the Picture and Content control do not render correctly. In certain scenarios depending on the specified size of the control, parts of the control’s data appears cut off in the PDF.
  c. A View or control could display over two pages rather than displaying on one page when viewing a generated PDF. Currently there are no settings to create page breaks within the PDF.
  d. Viewing a generated PDF of a Form that has a tab containing a single control will not display the entire control but rather parts will appear as cut off.
• An exception stating "Parameter name: array" is thrown when attempting to check in a View containing multiple Form/subForm instances.
  Workaround: Check in the subForm prior to checking in the parent View.
• Deleting the foreign key property and association from a SmartObject will cause that the view cannot be edited and an infinite spinner is displayed.
• The following error is displayed at runtime on an Item View where a Merge Cell Down function has been used: "TypeError: 'null' is not an object (evaluating 'toRow.ref')" "function updateTableArray has corrupted the table array"
• Changing the "Watermark" property on a Check Box List control on a View will cause the existing rules to disapear.
• Configuring a filter on a View of a SmartObject method will result in only the first two filter arguments being used in the runtime execution.
• If a control is changed On a View for example a Button control is changed to a ToolbarButton control, all associated rules are removed.  
• When attempting to transfer data from one [ListDisplay] to another in a List View, the wrong data is surfaced at runtime. Currently, the transfer of data between controls in the body template of a List View is not supported.
• Picker control does not resolve user Display Names from Active Directory that contain a space or are double barrelled.
• At runtime on an Editable List if a multivalue SmartObject property is used and items are selected in the checkbox list control and the List is saved an error occurs. The multivalue column shows the selected IDs but not the corresponding display values.
• Using the List View filter at runtime to search on dates does not function correctly and the data that is returned is incorrect.
• There is no 'Does not contain' operator available on the View runtime filter.
• In the View Designer you are unable to resize a row vertically.
• The Column size of a List or Editable List View cannot be adjusted at runtime.
• When large font sizes are applied to Controls in a View such as Textbox, TextArea, Calendar, Lookup and dropdown will result in the control displaying at runtime with a scrollbar rather than the control resizing itself.
• Dragging and dropping a button control onto a View will result in an empty system event being created for the Onclick event.
• Dragging a column in a List or Editable List View to a new position causes all the columns to resize to half the total drop column area. While designing a List View in the View Designer, merging a cell containing a Table Control with controls will remove the controls from the Table Control and add them to the current cell.
  Workaround: 1. Merge the cell containing Table controls before adding Controls to the table. or 2. Don’t merge the cell containing the Table, but merge the cell on the left of the cell with the cell containing the Table control.
• On a List View where Paging is enabled you are unable to sort according to the values in an unbound column.
  Workaround: 1. Save data to a field and bind the column to the created field.
• It is not possible to use a field in an expression on a control that is bound to the same field on the View.
  Workaround: 1. On a List View: Drag a datalabel control to the bound column and configure the datalabel with the same expression using the desired field. 2. On an Item View: Drag a corresponding control to the design canvas and configure the control using the desired field.
• The following error is displayed when a SmartObject property control on a View is changed to a Lookup control and a Data Source is linked to the Lookup control: "an item with the same key has already been added" 
  Workaround: Click OK on the error message and continue with the set up. The Data Source will be added.
• When searching an Editable List which contains associated controls such as dropdowns for example, extra fields are available on the View which are also taken into consideration when performing the Quick Search. When searching All Fields or All Visible Fields some of these extra fields might be included with the List View’s filter to execute the GetList. Filter Exception messages might be displayed as a result.
• When using the default PDFFile SmartObject on a View or Form, without configuring the Data Source on the Save as PDF control, the SmartObject does not reflect in the context tree of the Rule Designer.
  Workaround: Open the Data Source configuration of the Save as PDF control and manually re-select the PDFFile SmartObject.
• When changing a control on a View to a Content control, the Content control is not displayed properly and is difficult to select.
  Workaround: Click on the speck and provide width and height values for the Content control.
• When using the Content control and the hosted page employs responsive design the horizontal scrollbar does not show in the Chrome Browser. If the content does not overflow in the direction for which the user has explicitly set the scrollbar to show, it won’t show.
  Workaround: Edit the hosted page if possible and alter the styling of the ‘body’ element setting the ‘overflow-x’ and ‘overflow-y’ options to ‘scroll’ as required, where the ‘x’ axis is horizontal and ‘y’ is vertical.
  To show the vertical scrollbar, the body element needs to be styled as follows:
  <body style-"overflow-y:scroll">
  
  To show the horizontal scrollbar, the body element needs to be styled as follows:    
  <body style="overflow-x:scroll">
  To show both scrollbars, use both options as above.

Forms

• When editing a Form which contains a View that is being edited by another user, if an action is deleted the Form is held in a state that cannot be saved.
• When a Form contains an underscore in the URL, SmartForms double's the underscore when the URL is generated. This in turn causes problems when the Form is hosted  elsewhere when URL validation is performed, for example in SharePoint where the double _ is removed and replaced with a single one when it attempts to render the Form.
• If a view is checked out by UserA and UserB tries to check in a Form that contains that View an error stating "cannot check in a Form with checked out views" occurs. The error message gives the option to check in the relevant Views, however, when selecting 'yes' a further error is received stating that the View is checked out by another user.This prevents the Form from having multiple designers working on the same project.
• Currently no more than 8 tabs can be added to a Form.
• When editing a Form where the Form title had previously been changed, saved and checked in the orginal title is displayed rather than the new one.
  Workaround: Rename the Form on the “Details” tab rather than on the Layout > Context Browser Form properties.
• The Form design canvas does not scroll horizontally when attempting to drop a View to the right of another View.
  Workaround: Use the right arrow button on the keyboard to move the Form to the far right. Then drop the required View in the drop zone.
• In the Forms Designer you are unable to change or resize the view after it has been dragged onto the Form.
• Changing the orientation of a View, for example changing a row to a column will result in the disproportionate rendering of a Form.
  Workaround: 1. Make the required orientation changes. 2. Finish the Form wizard. 3. Edit the Form again and click through to Finish. 4. The Form will render correctly now at Design and Runtime.
• An error occurs if there are two checked out Forms using the same View with a new rule defined on Form level for an event on both the Views. The first Form must be checked in after the second Form.
  Workaround: 1. Accept the error message. 2. Check in the lastest (second) Form 3. Check in the earlier (first) Form.
• When using multiple instances of the same View in a Form will result in the Form Rules and Expressions on the subview not executing as expected.
  Workaround: Create duplicate Views of the View to be used multiple times, by using the Save As functionality and providing a new name. This will ensure that unique instances of the View are used on the Form and the rules and expressions will execute correctly.
• When creating a Form that consists of many Views and multiple States the Form rules are not visible after adding an additional State. This issue occurs when the Form definition increases and exceeds the "Maximum Request Length" specified in the web.config.
  Workaround: Open the web.config of your SmartForms site, find the following entry: <httpRuntime maxRequestLength="8192" /> and change the value to a larger number. The maximum allowed value is "2097151".
• When using the default PDFFile SmartObject on a View or Form, without configuring the Data Source on the Save as PDF control, the SmartObject does not reflect in the context tree of the Rule Designer.
  Workaround: Open the Data Source configuration of the Save as PDF control and manually re-select the PDFFile SmartObject.
• When using the Properties section on the Form layout step to disable a View, all other Views on the Form are subsequently disabled in runtime. As a result Rules will not execute as expected.
  Workaround: Rule Actions can be used to enable or disable Views on a Form.

Rules

• In the rule designer the textbox for an expandable area on the Mappings screen doubles in size when the textbox area is collapsed and populated with a value.
• When configuring a rule to transfer data on a picker control changed event the SmartBox SmartObject data fails to  transfer.
• When configuring a rule on a View and the " Send an E-mail" action is configured, it is not possible to add an attachment to the message as the Attachment Control is missing.
• Changing the Dropdown List control's properties on a View will cause the "Populate a List control with data" to be added back to the "View executed Initialize" Rule after it was explicitly removed.
• Unexpected behavior is experienced when the 'Show a message' action in the Rule Designer is configured. For example, creating a space between fields that have been dragged and dropped onto the message body moves each context field to a new line.
  Workaround: Create the space or line break before dragging the required context field into the message body field.
• The following issues are known when using the 'Send an e-mail' action in the Rule Designer.
  a. More than one e-mail address can be added to the From field.
  b. The To field is not a required field.
  c. Only the first person in the To field receives an e-mail
  d. HTML is an available option but only Plain text is supported at present.
  e. The attachment icon is missing which only allows items from the context browser to dragged and dropped in the attachment field.
  f. Unable to change font or font size.
• When the All Controls Validate checkbox is selected while configuring the condition 'the form passes validation' in the Rule Designer, at runtime the Form will not function as validation is expected on column headings which is not possible. Workaround: Do not use the All Controls Validate checkbox but rather check the Validate checkbox for each individual control listed.
• When using the "Execute a method on a control for values in a specific state" Action and selecting anything other than Checked or Unchecked, the error "One or more actions could not be transformed" is displayed.

Workflow Designer

• If the SmartObject used in the item Reference configuration is changed and deployed the Item Reference will not continue to function correctly.
• Unable to use Chinese characters for new workflow description.
• When a workflow is built and deployed, a duplicate 'Rule Action' entry is created in the Action Settings screen when an activity's name is changed after its first deployment.
• Issues are encountered when workflow data fields have the same name as a standard data field, for example Priority. The workflow field is applied to the standard field rather than to the custom data field.
• An error is displayed when opening the Workflow Designer using Safari Version:5.1.7 as the browser
• The PDF control is not surfaced as a Form Control in the Context Browser of the Workflow.
  Workaround: Use a Form Parameter (or hidden textbox) to store the value of the PDF control.

SmartForms Workflow Integration Wizards

• In K2 Designer for Visual Studio when using the SmartForms Client Event wizard the ellipsis buttons in the Action Display Settings do not function.
  Workaround: Type in the required text or field data.
• In the SmartForms Integration Wizard it is not possible to drag an XML field into the process data fields input box after supplying the page field first.
• The two radio buttons namely, 'Use Default Version' and 'Bind Page Version to Process Version (on Deploy)' found on the Select Page and State screen of the SmartForms Client Event wizard are currently disabled and cannot be used.

SmartForms Web Part

• An error stating "Web Part Error: Cannot import this Web Part" is displayed when a SharePoint 2010 Site Template containing the SmartForms Web Part is imported and a sub site is created from the template.
  Workaround: Configure the SmartForms Web Part manually.
• When using SharePoint 2013 and trying to add a Form to a SharePoint Page through the SmartForms Web Part, the FormsServer in the Connection Settings does not retain the  selected Form.

Browsers

• Applying a style to a label with "No Color" causes the Form not to load in Internet Explorer and javascript errors occur. Since "No Color" is selected during desing time, a # value is assigned at runtime and Internet Explorer does not recongnize hash values as valid CSS colors.
• Silverlight is not supported when using the Chrome browser on a Mac operating system. This will result in issues when working in the K2 Workflow Designer which requires Silverlight. For more information on Silverlight and browser support see http://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx. • Silverlight is not supported when using the Safari browser on Windows operating system. This will result in issues when working in the K2 Workflow Designer which requires Silverlight. For more information on Silverlight and browser support see http://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx.
• Issues with SmartObjects and Views will be experienced when using Internet Explorer (64 bit) as Silverlight is not supported on 64 bit.
• At runtime using Safari as the browser a Form containing a View in which a SmartObject property is of type memo, will result in the scrollbar not displaying when data is added. Workaround: Set the default row's value to at least 5 in the designer under the control properties.
• When selecting a few activities in the Workflow Designer with the left-mouse button and then clicking on the "Save as Template" option will result in an error that states "The clipboard isn't available in the current host". This applies to all browsers except Internet Explorer.
  Workaround: a. Open K2 Designer in Internet Explorer 9. b. open the workflow. c. Select the activities and right -click. d. select "Save as Template".
• In Internet Explorer 8 when setting a Lookup control's Read-Only property to true causes the Lookup's control button's opacity to be very high appearing almost invisible.
• Hosting View Flow in a Content Control in SmartForms Runtime overrides the placement of other controls.
  Workaround: When running a Custom Control that points to Silverlight objects or when using a URL that references Silverlight controls in a Content Control, it is recommended to use windowless mode to ensure that the artefacts are shown.
• The following error occurs when using Claims-based Authentication with Safari as the browser: Unexpected end of file. Following elements are not closed: Cookie, SecurityContextToken. Line 1, position 2998.

General

• Issues will be experienced when using K2 smartforms on an Android or Windows mobile device.
• The validation function on Expressions at design time does not validate field Types correctly which could result in an error at runtime.
• An error stating "Illegal operation attempted on registry key that has been marked for deletion" may occur when trying to use the K2 Designer when smartforms is installed in an environment using a Windows Server 2008.
  Workaround: Restart the K2 Server.
• When renaming an existing Category a user is able to rename the Category to that of another existing Category and thereby creating a duplicate category.
• When an i button is clicked in the K2 SmartForms Runtime site a 404 error will occur. The i buttons affected are:
  • Login screen
  • Hyperlink popup
  • Picker search modal
  • List View Filtering popup
  • Advanced Filter option
  Workaround: 1. open the Design Time site. 2. Browse to [install drive]k2 blackpearlK2 SmartForms Designer and copy the Documentation folder. 3. Browse to the Runtime Site and paste the Documentation folder in [install drive]k2 blackpearlK2 SmartForms Runtime.
• When creating a workflow in K2 Designer for SharePoint the user is able to click Next without selecting a Form on the User Form screen even though the Form and State fields are marked as mandatory.
  Workaround: Navigate back to the User Form screen and reconfigure by selecting the required Form and State.
• In the K2 Designer For SharePoint, if a user configures a SmartForms User Task with a newly created Form that has not been checked in at least once then deployment will fail. This issue only occurs when a Form is created for the very first time.
  Workaround: Check the Form in before using it in the User Task. Once the Form has been checked in, the workflow deployment will succeed, even when it is checked out again.
• In the K2 Designer for SharePoint after upgrading to K2 smartforms 1.0.2, the SmartForms User Task > Form Selection might not reflect all the nodes to be expanded in order to select sub-folders or Forms.
  Workaround:
  1. Navigate to SharePoint Central Administration > System Settings > Manage Farm solutions
  2. Select the K2 for SharePoint – K2 Designer smartforms client event.wsp solution
  3. Retract the solution
  4. Re-deploy the solution after the schedule retraction