Release Notes

22127

Interface now properly creates Aliases for tag templates under AF.

22133

Attribute values referencing other event frames are captured regardless of the order event frames are created.

22137

Constraint issues during a "Delayed Start" no longer happen.

22140

Unirecord data sources are now included in unirecord imports and exports.

22156

Cache start and end times can no longer be permanently altered by arbitration events.

22159

PI Event Frames Interface Manager will enable /TS flag option only for Emerson DeltaV and AVEVA Batch Management InBatch.

22166

Running the interface second time in recovery mode resets the Event Frame's Attributes value timestamps. The Event frame attributes are processed differently during updates.

22172

When removing an interface from PI Event Frames Interface Manager, it will also remove any associated services.

22178

Event frames are now merged properly within the cache time.

22181

When adding an interface to PI Event Frames Interface Manager, the instance ID will be initialized as the same value of interface ID.

22185

Batch Interface events are sorted based on timestamputc. If two events have the same timestamputc, property events are processed last.

22197

The Auto generated Attribute names ("Event_1", "Event_2" etc) are now named in proper sequential order.

22205

Property templates are now assigned to the correct batch when there are multiple Procedures/Batches with the exact same name.

22208

PI Event Frames Interface Manager now handles any differences in specifying module database Module Paths and event frames Element Paths correctly.

22209

Interface will no longer have a delay in processing a batch when the local time is greater than GMT.

22211

MONITORTAGWINDOW now defaults to 0, meaning monitor tag counts don't get trimmed to the most recent days of activity and roll over at INT_MAX unless MONITORTAGWINDOW is deliberately set.

22216

Interface ID has been added to the message logs in order to uniquely identify log message.

22218

All generated unirecords will have the placeholder [TIMESTAMP] have the format "YYYY-MM-DD" for a SQL source and "YYYY/MM/DD" for non SQL source like EVT files.

22219

Unit procedure level event frames using different units will no longer be merged.

22221

Monitor tags now accurately reflect the number of batches and their child events.

22224

Bifconfig properly creates new default virtual user service without errors.

22235

Interface configuration for RST and RET reads UnitedStates format standard.

22245

The unit procedure batch id attribute is controlled by the unit procedure recipe template batchid.

22246

BifConfig does not allow older interfaces to edit health tags.

22249

All batch interfaces remove passwords from INI file regardless of parameter capitalization.

22250

Merging issue causes unit procedure and operation not to close.

22260

Batch event frames no longer merge event frames when merging is disabled and unique ids don't match.

22268

All RST and RET within the configuration will be parsed as US format. Fix in current development branch and in 4.3.x.x Branch.

22275

A check that verifies that a Procedure Event Frame and a Unit Procedure Event Frame are both generated by the same interface instance before linking them together.

22283

The Event log source is created during the interface install step.

22464

For interfaces with a version 5.0.0 or greater, PI Event Frames Interface manager nows tail the windows event viewer instead of PI Message log.

23099

Linking is now always available to be configured in PI Event Frames Interface Manager.

23177

BifConfig now stores RST and RET as UTC Note that they can be edited in a local friendly time string and read into the interface correctly. When written by the configuration program, they will write the times out as UTC and a local time string as a comment.

23811

Interfaces now utilize the Event Viewer instead of the SDK message logs.

24552

PI Event Frames Interface Manager now updates the server information icon correctly.

25136

PI Event Frames Interface Manager displays different options based on the installed interface version

25314

AVEVA Branded Install kit.

25811

PI data server collectives and PI buffering to multiple PI data servers is now supported.

26756

With the release of version 5, if you have a batch interface supported batch database, it will no longer be able to write to PIBatch Database. Version 5 only supports Event Frames Customers who need to write to PIBatch. The database needs to stay with Version 4.x.x.x Batch Interfaces.

27091

Extra emphasis on ensuring AF checkin is performed before disconnecting, as well as the addition of the AFAutoCheckin feature.

50935

Addressed advanced parsing issue when using LBE ("Left Bound Exclusive").

52120

Whenever an interface becomes the primary, it will use the /RST command line switch as the start date and process the batches.

67289

UniRecord exports now include all UniRecord fields.

67298

Event sorting is faster and memory consumption is better managed during event queuing.

67926

Interface will not allow Batch events with a zero start time.

68207

BifConfig will now store SCAN values as low as one second without complaint.

68907

Default account to setup interface service is now Default Virtual User (NT Service/).

69287

Updated the PI Event Frames Interface Manager utility to only allow TagPath properties to be set on Asset Templates and Property Templates. Fixed issue where the TAGPATH value was not being saved properly.

69486

All attributes are now created on the correct event frame.

69854

Fixes minor failover issues and includes a health tag that can be used to monitor failover status.

70398

Float tag values are now evaluated correctly.

70403

Message logging includes exception data.

70471

Very long log messages are successfully logged.

72522

Interface stability improvements.

73489

Interface no longer hangs due to locale thread lock issue.

73498

Setup kit creates the event source name under application logs to match with interface application name, which is used by logging framework.

Windows Server 2022 (64-bit)

Yes

Windows Server 2019 (64-bit)

Yes

Windows Server 2016 (64-bit)

Yes

Windows 11 (64-bit)

Yes

Windows 10 (64-bit)

Yes