1​.11

These release notes describe enhancements to Gateway for Unified Engineering and include product upgrades, resolved and known issues where applicable.

Prerequisites

The following tables display the minimum hardware and software requirements for running AVEVA Gateway for Unified Engineering 1.11.

For more information, refer AVEVA Gateway for Unified Engineering 1.11 User Guide.

Hardware

Software

Compatibility

The release is compatible with the following:

New features and enhancements

• Table Export Options for Grids and Database Views: When exporting Grids or Database Views, gateway configuration administrators can now choose how output column names are determined. The new Column name source option allows columns to be named using either their original grid column names or the underlying AVEVA attribute names. An additional Exclude non-attribute columns option allows columns without an underlying attribute to be omitted from the export entirely. These options are available in the export configuration form for the Grid and Database View contexts. Existing configurations and newly created configurations default to the original column name behaviour, ensuring backwards compatibility.

• Configuration Protection: Gateway administrators can now protect gateway configurations using the new Protect configurations security setting. When enabled, configurations stored in the project defaults location are encrypted, reducing the risk of unauthorised access. Configurations are automatically encrypted or decrypted on save when the setting is changed. Exported configurations are always provided in unencrypted form to support import into other projects. This setting is available for AVEVA Unified Engineering 4.1 and later.

• Single Dataset Publishing for AVEVA Integration Service: When publishing Grids or Database Views to AVEVA Integration Service, gateway configuration administrators can now choose whether the published output is grouped as a single dataset (shared acknowledgement ID) or published as separate datasets (one per Grid or Database View). Additionally, publishing to AVEVA Integration Service is now supported for both Engineering and Generic data source types. For more information, refer Other Options

• Publishing:

  • The Engineering Gateway now supports publishing sub-grids alongside the main grid. When the new Sub-grids publish option is enabled, any sub-grids associated with elements in the published grid are automatically included in the publish output. For more information, refer Publish Using User Interface

  • When publishing Grids or Database Views, gateway users can now choose how element data is collected and structured in the published output using the new Item data publishing scope option. The new Attributes mode publishes all display attributes for every element collected by the Grid or Database View, with the output grouped into separate tables or XML files per element type. For more information, refer Publish Using User Interface

  • The Engineering Gateway now supports selecting grids for publishing by their exact name (lstnam attribute) or by glob patterns that match the full grid hierarchy path. This is available in command line mode via the new -SelectedGrids parameter, and in PML macro/TTY mode via three new IEDPublisher methods: SelectGrids(), GetSelectedGrids(), and ClearSelectedGrids(). For more information, refer Publishing Using PML Macros

  • The Engineering Gateway now partially supports delta publishing, allowing only changed data to be published since the last successful publish run for a given configuration. This significantly reduces publish time and system load for large projects. Delta mode is currently supported for Grids only.

• Explicit Attributes for Integration Service Output: When publishing data to AVEVA Integration Service, gateway configuration administrators can now define explicit attributes for Grids and Database Views for Engineering, Draw, and Model. Explicit attributes add named columns to the published table, with values derived from PML1 or PML2 expressions evaluated per element. This makes it straightforward to include element-level metadata such as Name and Class alongside existing grid or database view data. For more information, refer Configure Explicit Attributes for Integration Service Output

• Compatibility: Gateway for Unified Engineering 1.11 is compatible with AVEVA Engineering 15.8.

• Staging Area Cleanup: The Draw, Model, and Engineering gateways now support automatic cleanup of the staging area before publishing. Gateway configuration administrators can define file cleanup patterns for each output context. When publishing, any files in the staging area whose names match the configured patterns are removed before new content is generated. This ensures the staging area contains only files that correspond to elements currently present in the Dabacon product, eliminating stale files from previous publish runs. This feature applies to File System output only and is available in both Advanced and Simplified modes of the Engineering Gateway. For more information, refer Staging Area Cleanup

• Variables and AIS Context Template: Gateway configuration administrators can now define Variables in the General settings of the Configuration Editor and use them to build dynamic Context metadata sent to AVEVA Integration Service when publishing. Three variable types are supported: constant, constant hint (from predefined project or product lists), and PML expression. These features are available in the Engineering, Draw, and Model Gateways. For more information, refer Configure Context for Integration Service Output

• Data Retention Period for AVEVA Integration Service: Gateway configuration administrators can now set a data retention period for data published to AVEVA Integration Service using the new Expiry duration setting (in hours), available in the Integration Service output Other options. When set to 0 (the default), the retention period is controlled by the Integration Service server. When set to a value between 1 and 744 (up to 31 days), the published data expires after the specified number of hours. This setting defaults to 0 for both new and upgraded configurations.