Last revision: 9/6/2023
This Readme provides information about AVEVA InTouch HMI 2023 Patch 03. Readme files from previous releases of AVEVA InTouch HMI are posted on the support site.
The Web Client now supports adding start and end time to the Trend Client using script.
Syntax
TrendClient1.SetStartAndEndTimes(MyStateTime, MyEndTime, 0);
TrendClient1.GetStartAndEndTimes(MyStateTime, MyEndTime);
Limitations
The limitations of SetStartAndEndTimes script at the time of this release are:
The Industrial Graphic Editor (IGE) includes support for SVG graphics for those HMI products that can display them. However, this support has some limitations. The table below shows the SVG graphic support status for each type of element for various versions of the IGE.
Element Type |
Element |
2023 Patch01 through 2023 Patch03 |
|
Element Type |
Element |
2023 Patch01 through 2023 Patch03 |
Animation elements |
animate |
NO |
|
Graphics elements |
circle |
YES |
Animation elements |
animatecolor |
NO |
|
Graphics elements |
ellipse |
YES |
Animation elements |
animatemotion |
NO |
|
Graphics elements |
image |
YES |
Animation elements |
animatetransform |
NO |
|
Graphics elements |
line |
YES |
Animation elements |
set |
NO |
|
Graphics elements |
path |
YES |
Basic shapes |
circle |
YES |
|
Graphics elements |
polygon |
YES |
Basic shapes |
ellipse |
YES |
|
Graphics elements |
polyline |
YES |
Basic shapes |
line |
YES |
|
Graphics elements |
rect |
YES |
Basic shapes |
polygon |
YES |
|
Graphics elements |
text |
YES |
Basic shapes |
polyline |
YES |
|
Graphics elements |
use |
YES |
Basic shapes |
rect |
YES |
|
Shape elements |
circle |
YES |
Container elements |
a |
YES |
|
Shape elements |
ellipse |
YES |
Container elements |
defs |
YES |
|
Shape elements |
line |
YES |
Container elements |
g |
YES |
|
Shape elements |
path |
YES |
Container elements |
glyph |
YES |
|
Shape elements |
polygon |
YES |
Container elements |
marker |
NO |
|
Shape elements |
polyline |
YES |
Container elements |
mask |
NO |
|
Shape elements |
rect |
YES |
Container elements |
missing-glyph |
YES |
|
Structural elements |
defs |
YES |
Container elements |
pattern |
NO |
|
Structural elements |
g |
YES |
Container elements |
svg |
YES |
|
Structural elements |
svg |
YES |
Container elements |
switch |
YES |
|
Structural elements |
symbol |
YES |
Container elements |
symbol |
YES |
|
Structural elements |
use |
YES |
Descriptive elements |
desc |
YES |
|
Text content child elements |
altglyph |
YES |
Descriptive elements |
metadata |
YES |
|
Text content child elements |
textpath |
YES |
Descriptive elements |
title |
YES |
|
Text content child elements |
tref |
YES |
Filter Elements |
filter |
NO |
|
Text content child elements |
tspan |
YES |
Filter light source elements |
feDistantLight |
NO |
|
Text content elements |
altGlyph |
YES |
Filter light source elements |
fePointLight |
NO |
|
Text content elements |
text |
YES |
Filter light source elements |
feSpotlight |
NO |
|
Text content elements |
textPath |
YES |
Filter Primitive Elements |
feBlend |
NO |
|
Text content elements |
tref |
YES |
Filter Primitive Elements |
feColorMatrix |
NO |
|
Text content elements |
tspan |
YES |
Filter Primitive Elements |
feComponentTransfer |
NO |
|
Uncategorized elements |
altglyphdef |
NO |
Filter Primitive Elements |
feComposite |
NO |
|
Uncategorized elements |
altglyphitem |
NO |
Filter Primitive Elements |
feConvolveMatrix |
NO |
|
Uncategorized elements |
clippath |
NO |
Filter Primitive Elements |
feDiffuseLighting |
NO |
|
Uncategorized elements |
color-profile |
NO |
Filter Primitive Elements |
feDisplacementMap |
NO |
|
Uncategorized elements |
cursor |
NO |
Filter Primitive Elements |
feFlood |
NO |
|
Uncategorized elements |
font |
YES |
Filter Primitive Elements |
feFuncA |
NO |
|
Uncategorized elements |
font-face |
YES |
Filter Primitive Elements |
feFuncB |
NO |
|
Uncategorized elements |
font-face-format |
YES |
Filter Primitive Elements |
feFuncG |
NO |
|
Uncategorized elements |
font-face-name |
YES |
Filter Primitive Elements |
feFuncR |
NO |
|
Uncategorized elements |
font-face-src |
YES |
Filter Primitive Elements |
feGaussianBlur |
NO |
|
Uncategorized elements |
font-face-uri |
YES |
Filter Primitive Elements |
feImage |
NO |
|
Uncategorized elements |
foreignobject |
NO |
Filter Primitive Elements |
feMerge |
NO |
|
Uncategorized elements |
glyph |
NO |
Filter Primitive Elements |
feMergeNode |
NO |
|
Uncategorized elements |
glyphref |
NO |
Filter Primitive Elements |
feMorphology |
NO |
|
Uncategorized elements |
hkern |
NO |
Filter Primitive Elements |
feOffset |
NO |
|
Uncategorized elements |
mpath |
NO |
Filter Primitive Elements |
feSpecularLighting |
NO |
|
Uncategorized elements |
script |
NO |
Filter Primitive Elements |
feTile |
NO |
|
Uncategorized elements |
stop |
NO |
Filter Primitive Elements |
feTurbulence |
NO |
|
Uncategorized elements |
style |
YES |
Gradient elements |
linearGradient |
Partial* |
|
Uncategorized elements |
view |
NO |
Gradient elements |
radialGradient |
Partial* |
|
Uncategorized elements |
vkern |
NO |
(*) Gradients are supported up to 3 colors
The Windows tab is now renamed back to Windows & Scripts. The Scripts folder in Windows pane of the WindowMaker is now re-enabled. The Scripts folder is created by default on creating a new application. You can also create custom folders using the New Folder option. It allows you to organize the scripts as required.
The Windows & Scripts tab has the following right-click menu options:
InTouch HMI 2023 P03 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.
Defect ID |
SR/Case Number |
Description |
IMS-2394926 |
960277563 |
An error occurred when the user tried to open a graphic which was configured with aaHistClientTrendControl and the options Modal and Cache Industrial Graphics not embedded in InTouch Windows were selected in Show Symbol animation dialog box. |
IMS-2428264 |
960285601 |
Post-upgrade from InTouch HMI 10 to InTouch HMI 2020 R2 SP1, when the user tried to export all windows, not all windows were exported, and it affected the Cross Reference and Update Use Counts functionalities too. |
IMS-2431478 |
960285540 |
In the Alarm Pareto Chart, the configuration was changed, saved, and closed. The configuration was reset to default when the window was reopened. |
IMS-2435617 |
960284372 |
During navigation in an Industrial Graphic, a random graphic was fetched and moved to a different location or folder when the mouse pointer was moved outside the scroll bar and subsequently released. |
IMS-2444650 |
960284433 |
In Alarm Client Control, when set the Client Mode as Historical Alarms and Database Name as History Blocks, applying a filter to the OperatorFullName column filtered the Operator column rather than OperatorFullname column. |
IMS-2446860 |
960289215 |
On screens with the resolution 1024x768, the edges of the Access Name interface in the InTouch WindowMaker were cutting off. |
IMS-2447657 |
960288375 |
When logging in or out of an IDE application with authentication set to ArchestrA OS user-based or OS group-based, no audit trail was sent to the runtime database for historical block alarms in Alarm Client Control. |
IMS-2452489 |
960285842 |
An unhandled exception was raised in Batch build, when changing content of the frame window with ActiveX control. |
IMS-2455974 |
960286278 |
On a German Operating System, when the user installed an English version of SP 2020 R2 SP1, the InTouch HMI still displayed in German. |
IMS-2463037 |
960294093 |
In System Platform 2023, the System font option was not available in the font selection dropdown for the Text object on a window in InTouch WindowMaker. |
IMS-2463107 |
960294095 |
In InTouch HMI 2023 WindowMaker, the animation color chooser icon appeared stretched and distorted. |
IMS-2467728 |
960282310 |
In Map App widget:
|
IMS-2472697 |
960294727 |
In System Platform 2020 R2 and System Platform 2023, when large values were present in the property HistTrend.ChartStart, WindowViewer stopped responding. |
IMS-2475960 |
960295993 |
In Industrial Graphic toolbox, if the window contained an SFC, an unhandled exception was displayed when the content of the frame was changed or the frame was closed. |
IMS-2477681 |
960297342 |
In InTouch WindowMaker, when tried to open a window property and moved the cursor from left to right, and if the cursor crossed the open InTouch window, the property dialog got switched to the properties of the selected element. |
IMS-2483824 |
960298637 |
In Japanese System Platform 2020R2 SP1 P01, the action script "WWControl(InfoAppTitle("View"),"Maximize");" did not maximize the application. |
IMS-2486320 |
960299248 |
In InTouch WindowMaker, when entered a carriage return character in Quick Function Name field, an error saying "Invalid character in script name" appeared. |
IMS-2486803 |
960298629 |
When tried to print the Data Change Script to text file, garbage characters appeared in saved file. |
IMS-2488560 |
960290985 |
In InTouch HMI application, importing System.Windows.Forms.dll failed and related scripts were not working as expected. |
IMS-2493344 |
960300349 |
In the Industrial Graphic of System Platform 2023, adding a new choice was getting overwritten by the default choice. |
IMS-2496286 IMS-2503436 |
960301781 |
In InTouch HMI 2023 English and Japanese versions, when the characters - and _ were entered in the Access name field, an error occurred. |
IMS-2506113 |
960304595 |
Post-upgrade from System Platform 2020 to System Platform 2023 P01, many place holder tags were visible in Tagname Dictionary. |
IMS-2506122 |
960304598 |
After creating a Template Window in InTouch WindowMaker and restarting it, every time the WindowMaker was opened a warning window with message "cannot open file win00000.win" was displayed. However, no warnings or error messages were shown in the logger. |
IMS-2508062 |
960295674 |
In Windows 2022, could not access the root folder (C drive) while importing and exporting tag information using DBDump and DBLoad utilities. |
IMS-2508960 |
960305456 |
InTouch HMI 2023 and and InTouch HMI 2023 P01 allow user to create more than 64 members of supertag, However, when tried to perform dbdump and then dbload, an error saying "64-member supertag limit exceeded, please cancel or create a new supertag" appeared. |
IMS-2512098 |
960305837 |
Alarm Pareto ActiveX control lost the configuration after closing and reopening the window in InTouch HMI WindowMaker. This problem occurred only if Query Filter was defined. |
IMS-2512457 |
960301781 |
In a Japanese Windows 10 Operating System, even though the Windows language setting was English, the graphic user interface of InTouch WindowMaker was in Japanese. |
IMS-2513405 |
960305130 |
Post-upgrade from earlier versions of InTouch HMI to InTouch 2020 and InTouch 2020 P01, the user could not delete unused tags using Delete Unused Tags or Update Use Counts options. |
IMS-2514233 |
960306058 |
In InTouch WindowMaker, when an embedded graphic was selected and then script was opened from the script list by using the keyboard, then Custom property menu and script opened at the same time on the same command. |
IMS-2524526 |
960306742 |
In System Platform 2023 P02 English and Japanese versions, during runtime, View app did not accept the minimum value (example: 0.1) of an attribute. |
IMS-2528434 |
960294727 |
After applying the hotfix, current time was showing incorrectly in Historical Trend Setup dialog. |
IMS-2531700 |
960308883 |
In System Platform 2023 P01 and System Platform P02, tagname section was getting empty after saving data change script with galaxy object. |
IMS-2532339 |
960296426 |
Post-upgrade from System Platform 2020 R2 SP1 to System Platform 2023 P01, after opening an InTouch HMI application, the InTouch WindowViewer started popping up error messages. Clicking Yes on each error message eventually closed the WindowViewer without a warning. |
IMS-2537368 |
960311208 |
After opening the ViewApp in IDE and moving any docked tool window, if the WindowMaker was closed and reopened, the WindowMaker did not respond. |
IMS-2543691 |
960313644 |
InTouch HMI application stopped responding after deleting specific registry keys and when WindowViewer was set to Run as Service. |
IMS-2549871 |
960312963 |
In Alarm Client Control, when the Security was set as Galaxy, the default alarm comment was not working for Signed Ack. |
IMS-2559603 |
960317501 |
Post-upgrade from InTouch HMI 2020 R2 SP1 to InTouch HMI 2023 P02, an unhandled exception was displayed while deleting data change scripts. |
IMS-2568806 |
960318718 |
Alarm query was not working when LIKE operator was used. |
IMS-2569696 |
960320062 |
In the WindowMaker of InTouch HMI 2023 P02, when a Print icon was added to the Quick Access Toolbar, the hotkey assigned to it did not work. |
IMS-2570205 |
960314320 |
In InTouch HMI 2023 P01, when the Data Change Script in text file was printed, gibberish characters had been introduced in the saved file. |
IMS-2573866 |
960319739 |
When a closed window was opened or when clicked on an opened window, the windows view panel expanded automatically. |
IMS-2575882 |
960321087 |
Could not drag the scroll bar in the Recipe Manager Utility. |
IMS-2579328 |
960320638 |
When the WindowMaker was closed while any of the views like windows, script, supertags, tools, and so on were floating, the WindowMaker did not open and was not responding. |
IMS-2581088 |
960321913 |
In InTouch HMI 2023 P02, the List View button of in Tagname Dictionary window did not work. |
IMS-2584004 |
960318205 |
Even after applying the Hot Fix 2563418, the user input animation did not work with resizable keyboard configured. |
Resolved Issues for Web Client
Defect ID |
SR/Case Number |
Description |
IMS-2429174 |
960282310 |
In Map App widget:
|
IMS-2446396 |
960290179 |
Occasionally, the InTouch Web Client displayed an error message - Sorry, but this application is currently unavailable. Please try again later. If this issue persists, please contact your system administrator. |
IMS-2511432 |
960271578 |
When the InTouch HMI application with custom DLLs were used, a warning message appeared and the user could not work in Web Client. |
IMS-2538930 |
960267753 |
On a German Operating System, the objects and its references were not initialized correctly. |
IMS-2546782 |
960267753 |
In German version of InTouch HMI 2023 P01, after applying the Hot Fix 2410425, the application did not work properly in InTouch Web Client. |
Resolved Issues for PAOEM
Defect ID |
SR/Case Number |
Description |
IMS-2358214 |
960270903 |
Occasionally, IDE was not responding and no error message was logged in OCMC. |
IMS-2477842 |
960297344 |
In InTouch HMI 2023, the deleted Symbol Wizard Option was still visible when symbol was embedded in another symbol. |
This section describes known issues that remain in the release of InTouch HMI 2023 P02, in addition to those mentioned in the Known Issues section of the underlying InTouch HMI 2023 and InTouch HMI 2023 P01 Readmes.
Issue ID |
SR/Case Number |
Description |
IMS-2406541 |
960279683 |
The NavigationTree widget does not support an Alarm adorner. |
Last revision: 6/15/2023
This Readme provides information about AVEVA InTouch HMI 2023 Patch 02. Readme files from previous releases of AVEVA InTouch HMI are posted on the support site.
InTouch 2023 P02 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.
Defect ID |
SR/Case Number |
Description |
IMS-2101507 |
960157367 |
In an InTouch HMI-managed application, Alarm acknowledgement did not work occasionally and showed the error message "User name\<DomainName> not found". |
IMS-2174720 |
960233973 |
On System Platform 2020 R2 SP1, in the WindowViewer of the InTouch Access Anywhere, resolution configuration for Fit to Screen and Fit to Browser did not work. |
IMS-2187651 |
960239102 |
In InTouch HMI 2020R2 P01, in Frame Window mode, Key script was not executed when focus was set on window. |
IMS-2192698 |
960237304 |
In OPC UA Client, after exiting view.exe, the tag value displayed as Zero, and the zero tag value showed the status as Good Quality. |
IMS-2200886 |
960241586 |
If a prompt to restart was enabled when a change was detected for the NAD clients, during the restart of the WindowViewer, when clicked "Yes" on the prompt, an error was displayed. |
IMS-2202474 |
960242441 |
In InTouch HMI 2020 R2 SP1, after applying the hotfix 1891563, the action script "WWControl (InfoAppTitle("View"),"Minimize")" did not work. |
IMS-2219326 |
960215691 |
In System Platform 2020 R2 P01, secured write window was not working properly, it randomly displayed the message "Unable to retrieve Reason description". |
IMS-2219954 |
960234620 |
When the length of the alarm name was greater than 64 bytes, the alarm was not acknowledged. |
IMS-2262172 |
960242024 |
In a German installation of InTouch HMI 2020R2 SP1 P01, when tried to print an HTML file, the object type was garbled. |
IMS-2272643 |
960247100 |
In a German installation of InTouch HMI 2020R2 SP1 on a German Operating System, the alarm state in Alarm Client Control was not shown in run time. |
IMS-2310887 |
960254250 |
In an English installation of System Platform on an English Operating System, if the Region and System Locale was set to German (Germany), state messages from the A2ALMDB did not work for historical alarms in the Alarm Client Control. |
IMS-2311510 |
960258609 |
While using InTouch HMI on a touchscreen device, with Operating System-Based Security configured in WindowMaker, upon expiration of the password, the New Password dialog did not display the on-screen keypad. |
IMS-2325190 |
960262588 |
Post-upgrade from System Platform 2012 R2 to System Platform 2020 R2 SP1 P01, the WindowMaker stopped working. |
IMS-2331151 IMS-2321560 |
960262172 |
In English and Japanese installation of InTouch HMI, when a QuickFunction was created with the same name as an existing one, the warning message displayed incorrect punctuation mark. |
IMS-2333324 |
960237027 |
On a touch panel device, when multi-touch operations were performed in WindowViewer, a Microsoft .NET Framework error occurred. |
IMS-2334839 |
960262913 |
Post-upgrade from System Platform 2017 to System Platform 2023, a placeholder tag was displayed and on clicking on that tag the WindowMaker stopped working. |
IMS-2339391 |
960266576 |
Post-upgrade from System Platform 2014 to System Platform 2020 R2 SP1, in the standalone InTouch application, cross-reference did not display remote reference properly. |
IMS-2347664 |
960266633 |
In InTouch HMI 2020R2 SP1, when Substitute Strings was performed for some screens in WindowMaker, an error message displayed "no strings to substitute" |
IMS-2349334 |
960267719 |
All configuration to the Home Window was lost after any changes were made to configuration of WindowViewer. |
IMS-2359141 |
960271530 |
The Application Manager showed incorrect wwHeap start location. |
IMS-2362297 |
960269448 |
After applying the hotfix IMS-1837216 on the System Platform 2020 R2, when tried to restore the archived file that was purged from A2ALMDB, the restore failed with transaction rolled back. |
IMS-2365793 |
960268024 |
On Windows 11 Operating System, when clicked on Edit bitmap option an error occurred - "Windows cannot find 'C:\Windows\system32\mspaint.exe." |
IMS-2365798 |
960262517 |
In System Platform 2020 R2 SP1, the script GetXmlCurrentAlarms2 of WNWRAPCONSUMERLib.wwAlarmConsumerClass type from dll "wwwrapconsumer" did not return Chinese characters in alarm messages. Instead, empty strings were returned. |
IMS-2366508 |
960262273 |
In Alarm Client Control, event queries containing LIKE operator with cyrillic strings were not working when the unicode characters were not explicitly specified. |
IMS-2371718 |
960273565 |
In Standalone InTouch HMI 2023 , saving windows in WindowMaker did not update the WindowViewer automatically. |
IMS-2383912 |
960276597 |
Post-upgrade from SP 2020 R2 SP1 to SP 2023, the migrated scripts were shown as windows. |
IMS-2398894 |
960276631 |
In InTouch HMI 2023, when the characters - and _ were entered in the Access name field, an error occurred. |
IMS-2331459 IMS-2317450 |
960261330 |
The system allowed creating multiple data change scripts for the same tag. The tagname list displayed duplicate tag names of the same tag. |
IMS-2348913 IMS-2154131 |
960229944 |
In InTouch managed application, the Cross Reference utility was not working properly for Industrial Graphics with InTouch tag reference. |
IMS-2375803 IMS-2402179 |
960275068 |
Post-upgrade from System Platform 2014 R2 SP1 to System Platform 2023, customized folders created in InTouch project view was missing. |
IMS-2356439 |
960270865 |
Performing a DBload with the UPDATE option in command line of the file resulted in data being changed in tag fields that are not specified in update file. |
IMS-2406601 |
960268645 |
After performing Update Use Counts, the WindowMaker and WindowViewer stopped working. |
IMS-2432439 |
960285977 |
In standalone InTouch HMI 2023 application, when tried to edit any condition script, the WindowMaker got closed. |
IMS-2433137 |
960286115 |
The column header "LocalTag" for I/O tags, indirect tags, and HistTrend tags was missing in DBDump file, but the value was present. |
IMS-2441269 |
960287310 |
In InTouch HMI, on opening the Tagname Dictionary after configuring the security, the WindowMaker stopped working. |
IMS-2445593 |
960286278 |
On a German Operating System, when the user installed an English version of SP 2020 R2 SP1, the InTouch HMI still displayed in German. |
Resolved Issues for Web Client
Defect ID |
SR/Case Number |
Description |
IMS-2319495 |
960257441 |
On System Platform 2023, in InTouch WebClient, when loaded the windows in shared Iframe HTML page and when the "show header" option was unselected, the HTML page showed the application home page. |
IMS-2351349 |
960267722 |
In a Germain installation of InTouch Web Client, the value display and keypad in the User Input Animation screen was not localized and the decimal separator "," appeared as ".". |
IMS-2351356 |
960267753 |
In a German installation of InTouch HMI 2023, some values of DataStatus icon were not displayed in the WebClient. |
IMS-2351366 |
960267728 |
In a German installation of InTouch WebClient, for Alarm Client Control, the date format in Alarm Client Control was not localized and displayed in English. |
IMS-2371346 |
960274071 |
When the alarm states of two alarms displayed in a Frame window changed to normal, one of the alarms was not updated and did not reflect the changes. |
IMS-2383810 |
960273988 |
In InTouch WebClient, if the WindowViewer was restarted, the open browser sessions were not reconnecting to it. |
Resolved Issues for PAOEM
Defect ID |
SR/Case Number |
Description |
IMS-2302116 |
960253537 |
In System Platform 2023, when the graphics overlapped, the symbol did not get the tooltip action. |
IMS-2372399 |
960267195 |
When the Custom Property Minimum Value and Maximum Value was provided, Minimum and Maximum fields both showed the current value of the pen itself instead of showing the actual value. |
IMS-2370016 |
960266612 |
After upgrading to System Platform 2023, when the Access Name field was set to only active items, and when the window was closed and reopened, only a few values were displayed. |
IMS-2354335 |
960261588 |
In the managed InTouch HMI application, a button configured with action script or touch animation did not get highlighted, when it was covered by an image which was embedded in a graphic. |
IMS-2352539 |
960265138 |
Post-upgrade from System Platform 2017 U2 to System Platform 2023, in runtime, when a popup window was closed and reopened, some data disappeared and buttons on the popup were not working. |
IMS-2404039 |
960276339 |
In InTouch HMI, while having the Access Name as On demand and when tried to switch screen, there was a delay in updating the animations and current status. |
IMS-2404040 |
960273500 |
When tried to switch screens, the values were not updated in the animation. However after reinitializing the access names manually, the values were updated correctly. |
This section describes known issues that remain in the release of InTouch HMI 2023 P02, in addition to those mentioned in the Known Issues section of the underlying InTouch HMI 2023 and InTouch HMI 2023 P01 Readmes.
Issue ID |
SR/Case Number |
Description |
IMS-2406541 |
960279683 |
The NavigationTree widget does not support an Alarm adorner. |
This section lists important InTouch HMI documentation corrections.
Location of Change |
Existing Documentation |
Change |
|
Notes Regarding Hot Backup Pairs
|
Notes Regarding Hot Backup Pairs The Hotbackup Utility allows multiple hotbackup pairs with the exact same node names. This is only allowed for provider types Galaxy and Galaxy_<name>. For example it is now legal to add these two pairs in the utility:
|
Last revision: 4/15/2023
This Readme provides information about AVEVA InTouch HMI 2023 Patch 01. Readme files from previous releases of AVEVA InTouch HMI are posted on the support site.
With this release, Industrial Graphic Editor supports import of Scalable Vector Graphics (SVG) as Industrial Graphics. You can import an SVG into the Graphic Editor and the graphic elements automatically get converted to an Industrial Graphic, which can include many primitives. A list of supported SVG elements can be found at SVG Github.
To import an SVG and insert as an Industrial Graphic:
Note: You can import multiple SVG files at once.
OR
You can drag and drop multiple SVG files at once.
CAUTION: You can drag and drop SVG files only if User Account Control (UAC) is turned off. Before turning off UAC, be sure to check your organization's security policy, as turning it off could cause a security issue. If you try to drag and drop an SVG file to the canvas with UAC turned on, a forbidden icon is displayed.
Note:
- If there are any unsupported characters in the name of the SVG or primitive, it will be converted to “_”.
- The SVG element name is used to name the corresponding primitive. If a SVG element does not have a name, then Industrial Graphic primitive type is used to name the primitive. For example, if the SVG group name is "Header", the primitive name in Graphic Editor after import will also be Header. If the SVG group has no name, the same will be named as <primitive type>_<number>, that is group_01.
- Only three colors are supported in gradients. If the SVG file has more than three colors for primitive, the first, last, and middle colors are considered. The middle color is calculated by the formula middle color = (int)((colors.Length) / 2). That is, if there are four colors, then it will consider the second color as middle color.
Limitations of SVG Support at the time of this release
The following features are not supported at the time of this release:
InTouch 2023 P01 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.
Defect ID |
SR/Case Number |
Description |
IMS-1422203 |
960095245 |
An InTouch window did not display automatically on the second monitor after unplugging and replugging the cable of the second monitor. |
IMS-1427006 |
960083080 |
Post-migration to System Platform 2020, 2020 R2, or 2020 R2 SP1, the queries were not working properly. |
IMS-1437426 |
960100610 |
When the InTouch application was converted to a different resolution, the location settings of the pop-up window were automatically modified. |
IMS-1441162 |
960102205 |
In a Chinese installation of System Platform 2017 U3 SP1 P01, input characters were not displayed correctly on a HistClientTrend control. |
IMS-1441744 |
960101893 |
Post-upgrade from InTouch HMI 2017 U3 SP1 to InTouch HMI 2020 R2, a black vertical bar appeared at the right edge of the historical trend, which blocked the data from being displayed. |
IMS-1441780 |
960102148 |
In the Script Editor, the validation failed to highlight or indicate the errors in the scripts. |
IMS-1466308 |
960101784 |
Some users noticed performance issues during language switching when Network Application Development (NAD) was enabled in the Client Node. |
IMS-1470558 |
960104174 |
In a Chinese installation of InTouch HMI, the dialog boxes for Historical Logging Properties and Enable Storage to Historian did not contain the options "Log Alarms and Events" and "Alarm Query". |
IMS-1485624 |
960105280 |
When the DataChange script was set to print InTouch Window automatically, sometimes an error "Cannot write to printer" was displayed and on clicking OK, the WindowViewer got closed. |
IMS-1488665 |
960104974 |
Performance issues were observed post-upgrade to InTouch HMI 2020 R2. |
IMS-1489511 |
960106080 |
In WindowMaker, when the 'Resizeable keyboard' option was selected and the 'DialogStringEntry()' function was executed in the WindowViewer, a virtual keyboard was displayed, but the characters typed were hidden with dots and the actual characters typed were visible. |
IMS-1490869 |
960095262 |
Post-migration to InTouch HMI 2020 R2, some users received errors when converting Smart Symbols to Industrial Graphics. |
IMS-1501344 |
960105683 |
Post-migration to InTouch HMI 2014 R2 and then to InTouch HMI 2020 R2 P01, when using the InTouch HMI application as an OPC UA server, only the system tags and not the application tags were displayed. |
IMS-1513543 |
960111494 |
Users on InTouch HMI versions 2017 and higher noticed that modifying the label Panel Meter graphic did not get updated in WindowMaker or WindowViewer. |
IMS-1513735 |
960111953 |
When a non-administrator user closed the WindowViewer in the RDP session, an error was logged in Event Viewer. |
IMS-1530179 |
960112125 |
The InTouch HMI application stopped responding while viewing or switching languages of an Alarm Client Control loaded with a large number of alarms |
IMS-1574747 |
960112436 |
In the InTouch HMI Script Editor, when the character (") was typed, the Window Maker stopped working. |
IMS-1635437 |
960130330 |
Post-migration of a galaxy from System Platform 2014 R2 to System Platform 2020 R2 SP1, when the user tried to log on into InTouch application runtime with an incorrect password, the WindowMaker and WindowViewer stopped responding. |
IMS-1811448 |
960163277 |
In the Alarm Client Control, a query containing a LIKE operator with a historical block failed to execute. |
IMS-1829937 |
960166220 |
In the Historical alarm mode of Alarm Client Control, TimeLCTOAT showed TimeLCT value instead of TimeOAT for Ack alarms. |
IMS-1837216 |
960167721 |
Post-upgrade from InTouch HMI 2014 R2 SP1 to InTouch HMI 2020 R2, the restore of Alarm DB archive files failed. |
IMS-1839032 |
960154960 |
When a Vertical animation was applied to a graphic within a group, the anchor point was modified. |
IMS-1841302 |
960169699 |
When the user fast switched to WindowViewer with cahce settings disabled, language switch did not work as expected. |
IMS-1844310 |
960170260 |
When a thin client device containing a smart card was rebooted, the WindowViewer stopped responding. |
IMS-1850602 |
960161774 |
In a standalone InTouch HMI application, when a DBLoad failed, the error message showed "0.000000s" instead of the reason of the failure. |
IMS-1859516 |
960173337 |
Button with action script worked properly, but did not look depressed when pressed down. |
IMS-1864732 |
960174132 |
In InTouch HMI 2020 R2, the text in the Industrial Graphics displayed in bold at runtime, but the text was not bold in edit mode. |
IMS-1874376 |
960152717 |
In an InTouch HMI-managed application, when embedding a graphic into another graphic, warning messages were logged in the SMC. |
IMS-1876906 IMS-2051501 |
960161046 |
Upon applying the HotFix 1794095, and changing AccessName and Item name using the IOSetItem function through script, the secondary source for this Item did not work. |
IMS-1877421 |
960155771 |
When the Window Lock count value reached the maximum value of 255, the WindowViewer stopped responding. |
IMS-1879263 |
960163861 |
A pop-up window failed to appear when called from another window configured with TopMost mode. |
IMS-1882063 |
960165528 |
In a German installation of InTouch HMI, the dialog boxes for Historical Logging Properties and Enable Storage to Historian did not contain the options "Log Alarms and Events" and "Alarm Query". |
IMS-1890131 |
960161750 |
In InTouch HMI 2020 R2 P01, the pop-up windows were cut off on the right and bottom on a migrated app. |
IMS-1891563 |
960175987 |
In InTouch HMI 2020 R2 SP1, Polish characters were not displayed properly at runtime. |
IMS-1897151 |
960097549 |
Post upgrade to InTouch HMI 2020 R2, when a choice of Symbol Wizard embedded to the object was not used, the system gave an object-level warning message - Could not resolve reference: <Reference> |
IMS-1898475 |
960181136 |
Performance issues were observed when NAD was activated and switched to the Slovakian language. |
IMS-1899107 |
960181400 |
When an InTouch HMI application was deployed to runtime and upon language switching, language change anomalies were observed in the top bar and in the pop-up menu at the bottom. |
IMS-1899188 |
960182742 |
In a standalone InTouch HMI application, the changes to the graphic smoothing properties were not getting saved. |
IMS-1908157 |
960182399 |
The Visibility animation disappeared during the conversion of InTouch window symbols to Industrial Graphics. |
IMS-1909748 |
960174140 |
SQL Data Grid was not able to perform write if column names have a space in the name. |
IMS-1934826 |
960190505 |
When a button was configured with a String Type User Input animation, no characters were displayed on the button in Runtime. |
IMS-1938407 |
960173877 |
In the Alarm Purge/Archive Utility, when the Mapped Network Drive Path was used to archive files and run as a service, the path was not validated. |
IMS-1948798 |
960161899 |
When the InTouch HMI application was launched, WindowMaker did not release memory and the entire application stopped responding. |
IMS-1968828 IMS-1987065 |
960171848 |
When trying to delete an open window, the ‘Cross Reference’ results displayed incorrect information. When an InTouch HMI application was exported and then imported again, the Delete Unused Tags count varied. |
IMS-1984111 |
960193761 |
Alarms in Alarm Client Control could not sort for the Value field. |
IMS-1986522 |
960199402 |
In read-only InTouch HMI application, encrypted communication caused high CPU utilization and logged repeated messages. |
IMS-1989232 |
960200052 |
When an application was viewed in WindowViewer from the Application Manager, and languages switched, a change in font style was observed for a few text box elements. |
IMS-2002264 |
960202862 |
On Windows Server 2019 DataCenter operating system with InTouch HMI 2020 R2 SP1, when the server was shut down without closing the WindowMaker development process and opened WindowMaker again after the restart, all the Symbols in Library were missing. |
IMS-2003842 |
960197785 |
On InTouch 2020 R2, when tried to run a Cross Reference or Update Use Counts, the application stopped working. |
IMS-2008057 |
960193740 |
The AlarmApp in OMI application was not working properly when tried to display Historical Alarms and Events using the Like/NotLike filter query. |
IMS-2028402 |
960208100 |
When the WindowMaker was launched from the IDE for an InTouch HMI managed application, the MSI Installer triggered a repair of the InTouch HMI. |
IMS-2029977 |
960202862 |
The OMI application was not responding when fetching and displaying the Alarms. |
IMS-2038269 |
960209026 |
In the German installation of InTouch HMI, there was an issue when the Alarm printer was run first and then tried to configure it. |
IMS-2040049 |
960191487 |
The Alarm Client Control did not display real-time alarms, and an error message was displayed: WNALregister AlarmMgr not running was displayed. |
IMS-2044085 |
960209847 |
Post-upgrade from System Platform 2014 R2 SP1 to System Platform 2020 R2, Alarm Client Control showed Timestamps of TimeOAT as 01-01-0001 00:00:00 at runtime. |
IMS-2048357 |
960205592 |
There was inconsistency in exporting locale data once the Windows have been converted to Industrial Graphics. |
IMS-2051413 |
960199338 |
AppEngine Memory consumption increased after two months of running. |
IMS-2065049 IMS-2131559 |
960200052 960223807 |
When an application was viewed in WindowViewer from the Application Manager, and languages switched, a change in font style was observed for a few text box elements. |
IMS-2071352 |
960212605 |
In InTouch HMI 2020 R2 SP1 Standalone application configured as NAD, on a client node, when the pens in trend configuration is modified, then exited and reopened the WindowViewer twice, the Trend configuration changed completely. |
IMS-2084995 |
960211602 |
In System Platform 2023, the DataGrid widget was not able to retrieve data from a CSV source data string, if it contained diacritical mark (hacek) such as ě š č ř ž ň ť. |
IMS-2105456 |
960211641 |
In Alarm Client Control, when configured the Historian alarm with Maximum Records as zero, showed duplicate rows every time a filter is added. |
IMS-2124385 |
960218654 |
A DBDump operation of an application containing IO Real tags with minimum and maximum values in decimals did not show the decimal values exactly as they were in the Tagname Dictionary. |
IMS-2130974 |
960209847 |
In an Alarm Client Control, the TimeOAT and UTC time columns of Historical Alarm and Events displayed incorrect values at runtime. |
IMS-2132552 |
960164448 |
InTouch OMI, the Alarm Application was not filtering the Alarm_DurationMS column as expected for Historical Alarms. |
IMS-2133787 |
960224006 |
InTouch HMI 2020 R2 SP1 could not read Script Function Library file properly. |
IMS-2134491 |
960227405 |
When multiple scripts were opened by right-clicking on windows and selecting Window Scripts, WindowMaker stopped responding. |
IMS-2136522 |
960227801 |
Upon upgrading InTouchViewApp from System Platform 2014 R3 SP1 to System Platform 2023, all QuickFunction Scripts were listed under the Application script folder and could not be edited.
|
IMS-2136630 |
960227631 |
During an import of Galaxy Style library, an error was displayed - "Imported Theme file is not a valid Theme". |
IMS-2137801 |
960223143 |
The changes to managed InTouch application took a long time to save. |
IMS2139500 |
960229042 |
The save function from reporting panel did not work in Web Browser widget and only displayed blank window. |
IMS-2139638 |
960228620 |
InTouch HMI 2023 was unable to get any alarms out of Historian with Alarm Client Control. |
IMS-2142309 |
960227083 |
In InTouch HMI 2023, the native window did not zoom when using Ctrl + Mouse Wheel. |
IMS-2145063 |
960227839 |
Upon upgrading the galaxy from System Platform 2014 R2 SP1 P02 to System Platform 2020 R2 SP1, the callup time is significantly slower when showing symbols. |
IMS-2146427 |
960213215 |
In WindowMaker, the Window Report Japanese translation string was incorrect with loss of some characters. |
IMS-2156288 |
960227114 |
In WindowMaker or WindowViewer of an InTouch application, upon clicking the Help in the About box, the WindowMaker stopped working. |
IMS-2157490 |
960221745 |
In WindowMaker of an InTouch standalone application, could not change the color of a line to black or fill a shape with black color, if initially the default color is other than black. |
IMS-2157979 |
960231180 |
In InTouch HMI 2023, a Chinese word translation was incorrect. |
IMS-2158879 |
960226946 |
When an Alarm Client Control was opened the first time after launching WindowViewer, if the current language was Chinese (Simplified), then each Chinese character in the alarm translation was shown as a single question mark. |
IMS-2173252 |
960235701 |
WindowMaker stopped responding when the canvas was moved. |
IMS-2174147 |
960235608 |
When the security was set to OS-based authentication and the user logged in as an Administrator in WorkGroup Mode, an error message "DsGetDcName() failed to get domain controller name with error code 1355" was displayed in the OCMC. |
IMS-2175049 |
960234190 |
After loading a DBload db.csv file into any InTouch application, and tried to load the updated DB.csv file again to the same application, the DBLoad did not respond. |
IMS-2178572 |
960228563 |
In System Platform 2023, if a web widget was imported into the galaxy it appeared without any property. |
IMS-2179073 IMS-2135974 |
960237791 960225808 |
In the Alarm Client Control, custom colours could not be saved and reused using the Define custom colors feature. |
IMS-2189683 |
960239438 |
The Highlight animation in the navigation canvas did not work as expected. |
IMS-2198968 |
960239431 |
While view.exe was running, double-clicking the navigation button displayed an exception popup. |
IMS-2200640 |
960241533 |
In the Cross Reference tool of the Japanese installation of InTouch HMI 2020, the tag used in the condition script was displayed as 'Use In' Application script instead of Condition script. |
IMS-2211264 |
960236587 |
In the Symbol Editor, when the Graphic canvas was selected, keyboard shortcuts did not work. |
IMS-2250199 |
960247045 |
When the Industrial Graphic was opened using Show symbol animation or ShowGraphic, the User input animation for passwords did not mask the entered password letters. |
IMS-2266176 |
960248911 |
In InTouch HMI, the DataChange Script with "dot" character was not shown correctly. |
IMS-2275102 |
960249187 |
Post-upgrade of an InTouch HMI application from InTouch HMI 17.2 with export aaPKG from modern application to InTouch HMI 2023 with import aaPKG as standalone with industrial graphic, Window Maker generated an exception message and stopped responding. |
IMS-2276599 |
960245036 |
The Window Maker stopped responding when tried to print an application with A2 graphic. |
IMS-2276803 |
960243637 |
In InTouch HMI standalone application, when the Industrial Symbol Library was opened, all Industrial Symbols disappeared from the Symbol Toolbox and Windows. |
IMS-2277145 |
960250411 |
In WindowMaker, when quick functions were called from application script, unique names were displayed. |
IMS-2277373 |
960249202 |
In InTouch HMI, Elapsed Time and Time Custom Properties keypad input did not display the label when tried to input a value on the shown keypad. |
IMS-2281419 |
960251011 |
Post-upgrade from System Platform 2020 R2 to System Platform 2023, occasionally the InTouch application stopped responding when the WindowViewer was launched. |
IMS-2292215 |
960254253 |
In System Platform 2020 R2 SP1, when the operating system-based security authentication type was selected with the option "User must change password next logon", using AttemptInvisibleLogon () function did not display the "Change Password" popup. |
IMS-2293118 |
960252566 |
On a German installation of InTouch HMI application, Post-upgrade of System Platform 2014 R2 SP1 P02 to System Platform 2023, the diacritical characters of the window names did not display properly in the Project Tree view. |
IMS-2307818 |
960258330 |
Slider animations did not work in Phoenix Contact Panel PC with InTouch HMI 2023 on Window 10 LTSC 2019. |
IMS-2311749 |
960256990 |
Post-upgradet to System Platform 2023, the Window Maker stopped working. |
IMS-2318559 |
960260021 |
Post-upgrade from System Platform 2017 U3 SP1 P01 to System Platform 2023, no windows were available in InTouchViewApp. |
Resolved Issues for Web Client
Defect ID |
SR/Case Number |
Description |
IMS-1216684 |
960069135 |
Web Client failed to load for an InTouch window using Content Frame. |
IMS-1432030 |
960098018 |
Upon upgrading System Platform 2014 SP1 to System Platform 2020 R2 P01, about 90% of the graphic symbols were missing in InTouch Web Client. |
IMS-1502997 |
960101905 |
In the Symbol Editor, after resizing an object, the InTouch Web Client interface could no longer load the page with the object. But it worked with WindowViewer. |
IMS-1557166 |
960115378 |
The Web Browser widget failed to connect to Web Client. |
IMS-1589054 |
960120394 |
On a French Operating System, graphics configured with user input animation for date and time did not display the modified entries in Web Client. |
IMS-1846703 |
960171482 |
When viewing graphics in the web browser, the horizontal and vertical scroll bars appeared even though the Show Header check box in the InTouch Web Client settings was not selected. |
IMS-1856156 |
960170149 |
Some fonts on graphic displayed in InTouch Web Client appeared different than when displayed in Window Viewer. The text looked bold and big, as expected, in Window Viewer but appeared small and not bold in Web Client. |
IMS-1858770 |
960162276 |
The InTouch Web Client stopped responding when the direct link to the Symbol : /api/symbol/ was used. |
IMS-1864186 |
960175659 |
The Web Client function embedded in iframe was not working as expected. |
IMS-1900683 |
960182266 |
When the OMI map settings were imported, an error was displayed: "Location Graphic cannot be imported because it contains invalid data". Exporting the OMI map settings worked fine. |
IMS-2100154 |
960220264 |
When the back camera was used, the QRCode_Scanner widget showed a mirror view in the capture area. |
IMS-2134541 |
960223695 |
In InTouch Web Client, objects that are meant to move on the map did not work. When the same screen was opened from the WindowViewer, these objects behaved as expected. |
IMS-2138666 |
960227707 |
Map App coordinates with decimal places were treated as 0° 0° |
IMS-2146450 |
960228465 |
In InTouch Web Client, it took a long time to load the page and open the windows with Trend control that uses LGH files as Historical Sources. |
IMS-2149165 |
960230722 |
The Windows Integrated Login button for AIM authentication was not working as expected. |
IMS-2315362 |
960256482 |
In InTouch 2023, the Show Graphic custom property did not work in Web Client until the Frame window containing the graphic is closed using the Close button in title bar. |
Resolved Documentation Issues
Defect ID |
SR/Case Number |
Description |
IMS-2176522 |
960235911 |
In the Understanding License Tag Counts section of the AVEVA™ InTouch HMI Management Guide, the maximum count of placeholder tags displays 4096. The document has been corrected to reflect that InTouch HMI 2023 and higher supports unlimited database handles to store placeholder tags at configuration time. During run time, all placeholder handles are available to be assigned to remote reference tags. |
This section describes known issues that remain in the release of InTouch HMI 2023 P01, in addition to those mentioned in the Known Issues section of the underlying InTouch HMI 2023 Readme.
Issue ID |
Description |
IMS-2200446 |
The location of the pop-up window is different, and the right and bottom borders of the window appears to be cut-off. Workaround 1: Use compatibility settings for view.exe
|
Last revision: 7/15/2022
This Readme provides information about InTouch HMI 2023 (Version 23.0.000). Readme files from previous releases of InTouch HMI are posted on the Support website.
This release includes all the issues shipped in the InTouch HMI 2020 R2 SP1 release and can be installed directly.
Important!
When installing System Platform 2023, Gateway Communication Driver is installed as a hidden feature of InTouch HMI 2023.
For more information about the Gateway Communication Driver installation, upgrade, and uninstall, see the System Platform Installation Guide, "InTouch HMI Requirements and Prerequisites" section, "Installing OI Gateway and Modifying FS Gateway Installations" topic.
Microsoft Windows Server 2016 Users - Remote Desktop Services and InTouch HMI
When InTouch HMI 2023 is installed on an older Windows 10 or Windows Server 2016 computer that has not been updated and has Remote Desktop Services enabled, WindowViewer may fail to launch. WindowMaker cannot be closed unless shut down using Task Manager.
Workaround:
Important: You can install the Microsoft update before or after System Platform. However, we recommend installing the Microsoft update before you install System Platform.
Secure Suitelink Communication
On a fresh installation of System Platform 2023, you may notice the following issues related to Secure Suitelink Connection:
Workaround:
To ensure connectivity between the Suitelink client and the WindowViewer:
For more information, see Configuring a Secure Suitelink Communication in the AVEVA InTouch HMI Help.
For important information about this product release, go to the AVEVA Global Customer Support (GCS) website. Information on the GCS website includes product requirements and compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.
InTouch HMI 2023 (Version 23.0.000) includes a number of new features, hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products.
New Look of InTouch HMI
InTouch HMI 2023 now has a new look. The product and icons have been redesigned for a simpler and enhanced user experience. The new user interface complies with the fluid design and adheres with the AVEVA Design System. Some of the key highlights of the new InTouch HMI 2023 user interface are:
Longer tag names and item names
The tagname length has been extended from 32 to 128 characters. Item name length has been extended from 79 to 254 characters.
Unlimited Tag Count Support
The InTouch license now supports unlimited tag count. This means that the run-time database can theoretically store unlimited tagcount license, which includes both local tags and tags that reference a remote tag source. However, we have tested up to 300,000 tag handles (300K) only. For more information, see the section Licensing in InTouch HMI in the InTouch HMI Help.
Cloud Graphic Versioning Support
The AVEVA Drive graphics supports Industrial Graphics, Client Controls, and Widgets in the Cloud, published from different products with different versions of the graphic subsystems. For more information, see the section Working with Industrial Graphics in AVEVA Connect in the InTouch HMI Help.
Map App Web Widget
You can use the Map App Web Widget to incorporate a zoomable map into InTouch HMI applications and display selected graphics in a geographical context. It supports a number of popular map providers, and is perfect for geographically distributed applications. You can integrate Supertags with MapApp widget to display it in WindowViewer or Web Client. For more information, see the section Using MapApp Widget with Supertags in the InTouch HMI Help.
Supertags
Supertags is now more easily accessible from the Windows panel. It also has an improved workflow, making it easier to manage members, instances, and attributes.
Improved Search in WindowMaker
The improved search functionality in WindowMaker allows you to search with a keyword simultaneously within the windows, scripts, tags, and symbols.
Bit State Animations
Bit State animations allow you to add conditions to an animation based on bit values. You can add multiple conditions and for each condition you can select individual bits in any pattern up to 32 bits.
Extended Truth Table Animations
The Blink, Disable, Value Display and Visibility animations have now been extended with the ability to configure animations with truth table conditions.
New Graphic Element - Multi Pens Trend
Introducing a new graphic element – Multi Pens Trend. A Multi Pens Trend is like a trend pen and displays a succession of process values but with multiple trend lines.
Ramp option with the Pushbutton Animation
Within the Pushbutton animation you can choose to apply a percentage ramp to the Increment, Decrement, Multiply and Divide actions.
Support for Momentary Touch
The Momentary Contact action is now available for the Pushbutton Boolean animation, allowing you to configure a time-period to hold the set value.
Option to Reset Industrial Graphic Option Cached Values
You can now choose to reset the Industrial Graphic cached values and windows properties when the window is closed and reopened.
Improved Association of Tag Reference with Graphic Element text
There is an improved association of the the tag reference with the text displayed for the Graphic Element.
Enhanced Language Switching at Runtime
The InTouch HMI application and the Alarm Client Control supports runtime language switching of alarm group names, and event and status bar messages.
Secure SuiteLink Configuration
As of System Platform 2023, the SuiteLink connection is by default set to secure with TLS encryption. If you want to enable the fallback mode to accept the unsecure connection, you have to make the configuration changes in the System Management Server. You can verify the mode of the SuiteLink connection, whether secure or unsecure, by checking the WWSLS component in the Log Viewer.
If unsecure fall back mode is not enabled and secure connection requirements are not met, then SuiteLink connection will fail. For more information, see Configuring Secure Suitelink as a Standard User in the AVEVA InTouch HMI Help.
Workspace Feature for the AVEVA InTouch HMI Web Client
Use the Workspace feature from the InTouch HMI Web Client for operators to create customizable dashboards dynamically. Workspace displays all graphics available in the Workspaces toolset of Graphic Toolbox in the selected application. This allows viewing an Industrial Graphic with runtime data by binding custom properties to tags from InTouch HMI. You can create, modify, and save your dashboards, and even share them with others on the team.
To access Workspace, you must:
Note:
- The AVEVA Historian search and elastic search features are installed to support the Workspace feature for the InTouch HMI Web Client. Workspace is available if you are using Flex licensing. Therefore, after installation, you may see AVEVA Historian listed as a Windows program, even if you did not install the Historian. Do not uninstall Historian. You can use the Modify workflow to restore the Historian search and elastic search features if you inadvertently uninstalled Historian.
- In this initial release of Workspace, searching for Application Server attributes is not supported when using Workspace on a remote node. Searching for Application Server attributes is only supported on the GR or Galaxy Repository node. This feature will be supported in future releases.
For more information, see Workspace in the AVEVA InTouch HMI Help, ITWebBrowser.pdf, and Widgets, Apps, and Controls Help.
Cybersecurity Enhancement
This version of InTouch HMI incorporates several cybersecurity enhancements.
X-Frame-Options Authentication Settings for Web Client
The Web Client now supports the X-Frame-Options HTTP response header. This can be used to indicate whether or not a browser should be allowed to render a page in a <frame>, <iframe>, <embed> or <object>. An XFrameOptions property has been added to the appsettings.json files under InTouchWeb\Server and InTouchWeb\Content.
The value of XFrameOptions in the appsettings.json file is blank by default. To ensure that the Web Client page can only be displayed in a frame on the same origin as the page itself, you must set the values of XFrameOptions as ‘SAMEORIGIN’. The value is not case sensitive. A shared Web Client may not load if the value of XFrameOptions is set to SAMEORIGIN.
If you specify the value of XFrameOptions as blank, the X-Frame-Options response header will not be added.
This section describes the hardware and software requirements to support System Platform products, including InTouch HMI.
System Sizing Guidelines
The following table provides guidelines for hardware configurations suitable for System Platform 2023 software based on the size of the installation. These guidelines are subject to the limitations of your Windows operating system.
Hardware Requirement |
Small Installation (1 - 25K I/O per Node) |
Medium Installation (25k - 50k I/O per Node) |
Large Installation (More than 50k I/O per Node) |
---|---|---|---|
CPU Cores (Minimum)1 |
Greater than or equal to 2 |
Greater than or equal to 4 |
Greater than or equal to 8 |
RAM1 (GB) |
Greater than or equal to 4 |
Greater than or equal to 8 |
Greater than or equal to 16 |
Storage (GB) 2 |
Greater than or equal to 100 |
Greater than or equal to 500 |
Greater than or equal to 1000 |
Network (Mbps) |
Greater than or equal to 100 |
Greater than or equal to 1000 |
Greater than or equal to 1000 |
Notes:
1 In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.
2 Minimum amount of storage needed to provide sufficient capacity for 1 week @ max frequency.
Hardware Requirements Notes
Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for InTouch HMI 2023. Refer to the following Microsoft Web pages for Windows and SQL Server hardware requirements:
Auxiliary Hardware Requirements
This section describes any optional hardware requirements beyond the specific hardware requirements discussed earlier in this Readme.
Alternative Authentication Using Smart Cards
This section describes additional details about the supporting software for an InTouch HMI system.
Software Requirement Notes
Windows Operating System Notes
Showing the set of charms is a standard feature of Windows versions 8.1 that cannot be disabled by software for a touch screen. As a result, operators can access these Windows charms and possibly unlock a dedicated touch screen view node.
.Net Notes
For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility .
Operating System Notes Common to AVEVA Products
ActiveX Controls Behavior on Supported Windows Operating Systems
Due to the Data Execution Prevention (DEP) feature of Windows 7 and later operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behavior in InTouch 2017 UPDATE 1 either in WindowMaker or WindowViewer. For more information, refer to Tech Note 922: "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)" available from the Technical Support web site.
Configuring Remote Alarm Retrieval Queries
The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on currently-supported Windows and Windows Server operating systems.
When InTouch WindowViewer is started and generates alarms from an interactive Windows desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.
This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.
To configure the AlarmViewer's alarm query
\\nodename:ip_address\intouch!$system
where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.
Using Alarm Manager on a Single Node Running Both InTouch HMI and Application Server Alarm Providers
Starting with Microsoft Windows Vista, the operating system imposes "Session 0 Isolation" as a security enhancement. All Windows services and associated programs are required to run in Session 0, and no GUI applications are allowed to run in Session 0.
Prior to Windows Vista, Application Server and InTouch HMI WindowViewer ran in the same Windows session. Session 0 Isolation requires that Application Server and WindowViewer run in separate Windows sessions. Alarms that are reported by the Galaxy are handled by the Session 0 instance of Alarm Manager (AlarmMgr), which is now different from the Console Session instance of AlarmMgr that handles InTouch alarms. A simple alarm query in an InTouch alarm display such as
\InTouch!$System \Galaxy!Area_001
is now serviced by two separate instances of AlarmMgr -- one running in the Console Session for InTouch, another running in Session 0 for the Galaxy.
This behavior, and related behaviors and error messages resulting from the Windows operating system Session 0 changes, along with procedures to configure the Distributed Alarm System to support alarms from both InTouch and Application Server on the same computer node running with Windows Vista and later operating systems, are described in detail in TechNote 988, "AlarmMgr Support for InTouch and AppServer on Windows Vista and Later". You can download this TechNote from the Global Customer Support (GCS) website.
Remote Desktop Services (Terminal Services) Behavior in Windows Server Operating Systems
Windows Server 2008 R2 and later Windows versions no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server 2008 and later, all remote connections are treated as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the Remote Desktop (Terminal Server Console) session.
In another aspect of Remote Desktop Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value with InTouch running in a remote desktop (RDP) client session. The cause of this behavior is that the relevant roles are not installed on the RDP client. You must install the "Remote Desktop Host" role in order for TSEGetClientId() and other related functions to work properly.
The impact to Application Server is minimal as most Application Server processes run as services. One impact to Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.
Application Server and InTouch HMI detect when the application is running in the console. In Windows Server, it implies that the application was started by a user physically at the machine. However, this behavior may require you to disable the group policy that enables Fast User Switching.
The software detects when an application is running in the console. All remote connections are treated as a remote RDP session by Windows Server, regardless of /console or /admin switches in the mstsc connection.
To disable fast user switching through the Group Policy interface
By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.
InTouch HMI Operating System Notes
You can configure local Windows security policies that work in conjunction with the EnableDisablekeys() script function to regulate the user's access to keys in a running InTouch application.
The following InTouch legacy script functions do not operate on 64-bit versions of Windows: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
InTouch HMI View Applications and DDE Support
NetDDE is not supported for InTouchView applications.
By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. Industrial Graphics make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, Industrial Graphics cannot communicate with InTouch tags when used with an InTouchView license.
In Industrial Graphics, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.
InTouch HMI Support for Windows User Account Control
System Platform 2023 with InTouch HMI supports User Account Control-enabled operations on run-time nodes.
.NET Framework Requirements and Compatibility
IMPORTANT: System Platform 2023 installs .NET 4.8 if the currently installed version of .NET is 4.7.2 or lower. If .NET 4.8 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to System Platform 2023, we strongly recommended that you:
After upgrading to System Platform 2023, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.8. We also recommend you test the upgrade in a staging system prior to upgrading your production system.
System Platform 2023 leverages Microsoft .NET Framework 4. The System Platform installation program will install .NET 4.8 if your system uses version 4.7.2 or lower. No change is made if your system uses .NET 4.8 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. System Platform 2023 will use .NET 4.7.1, 4.7.2, or later.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.8 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.
In application scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an application script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:
What's New in the .NET Framework: http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx
What's obsolete in the .NET Framework Class Library: https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx
Migration Guide to the .NET Framework 4.6 and 4.5: https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29
.NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29
Virtualization Host Support
See the Global Customer Support (GCS) Technology Matrix for supported virtualization environments.
SQL Server Requirements for All Components
See the GCS Technology Matrix for SQL Server requirements for System Platform 2023 components, including InTouch HMI 2023.
Note: Match SQL Server version to operating system version.
We recommend that you install and configure the supported SQL Server version before you begin the System Platform installation program, especially if you expect Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.
The System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, and then resume the installation.
Considerations for SQL Server
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Application Server User's Guide, About ArchestrA User Accounts, for further information and procedures to restore the aaAdministrators group.
Considerations for SQL Server Express
To work around this issue, configure Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.
The following sections describe the requirements to run InTouch Access Anywhere Server and supported browsers. For detailed information, see the InTouch Access Anywhere documentation.
You can determine the version of InTouch Access Anywhere Server installed on a computer using Programs and Features from the Windows Control Panel.
Requirements
The InTouch Access Anywhere Server can be installed as a System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional component installed on a separate computer within a network DMZ.
The following requirements must be met before you install the InTouch Access Anywhere Server or a Secure Gateway.
Supported InTouch Access Anywhere Browsers
InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5-compliant web browser. Browsers validated to support InTouch Access Anywhere include the following:
Functionally Compatible Browsers
Older versions of the listed browsers are functionally compatible with InTouch Access Anywhere. You may be able to use the following older versions of these browsers, but specific behaviors are unknown because no formal testing has been done with InTouch Access Anywhere.
You are strongly encouraged to upgrade to one of the supported browser versions listed in Browsers Tested with WindowViewer. For a complete list of considerations to run an InTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide.
Product Compatibility refers to the ability of a product to work with various versions of other products running on different network nodes. Product Compatibility also refers to the ability of a product to work with various versions of the same product running on different nodes.
Coexistence refers to same-node installation of a product with other products that support the same hardware, operating system, and SQL Server versions. Other products not listed will be covered by System Compatibility Testing unless specifically noted.
In a single-node environment, if you want to install multiple components on a single computer, all components must be at the same versions.
In a node-to-node environment, components are compatible between the current licensed version and one licensed version back. Refer to the GCS Technology Matrix for more information.
The following table lists products and their compatibility and coexistence with InTouch HMI 2023.
Product |
Version |
Compatibility |
Co-existence |
System Platform
|
4.5 |
N |
N |
2012 |
Y |
N |
|
2012 R2 |
Y |
N |
|
2012 R2 P01 |
Y |
N |
|
2012 R2 P02 |
Y |
N |
|
2012 R2 P03 |
Y |
N |
|
2014 |
Y |
N |
|
2014 P01 |
Y |
N |
|
2014 R2 |
Y |
N |
|
2014 R2 P01 |
Y |
N |
|
2014 R2 SP1 |
Y |
N |
|
2017 |
Y |
N |
|
2017 Update 1 |
Y |
N |
|
2017 Update 2 |
Y |
N |
|
2017 Update 3 |
Y |
N |
|
2017 Update 3 SP1 |
Y |
N |
|
2017 Update 3 SP1 P01 |
Y |
N |
|
2020 |
Y |
N/A |
|
2020 R2 |
Y |
N/A |
|
2020 R2 P01 |
Y |
N/A |
|
2020 R2 SP1 |
Y |
N/A |
|
InTouch CE |
10.1 |
N |
N |
InControl |
7.11 SP2 P01 |
N |
N |
Batch Management |
2020 |
Y |
Y |
QI Analyst |
8.0 SP4 |
Y |
Y |
SCADAlarm |
6.0 SP2 P01 |
N |
N |
Intelligence |
2014 R3 |
Y |
N |
2017 U1 |
Y |
Y |
|
Workflow Management |
2020 |
Y |
Y |
Mobile Operator Rounds |
5.01 |
Y |
Y |
2014 R2 |
Y |
Y |
|
Insight (see components below) |
1.0 |
|
|
Insight Client (On-Prem) |
17.x (via Historian) |
Y |
N |
Historian Client |
10.x/17.x |
Y |
N |
InTouch |
11.x |
Y |
N |
Recipe Management |
2020 |
Y |
Y |
PlantSCADA |
2016 |
Y |
Y |
2018 |
Y |
Y |
|
2018 R2 |
Y |
Y |
|
ClearSCADA |
CS 2017 R1 |
Y |
Y |
CS 2017 R2 |
Y |
Y |
|
CS 2017 R3 |
Y |
Y |
|
GS 2019 |
Y |
Y |
|
AVEVA System Monitor
|
1.1 |
Y |
Y |
1.2 |
Y |
Y |
|
Sentinel Agent |
1.0 |
N/A |
Y |
Sentinel Server |
1.0 |
N/A |
N |
ASB (now PCS)
|
SP 2012 R2 SP1 |
N |
N |
SP 2014 R2 SP1 P01 |
Y |
Y |
|
SP 2017 |
Y |
Y |
|
SP 2017 U1 |
Y |
Y |
|
SP 2017 U2 |
Y |
Y |
|
PCS and SMS
|
SP 2017 U3 |
Y |
Y |
SP 2017 U3 SP1 |
Y |
Y |
|
SP 2020 |
Y |
Y |
|
System Platform
|
4.5 |
N |
N |
2012 |
Y |
N |
|
2012 R2 |
Y |
N |
|
2012 R2 P01 |
Y |
N |
|
2012 R2 P02 |
Y |
N |
|
2012 R2 P03 |
Y |
N |
|
2014 |
Y |
N |
|
2014 P01 |
Y |
N |
|
2014 R2 |
Y |
N |
|
2014 R2 P01 |
Y |
N |
|
2014 R2 SP1 |
Y |
N |
|
2017 |
Y |
N |
|
2017 Update 1 |
Y |
N |
|
2017 Update 2 |
Y |
N |
|
2017 Update 3 |
Y |
N |
|
2017 Update 3 SP1 |
Y |
N |
|
2017 Update 3 SP1 P01 |
Y |
N |
|
2020 |
Y |
N/A |
|
2020 R2 |
Y |
N/A |
|
2020 R2 P01 |
Y |
N/A |
|
2020 R2 SP1 |
Y |
N/A |
Supported |
Y |
Not Supported |
N |
Not Applicable |
N/A |
In some cases, InTouch HMI is supported in newer environments than a compatible product. InTouch HMI has been tested for compatibility with a listed product only in the environments that are supported by that particular product.
For detailed English installation instructions, see the System Platform Installation Guide (SP_Install_Guide.pdf) or System Platform Installation Help (SP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed InTouch HMI Getting Started Guide booklet that is included in the installation package. This booklet is provided for all supported languages.
The information provided in this Readme file supersedes the InTouch Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.
The major decision you must make when you install InTouch HMI is whether to install the InTouch development and run-time components, or the run-time components alone. The installation program guides you in selecting the features you want, verifying or modifying your selections, installing prerequisite software, and then installing InTouch HMI and the IDE if you chose to install development components.
What You Need to Install InTouch HMI
You must have the following materials ready to install InTouch HMI:
Important: Use the hardware and software requirements listed in the Application Server Readme if you are going to install the IDE.
Prerequisites
The installation program analyzes the software installed on your computer and lists any required software that is not installed.
Note: At the start of the installation, the prerequisites check is system-specific rather than product-specific.
The following prerequisites, if not already present on your system, will be installed by the System Platform installation program:
SQL 2017 Express Core is installed automatically if either of the following conditions are met:
The installation program installs both system-specific and product-specific prerequisites. You do not have to exit from the installation program to install the prerequisite software. For more information about System Platform installation prerequisites, see the System Platform Installation Guide.
About the ArchestrA User Account
The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an Application environment. You must specify the same user account on every node when you install the System Platform components for the first time on computers that communicate with each other.
WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.
If the ArchestrA user account has not previously been configured, you will be prompted to configure it during the InTouch HMI installation. You must specify a user name, password, and domain.
If you choose to use an existing user account, it should meet the following requirements:
After you install the InTouch HMI, you can use the Change Network Account utility to change or recreate the ArchestrA user account. This utility is accessible from the Start menu in the AVEVA Common folder after you install InTouch. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility help.
Note: If you recreate the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.
Performing the InTouch HMI Installation
Before you start installing InTouch HMI, you should have a clear idea whether you want to develop, deploy, and publish your own applications, or require only the InTouch run time, to run applications already created and deployed.
The following procedure will guide you through the installation, with information specific to the InTouch HMI.
To install the InTouch HMI
The installation program prompts you to select an installation type: either product-based selection or installation by computer roles. As you are only installing InTouch HMI, click the product-based selection as your installation type.
Note: The 16 PenTrend supplementary component is not installed by default. You must select the Customize Installation option and select InTouch 16 PenTrend from the product list to install it as part of the InTouch HMI installation procedure.
Activating Your InTouch License
InTouch uses the AVEVA Enterprise License Server to make licenses available. The AVEVA Enterprise License Manager manages one or more License Servers.
You use the AVEVA Enterprise License Manager interface to make licenses available to InTouch. First, import the entitlement XML file received upon purchase of the license. Then, select which licenses on the entitlement to activate on the License Server. After activation, the license becomes available to WindowMaker or WindowViewer upon start up. The license is released when InTouch is shut down.
InTouch will run in Demo Mode if it cannot consume a valid license at start up time.
To install AVEVA Enterprise licensing, see the AVEVA Enterprise Licensing Guide.
Antivirus Software Exclusions
Antivirus software should be implemented as part of a defense-in-depth strategy to secure your industrial control systems.
Visit https://softwaresupport.aveva.com/ to get the latest information on antivirus software recommendations.
To modify, repair, or remove a product
Note: Modern applications can no longer be created, edited, or run after Application Server is uninstalled from the same computer that also hosts InTouch run time and development components. Modern applications no longer work because the Galaxy Repository required for Modern applications is removed when Application Server is uninstalled.
Upgrading refers to installation on a computer that already has a previous version. An upgrade removes the previous version of InTouch HMI and installs the latest version.
After the hardware and software requirements are met, you can upgrade to the latest version of InTouch HMI from the following versions:
You can only upgrade System Platform products that are already installed. You cannot install any new System Platform products by an upgrade process.
To upgrade from a previous version of the InTouch HMI
Upgrade Notes
Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to InTouch HMI 2023 that were developed with earlier versions of InTouch HMI as shown in the following table:
From |
Upgrade |
Node-by-Node Upgrade |
Migrate |
7.0 |
N |
N/A |
N |
7.1 |
N |
N/A |
N |
7.11 P07 |
N |
N/A |
Y |
8.0 SP2 P04 |
N |
N/A |
Y |
9.0 P03 |
N |
N/A |
Y |
9.5 SP1 |
N |
N/A |
Y |
10.0 SP2 |
N |
N/A |
Y |
10.1 (no SP) |
N |
N/A |
Y |
10.1 SP2 |
N |
N/A |
Y |
10.1 SP2 P01 |
N |
N/A |
Y |
10.1 SP3 |
N |
N/A |
Y |
10.1 SP3 P01 |
N |
N/A |
Y |
11.1 SP1 |
Y |
Y |
Y |
11.1 SP1 P02 |
Y |
Y |
Y |
17.0 |
Y |
Y |
Y |
17.1 |
Y |
Y |
Y |
17.2 |
Y |
Y |
Y |
17.3 |
Y |
Y |
Y |
17.3.1 |
Y |
Y |
Y |
17.3.101 |
Y |
Y |
Y |
20.0.000 |
Y |
Y |
Y |
20.1.000 |
Y |
Y |
Y |
20.1.001 |
Y |
Y |
Y |
20.1.100 |
Y |
Y |
Y |
Note: For InTouch Version 10.2 and newer, refer to the System Platform migration table. InTouch cannot be installed or upgraded as a single product since Version 10.2. Therefore all installed products on a node must be upgraded at the same time.
SPCPro was a Statistical Process Control (SPC) utility available with InTouch HMI prior to Version 11.0. SPCPro is no longer supported by InTouch HMI. We recommend that that you migrate your SPCPro databases to the latest version of QI Analyst if you still use SPCPro with InTouch. QI Analyst provides support for the latest versions of operating systems and databases.
QI Analyst also includes a utility to migrate your SPCPro database to a QI Analyst database, leaving the existing SPCPro database intact. Please contact your local sales representative for further information.
Important Note: We strongly recommend that you migrate your current SPCPro databases to QI Analyst before installing System Platform Version 20.0.000 with InTouch HMI. InTouch no longer includes SPCPro and will not open or migrate applications containing SPCPro components.
InTouch HMI 2023 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.
Defect ID |
SR Number |
Description |
IMS-1464013 |
960085476 |
Trend pen did not plot the graph continuously when values with Quality Details was bad. |
IMS-1489368 IMS-1513734 |
960099638 960111953 |
When a non-administrator user closes the WindowViewer in the RDP session, an error was logged in Event Viewer. |
IMS-1515320 |
960106780 |
Upon exporting the Hist Data with invalid or no dates in the historical data, some users noticed that the Date and Time columns were missing. |
IMS-1517809 |
960105179 |
The script editor failed to align to the screen and render correctly when used in dual screen mode. |
IMS-1521821 |
960113182 |
The InTouch HMI application running in a RDS environment allocated more cores than required, causing an instability in the application. |
IMS-1540602 IMS-1687124 |
960097549 |
Post upgrade to InTouch HMI 2020 R2, when a choice of Symbol Wizard embedded to the object was not used, the system gave an object-level warning message - Could not resolve reference: <Reference> |
IMS-1554949 |
960117750 |
The Alarm Manager stopped responding when queries with long syntax were executed. |
IMS-1573686 |
960119170 |
When the InTouch HMI application was configured with OS-User security settings with Smart card authentication enabled, the smart card login failed at run time. |
IMS-1575580 |
960119547 |
In the Application Script, the syntax validation highlighted errors even for correct syntax. |
IMS-1576918 |
960113571 |
The Store and Forward folder was getting locked by the Historian storage when running an RDS session of the InTouch application configured with Historian. |
IMS-1593973 |
960122249 |
In a German installation of InTouch HMI, the dialog boxes for Historical Logging Properties and Enable Storage to Historian did not contain the options "Log Alarms and Events" and "Alarm Query". |
IMS-1594043 |
960121987 |
When an InTouchViewApp symbol was embedded into an InTouch window with the Show Hierarchical Name option selected in the Galaxy Browser, and the window was closed and reopened, the Custom Properties window displayed incorrect window names. |
IMS-1606290 |
960122254 |
In InTouch HMI 2020, some users noticed that clicking the button configured to launch a popup window, displayed the popup window behind the main window. |
IMS-1607624 |
960125327 |
The InTouch HMI application, configured with storage of Historical logging to Historian, did not send initial tag data to the Historian until the tag value is changed. |
IMS-1611494 |
960126565 |
When an InTouch window was opened from Industrial Graphic using the ShowGraphic script, the Window did not adhere to the location details such as WindowRelativePosition/WindowLocation parameters |
IMS-1626752 |
960128958 |
The Smart card authentication did not function correctly if the smart card was inserted and removed prior to logging into the InTouch HMI application. |
IMS-1630068 |
960128286 |
The width of the SQL Bind List was too small making it difficult to read. |
IMS-1634067 |
960125914 |
During the Graphic template import, if an older version of the graphic template did not contain a wizard and the graphic template was nested in the imported object, the wizard properties are reset to default. |
IMS-1637341 |
960129136 |
While printing windows of the demo application , WindowMaker stopped responding and displayed an error "ucrtbase.dll". |
IMS-1638382 |
960129431 |
Closing two dialog boxes in a sequence caused the WindowViewer to stop responding. |
IMS-1642730 |
960125152 |
In the French version of InTouch HMI application, when a graphic was configured with a User Input animation with float data, the decimal values were not displayed correctly in Web Client. |
IMS-1653438 |
960133290 |
When an alarm client control was set with a filter and embedded on an InTouch window, at runtime, the first set filter was not applied. |
IMS-1660249 |
960135298 |
Post-upgrade to InTouch HMI 2020 r2 sp1, the VLC ActiveX plugin stops responding on when used or accessed in scripts. |
IMS-1663158 |
960136322 |
For German version of the Intouch HMI application, the WindowMaker stopped responding while printing the windows of the Demo application. |
IMS-1665662 |
960124052 |
When the WindowViewer was configured to run as a service, the historical logging of a Managed Application set to Store Logfile in specific shared directory did not work properly, with only intermittent logging. |
IMS-1673267 |
960131605 |
A new tag created in a remote session of WindowMaker was automatically deleted when the WindowMaker was closed and reopened. |
IMS-1676835 |
960134707 |
When the Alarm Client Control in configured in Historical mode was embedded into a symbol, the "TotalRowCount" property did not display accurate values. |
IMS-1677721 |
960138763 |
When a Condition Script or a Data Change Script was imported into an application with an existing script name, a duplicate script was created with the same name, without displaying a warning. |
IMS-1683872 |
960128161 |
The WindowMaker stopped responding when the Cross Reference Utility opened in WindowMaker was later refreshed in WindowViewer |
IMS-1685759 |
960141250 |
When an overlay window was dragged on the screen, a trace of the path traversed was seen until the window was docked. |
IMS-1686718 |
960137325 |
Post-upgrade to InTouch HMI 2020 R2 P01, non-administrator user accounts could not create tags or log data to the Historian server. |
IMS-1687910 |
960137786 |
Post migration to InTouch HMI 2020, the buttons configured with action script with using FileReadFields function, an additional comma was required for the file to be read correctly. |
IMS-1693225 |
960127172 |
An InTouch window configured with the loop back tags to show the Quality and Value fields from the OI Simulator, was closed and reopened, it displayed incorrect quality value. |
IMS-1696144 |
960134870 |
When a symbol embedded with Alarm Client Control and configured to display alarms in the Current Alarm mode, viewing the window in runtime using WindowViewer displayed the hidden alarms also. |
IMS-1712530 |
960145000 |
Upon creating a symbol with Analog Input Link, the user input dialog InTouch Web was displayed transparent with small fonts, making it difficult to use. |
IMS-1720932 |
960139561 |
While switching languages in runtime in WindowViewer, the language change for some symbols and texts and the element style animations did not function as expected. |
IMS-1737982 |
960145342 |
When the Notify Clients Now was executed on the on the master node, the NAD client nodes displayed warning messages to restart the WindowViewer. The WindowViewer took longer than expected to restart. |
IMS-1748816 |
960151686 |
Post upgrade to InTouch HMI 2020R2 SP1, some users encountered scripting errors in the Trend Client Control, wherein, modifying a property also modified other columns in the Control. |
IMS-1757587 |
960148952 |
When a QuickFunction was validated in the Script editor, a warning message with an incorrect function name was displayed. |
IMS-1758939 |
960154314 |
The fonts on number pad was transparent making it illegible. |
IMS-1761996 |
960127172 |
An InTouch window configured with the loop back tags to show the Quality and Value fields from the OI Simulator, was closed and reopened, it displayed incorrect quality value. |
IMS-1762140 |
960153441 |
On a Japanese InTouch HMI application, when the WindowMaker Print option Database entries used in the window was selected, all tag names were incorrectly printed as 0.000000000000000000000000000000000s. |
IMS-1776383 |
960156115 |
Post-migration of a galaxy from System Platform 2014 R2 to System Platform 2020 R2 SP1, when the user tried to log on into InTouch application runtime with incorrect password, then the WindowMaker and WindowViewer stopped responding. |
IMS-1793264 |
960161705 |
On a Russian operating system, when the Alarm Client Control was opened in WindowViewer, the system displayed an exception error, and warning messages were logged in the Logger. |
IMS-1801379 |
960162372 |
Post-upgrade to InTouch HMI 2020R2 SP1 on a Windows Server 2019 system, when a window containing an object with text overlayed on it was dragged, the text appeared to be distorted. |
IMS-1804858 |
960163470 |
Post-conversion of a standalone InTouch application to the latest version, the application was not available in the WindowMaker to edit. |
IMS-1808502 |
960163413 |
The Delete unused tags utility incorrectly detected the tags being used in the Industrial Graphics as being unused. |
IMS-1811254 |
960158530 |
Post-upgrade to InTouch HMI 2020R2 P01, the Alarm Client Control is taking a long time to retrieve data from History blocks using the new query filters. |
IMS-1839233 |
960167569 |
Some users could not change the expired password from WindowViewer using the ArchestrA-based security mode. |
IMS-1840007 |
960167037 |
Some users noticed that the WindowMaker stopped responding and automatically closed when the keyboard shortcut Ctrl + W was pressed when no windows were open. |
IMS-1840980 |
960167998 |
In the Alarm Client Control, the colour configuration for Events would reset if a query was executed which contained a LIKE operator with historical block. |
IMS-1841302 IMS-1787296 |
960169699 960160876 |
The WindowViewer language switching in runtime did not work as expected for a managed application with the cache settings disabled. The header content was translated and the content within the frame symbols did not get translated to the selected language. |
L00160031 |
- |
When the Memory caching is enabled and the option to reset Industrial Graphics cache is checked, some users noticed the following issues:
|
This section describes known issues that remain in the release of InTouch HMI 2023.
Issue ID |
Description |
1928318 |
When the Supertag instances are created by importing from a .CSV file, the imported Supertags are not displayed in the Supertags pane of the WindowMaker. Workaround: The Supertag instances created by importing from a .CSV file can be viewed in the tag dictionary. |
1826926 |
When a window containing a symbol with an embedded MapApp widget is viewed in WindowViewer, the MapApp does not load. Workaround: To view the embedded MapApp widget upon fast switching to WindowViewer:
|
1765301 |
When an existing Custom Client Control or Web Widget is overwritten to the Cloud, the latest version is not available for other users. Workaround: To overwrite an existing Custom Client Control or Web Widget to the Cloud, restart the WindowMaker and delete the existing client control or Web Widget in the source repository. This allows successful upload/download of the the client control. Similarly, restart the WindowMaker to retrieve the latest Custom Client Control or Web Widget. |
TFS-1351507 |
Language switching is not supported for the Carousel Widget in runtime. |
TFS-1369183 |
A Carousel Widget containing the Web Browser Widget, QR Code Scanner Widget, Trend Client Control, Alarm Client Control or SQL Data Grid Control will not display correctly in WindowViewer, as default browser security options prevent cross-origin requests. |
TFS-1372178 |
Carousel widgets in a managed application migrated from InTouch 2020 to InTouch 2020 R2, do not contain the latest properties. Workaround: On migrating a Galaxy from InTouch 2020 to InTouch 2020 R2, run the IDE as an Administrator atleast once, to allow loading the latest InTouch 2020 R2 carousel widget properties. |
TFS-1371799 |
When an InTouch 2020 application (.aapkg) is exported and imported to InTouch 2020 R2, then the default namespace for a tag reference within a Carousel widget is not resolved in runtime. Workaround: Open the graphic containing the Carousel widget. Edit any property and save the graphic. The tag reference is resolved, and the graphic is displayed in runtime. |
TFS-1374896 |
After a graphic/toolset is created, the letter case of the graphic name cannot be changed in WindowMaker. For example: INTOUCH cannot be changed to InTouch. Workaround: Rename the graphic to a temporary name. Rename the graphic again with the correct letter case. For example: Rename INTOUCH to ChangeName and then rename to InTouch. |
TFS-1377672 |
Connecting many clients to a busy OPC UA server may cause various warnings and errors to be logged from the InTouch OPCUA Host process. Warning messages are for information purposes only and do not indicate any loss in functionality. Error message indicate that the operation was aborted. Workaround: It is recommended that client connections to the server be planned and monitored, so not to burden the server and cause connection failures. |
The following table lists corrections to InTouch HMI 2023 documentation. Please note that these changes to the documentation are available in the English version of the Help only, and not in any localized Help.
Location of Change |
Description of Change |
ITOperate.pdf Section 'Web Client Mobile App' |
|
ITBuild.pdf Section 'Suitelink' |
|
ITBuild.pdf Section 'Importing an InTouch Application' |
|
ITBuild.pdf Section 'Updating Web Client Settings Using the Application Manager' |
Updated the Advanced settings for Web Client. |
ITWebBrowser.pdf |
Included new content related to configuring Web Client for OMI ViewApps. |
The InTouch library is offered in two different media:
\AVEVA System Platform\InstallFiles\CD-Intouch\UserDocs\English
You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:
http://www.adobe.com/products/acrobat/readstep2.html
After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu. Context-sensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have open on your computer.
To launch the Help Viewer, on the Windows Start menu, click AVEVA, and then click AVEVA Help.
The AVEVA Help Viewer launches in your default browser.
© 2015-2023 AVEVA Group Limited and its subsidiaries. All rights reserved. | Contact Us |