10.1 Update 1

Designer

• The tag name verification has been improved when configured in the TagName fields, to prevent double .. or . at the beginning of the name. This previously had the side effect of displaying these extra . in the tag list.
• The automatic association of standard symbols now works correctly when dragging DataTemplate tags onto a display.
• Protected to prevent the addition of new blank lines when a script is saved.

• LinearGauge: Revised and improved control.

• TrendChart: The isPause property is now working properly.

• Pushbutton: .Modified to exhibit the same visual behavior as in version 9.2.

• HTML5

  • DataGrid
    • Improved column alignment when updating rows.

  • TrendChart:

    • If the pens are modified to point to another Tag dynamically and very quickly, it might not register the change, or it might not update the pen's legend.
    • Y-axis manual editing allowed.
    • Y-axis roll-through allowed
    • Improved Cursor position.
    • Improved performance.

Historian

• The normalized table would have an index of -1 when a tag was not found in the tag dictionary, when using history with multiple solutions. Now we try to update the dictionary in this case, and we report it via trace message.

Protocol Drivers

• ValueSimulator: The initial value of the ValueSimulator's Address was using the wrong separator, resulting in all parameters being displayed in the first configuration field, even though the runtime functioned correctly.

• Barcode: Allows configuration of end char.

• ControlLogix: Import improved.

TagProviders

• DataHub: Improved performance.

Plug-in

• Improved to eliminate differences based on the order in which the plugin is added.

• The read-only indicator will be visible if the solution part is part of a locked plugin.
• Automatic screen update when an object is updated by an updated plugin.

Report

• An overload of the GetRequestAsync method was created to include the timeout parameter.

Runtime

• The full tag description cannot be updated at runtime; it's a read-only property, but it wasn't set to read-only, leading the user to try to modify it. Now it is explicitly read-only.

Security

• The Guest user should not be configured with a password; this is the system's default user, even when logging off. A protection has been put in place to prevent the password from being set.

• Revised when guest user does not have security rights to edit the solution.
• Create @Client.ChangeUserPasswordWithStatusAsync method.
• Security Policies working properly.

Script

• The TK.ExecuteClassMethodOnClientAsync() method was created.