Web HMIResolved Issues
The following issues were resolved in Web HMI 2.2 SP2.
| Issue | Description of Solution |
|---|---|
| DE44065: User and password checks shown in the bootstrapper logs require better formatting for usability. | The bootstrapper now logs user and password checks in an easy-to-read format. |
| DE49326: An unclear warning message appears during the Web HMI installation. | An accurate warning message now appears during the Web HMI installation. |
| DE61325: For Boolean editable fields on mimics, you must type a value. | You are now presented with a drop-down window to select values for Boolean editable fields on mimics. |
| DE62478: In Control Cards, you cannot select a separate HMI/SCADA data variable tag as a Control Point (SetPoint). | A Control Point can now be a separate variable tag. For example, TargetTemperature is the Control Point for ActualTemperature. If you modify the temperature of TargetTemperature, ActualTemperature gradually changes to that termperature. |
| DE66614: In Control Cards, the drop-down list window for the Attribute column does not work in Microsoft Edge. | The drop-down list window for the Attribute column is now working in Microsoft Edge. |
| DE82050: Assets deleted from the Model Editor remain in the Web HMI Runtime navigation hierarchy. As a result, the Runtime navigation hierarchy is out of synch with the Web HMI Asset Model. | The Runtime navigation hierarchy is now in synch with the Web HMI Asset Model. You no longer have to manually remove all assets from the Runtime navigation hierarchy that were deleted from the Model Editor. |
| DE89913: When Web HMI cannot reach a connected Workflow server, its responsiness slows down considerably. | The timer intervals are now set to greatly improve the responsiness of Web HMI. |
| US239904: A click zone on a mimic cannot relatively reference a child object. | Click zone navigation allows for both absolute and relative paths for click targets at the object type and the object level. |