Note the following known issues about the CygNet Thin Web Client:
Canvas File Names
Spaces in Canvas screen file names are valid when saving screens Canvas for view in the Native target environment; however, spaces are not permitted in a Thin Web Client page directive (URL). A Canvas screen file name for a screen intended to be viewed in the Canvas Native view is limited to the following characters: a-z A-Z 0-9 -._~. No special characters are permitted, other than -._~. Spaces in Canvas screen file names are valid when saving screens for use in the Canvas Native view only.
A Canvas screen file name for a screen intended to be published and viewed in the CygNet TWC web view is limited to the following characters: a-z A-Z 0-9 -._~. No spaces or special characters are permitted, other than -._~.
The TWC publishing service contains a file name check to detect spaces and invalid characters in a Canvas screen file name. If your screens have invalid characters in their file names, and the target environment is Web client, you will see an Error in the Publishing service when publishing these files, which will be reported in the Details pane on the Publishing page in Backstage view > Web Settings.
Canvas Application Names
The TWC application name can only contain letters and numbers. Spaces or special characters are not permitted.
Save Canvas Files in BSS
All Canvas screen files (and any associated images) intended for inclusion in a Thin Web Client application must be saved in a folder in the BSS.
Missing Files
The Publishing service will detect when a hyperlinked file or folder (e.g., a screen hyperlinked from a Navigation Button or CygNet Grid) is not stored in an application’s Blob folder or does not exist. The whole application will fail to publish, and you will see the following Publishing Exception error in the Error details on the Publishing status page:
Hyperlink target folder is not included in the application.
To prevent this issue, we recommend that you move the hyperlinked file to the application’s Blob folder or include the hyperlinked file’s Blob path in the application.
ACS Changes and Login Issues
The TWC server (and sometimes Canvas) doesn't always respond immediately to a change in the ACS. If you can't access to your application menu or other pages in the CygNet TWC web view, after configuring ACS security events and attempting to login, try forcing a browser refresh to clear the browser cache and/or browser history, and reload the page.
-
Force Refresh — Note that different operating systems and browsers use different commands or shortcuts to force refresh the browser. In Chrome or Edge on Windows, the keyboard shortcut Ctrl+F5 (or Ctrl+Reload) refreshes. On a Mac, hold Cmd-Shift-R or Shift-Reload. Most browsers also have a refresh button next to the URL. For Safari on a Mac right-click on "Safari" at the top left of the page and select "Empty Cache". Confirm your choice, then reload the page. For Windows, click the "Alt" key to reveal the menu bar. Select "Edit" – "Empty Cache". Then confirm the selection.
Republish All Applications After an Upgrade
The Publishing service will detect when a TWC system has been upgraded, but previously published applications have not been republished. After completing an upgrade (either after a fresh install or keeping TWC as it was), you must republish all previously published applications (using Soft publish on the Server page). If you don't republish all previously published applications, any subsequent publishing attempt will fail, and you will see the following Publishing Exception error in the Error details on the Publishing status page:
The Publishing service is in a migrating state. Please initiate the migration process (run Soft publish on Server page).
Facility Sending and Receiving
The Screen can be a facility sender and a facility receiver. It is a valid Canvas configuration to have controls source their facility from the Screen and have the Screen source its facility from another control.
Say you have a Tag Chooser as the facility source of a Grid and the Grid is the facility source of the Screen. On the same screen you have some Text Tools and other single-point controls (e.g., a Donut) sourcing their facility from the Screen. In this scenario the Tag Chooser sends a facility to the Grid, the Grid sends the facility to the Screen, and the Screen then sends the facility to a Text Tool or the Donut. This configuration works in the Canvas Native view. However, this configuration does not work in the web client. The workaround for a TWC page is to use the Grid as the facility source for all controls that use the Screen as the facility source.
Color on Thin Web Client Pages
Color configuration and presentation is handled a little differently in the Thin Web Client. Control properties for elements that specify color configuration (e.g., backgrounds, text, borders, grid columns and cells, Donut rings, markers, bars, etc.) offer the following color source choices:
- Auto — the element follows the color theme selected for the client
- Point State — the color corresponds to the point state color of the associated point
- <Self> — a default color is specified or you choose the color.
Auto color configuration is not supported as a color source in Canvas control properties in screens to be used in a Thin Web Client application because TWC does not support themes in the CygNet TWC web view. If a property specifies Auto for color configuration, the screen will use the <Self> color that is specified in the Canvas file during the publishing process.
Scalable Vector Graphics (.svg) in Thin Web Client
While Canvas and the Image control support .svg file types, we have observed that not all .svg files are compatible with web browsers. If you select an .svg file that is supported in Canvas, but not in a web browser, it may not display correctly in the CygNet TWC web view. We recommend opening the .svg file in a web browser to check that it opens and displays correctly. If it does, then it should be supported by the CygNet TWC web view.
Object Files in Thin Web Client
Canvas object files (.cob) are generally not supported in the CygNet Thin Web Client, with the exception of an object file used as the reverse side of the Detail control when flipped. Object files created for this purpose must following the TWC naming and storage rules: no spaces in the file name, no special characters, and the .cob file must be saved in a BSS folder, preferably in the same folder as the screen file with the Detail control. Note that while many of an Object's properties are visible in the Canvas user interface, they may not be supported in an object file created for a Detail control. Consult the Object Properties topic for more information.
Chart X-Axis Labels
We have observed overlapping date and time labels on a chart's x-axis when displaying a large number of data points in a narrow chart in the CygNet TWC web view.
