Issue: When using Internet Explorer 9 and selecting to Run in a new window on the landing page as shown below, the behavior might be different than expected. Depending on the settings used in Internet Explorer, a new tab might be opened instead of a new window.
Resolution: To get the expected behavior, the Internet Explorer settings have to be changed. Select Internet Options from the Internet Browser. Click on Settings as shown below:
Change the options as shown below and select A new window:
Issue: If a K2 smartforms browser session is left unattended and trying to access it again,an error may occur. This is due to the application trying to renew the session but the browser is blocking the renew pop-up dialog.
Resolution: Click on the pop-up dialog window, allow it to open and then sign in again
Issue: K2 uses the built-in compression of Internet Information Services (IIS) and Browsers to compress content over the internet allowing quicker and more responsive user interfaces. Both the packet size being issued by the K2 smartforms server and the packet size received by the client browser should be compressed. If there are notable differences between these two packet sizes, data compression is probably not configured correctly in IIS or proxies.
When rendering Forms over the internet, data compression might not be applied by the company who is accessing the Form which will cause different sizes in the Form being rendered at source and the Form being accessed on the client browser.
Data compression is not a K2 issue and requires the environment administration of the company who is trying to access the K2 Form to sort out.
Enabling data compression on the company wide will have side effects on other public websites (sites heavily using Ajax). Customers can setup filters on the gateway to check response headers and decide whether to enable compression or not. For reference purposes, see the following links:
Forefront Threat Management Gateway (TMG)
http://technet.microsoft.com/en-us/library/cc995193.aspx
ISA Server 2006
http://technet.microsoft.com/en-us/library/bb794746.aspx
ISA Server 2004
http://technet.microsoft.com/en-us/library/cc302509.aspx
Resolution: In order to compress data over the internet, the data compression settings need to be enabled on the environment.
The sample debugging used in this example is using Google Chrome’s developer tools.
It is important to note that Internet Explorer only reports on uncompressed sizes. If a Google Chrome browser is not available, it is recommended to use something like Fiddler or FireFox with FireBug installed
If there is a big difference in the size of the values, compression in the environment is enabled and working as expected.
If an item such as Content-Encoding is visible, compression was used when the client browser rendered the Form.
When both the Size and content values are the same or almost the same size, the environment potentially have a "compression not allowed" issue. To verify that no content compression has been applied, follow the steps in the Verify if compression was used when the client rendered the Form section above. The Content-Encoding item will not be listed. This is typically the case where Microsoft Internet Security and AccelerationServer (ISAServer) is used which does not allow compression. Contact the system administrator for further assistance as this is not a K2 product issue.
Another potential cause for content not being compressed could be that the dynamic and static content compression settings have not been enabled in Internet Information Services (IIS). Open IIS and click on Compression in the IIS section. Ensure that both the dynamic and static content compression settings have been enabled as shown in the image below. The IIS web server role features also need to be installed.
Issue: When Windows Authentication is enabled and using the NTLM provider with extended protection; the PDF Broker will fail.
Resolution: The server name needs to be added to the list of local intranet sites.
Issue: After creating a custom Task in the K2 Workflow Designer, a Worklist item could not be loaded error occurs when trying to open the worklist item.
Resolution: Check if the Parameter used for the serial number in the custom task corresponds with the default used in K2. The default is SerialNo. Change the parameter to be the same as the default.
Issue:The Content control does not load because of an HTTPS protocol error.
Resolution: This is standard browser behavior and applies to any website with an IFrame hosted on an SSL page. If you have a parent site that is HTTPS the IFrame URLs (Content control) must also be HTTPS. You can get around this by not accessing the form via HTTP or by changing the URLs used in the Content control to HTTPS.
It is also possible to change the default behavior of Chrome to allow the insecure content:
See the following links for more detail:
http://www.chromium.org/developers/how-tos/run-chromium-with-flags
http://stackoverflow.com/questions/14058789/how-to-force-loading-dynamic-insecure-content-in-chrome
Issue: Certain URLs are not displayed correctly and a browser console error is displayed.
Sites often disallow their content to be displayed in an iframe. The site is blocked by the site in question from being allowed to display in an iframe such as the Content control.
https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options
Resolution:
For example to use google maps in a Content control you need to use a specific url and include an API key. You need to use the embedded API with a valid API key as google and others have prevented using the other url in an iframe.
https://developers.google.com/maps/documentation/embed/guide
Issue:
You cannot open HTTP sites from a HTTPS parent site and vice versa.
http://javascript.info/tutorial/same-origin-security-policy
Resolution:
Issue: Internet Explorer 8 (including any other Internet Explorer version running in IE8 compatibility mode) is no longer supported. When running a SmartForm in IE8 or earlier compatibility mode; or the Forms Viewer web part in SharePoint 2010, you'll be presented with a message screen that states that the browser is not supported.
See the following KB articles for more information:
Issue:The NPAPI setting for Silverlight is disabled by default for Chrome 42.
Resolution:
Video | Links | Learn | Support |
No videos found for this article K2 on YouTube
No Additional links found for this article
No self-learning content for this article Try some scenarios...
No relevant support links available for this article
|