Decode a status of 16G correctly in messages from NetConnect
For historical reasons 16G was being decoded differently in messages received from the recipient in ENOM configured with the Edigas code NCGVHP to its use by other players. NCGVHP are changing their use of this status code in NOMRES messages from version 4.7 to bring it inline with its use elswhere. This fix allows 16G to be interpreted correctly as “Confirmed” in messages of this format from the NetConnect recipient.
Regional settings error on Balancing screen
Fixed a bug where an error message could be displayed on the Balancing screen for certain Windows regional settings.
Language settings error for SQL Server database upgrades
Fixed a bug upgrading SQL Server databases from ENOM v7.06 or earlier. An error could occur for certain SQL Server language settings.
Performance issue for outgoing messages
Fixed a performance issue in the ENOM service. Generating outgoing messages could be slow for SQL Server databases.
Support for DVGW package 17 format messages
ENOM now supports DVGW specification messages: ALOCAT 5.10 (TDDA,TDPA,TPA and TDA), CHACAP 4.6 (CHACAP and CHACAPR), IMBNOT 5.7, NOMINT 4.6 (CDT) and NOMRES 4.7 (HCN and HDT)
NCG Control Energy custom REQEST and REQRES
Added support for Netconnect’s implementation of REQEST and REQRES (BDR and SDR) as used only for the control energy process.
Sort Order for Messages
Fixed a bug where ENOM was not correctly sorting messages by creation time with the Only Latest option selected.
Balancing Zone Name duplication
Fixed a bug where ENOM would allow a balance name to be duplicated when editing.
Migrate some message functionality to a newer database provider
We are in the process of migrating ENOM database access to a newer database provider technology. This version has migrated some message functionality, including searching for messages in the Message Viewer and identifying messages to be added to the outbox.
As a result of this change, the ENOM database owner requires permission to create database views and the ENOM database application user requires permission to read database views. This applies whether ENOM is using an Oracle or SQL Server database.
Fix use of proxy servers for message boxes
ENOM can now be configured to use a proxy server when connecting to an FTP or SFTP type message box again. This feature was broken in previous versions.
Remove redundant filters from ENOM message viewer screen
Removed the broken “Received” and “Unprocessed M&B” filters from the ENOM message viewer and renamed the “Sent and Received” option to “Outgoing and Incoming”.
Large files sent over SFTP block other files from being downloaded
Fixed a bug where large files were downloaded by ENOM but not deleted from an FTP inbox due to a timeout issue.
170: Enable hourly values “Fully Expanded” setting for Edig@s XML V5.1 NOMINT (SDT)
When the setting “Fully Expanded” is selected on the Nomination Encoding tab for a Recipient, ENOM now encodes each hour in V5.1 NOMINT Edig@s messages to that Recipient in separate Period elements. This was done to enable kWh/h nominations at SNAM interconnection points.
271: Support METRED V5.1.3 messages
ENOM now decodes METRED 5.1.3 messages as used by Swedegas.
222: Locks and logs referred incorrectly to “Local Folder” when using FTP for message boxes
Fixed a bug where the ENOM service referred to local paths when logging FTP activity. This bug also caused the ENOM service to incorrectly use the Local Path set for the FTP Outbox as part of the lock name when taking locks on message boxes.
270: Increment version number when encoding V5.1 ACKNOW
Fixed a bug where the version numbers of these ACKNOW messages created by ENOM were not incrementing with each message.
218: ENOM Service cannot obtain a lock for long message box paths
Fixed a bug where ENOM could not obtain a lock when the length of the path to a message box caused the lock name to exceed 128 characters.
189: Enable “Fully Expanded” setting for Edig@s XML V4 REQEST (BDR) messages.
It is now possible to encode V4 XML format BDR messages in which each hour of a time interval appears in its own time interval element. This change was made to support GRTgaz Hourly Profile Declarations.
166: Create ENOM XML with multiple units in response to receipt of NOMRES messages containing one hourly and one daily unit.
When ENOM received an XML V5.1 NOMRES (TDT) containing two connection points, each using a different unit, the ENOM XML created to integrate with other systems did not include both units. ENOM now supports this behaviour and reports both units correctly.
223: Replace release notes with direction to GMSL website.
The menu option Help > Release Notes has been removed. It is no longer possible to view release notes inside ENOM.
132: Update to version numbering system
We have changed ENOM’s version numbering system to remove our internal build number from the version number we use externally. ENOM version numbers now follow the format Major.Minor.Hotfix. This has resulted in superficial changes to the “About” screen and to the ENOM installers.
82852: Encode PSV Notice
ENOM now supports the creation of PSV trade files for automatic upload to SNAM. A new message type “PSV Notice” has been created for this purpose. These messages allow users to post multiple trades directly to SNAM’s PSV portal for a single gas day over AS4. On the PSV portal these trades will appear as “Emessa” (submitted), ready for acceptance by your trading partners.
35: Decode PSV acknowledgement message
ENOM now supports the decoding of PSV Message Acknowledgements; called PSVACK in ENOM. These messages will be sent by SNAM to confirm Receipt of PSV Notices. PSVACK messages will populate the Ack column of the viewer in ENOM for the notices to which they correspond with “Accepted” or “Rejected”.
71388: Support v5 METRED message
ENOM now supports decoding of incoming v5 METRED messages. These are currently used by TEREGA (TIGF) in reporting the allocated values for some meters/locations, and by Astora Storage (for confirmed actual gas volumes in storage).
71134: v5.1 CAPDOC
ENOM now supports decoding of the v5.1 XML CAPDOC (DVGW implementation) messages used by German TSOs. Messages with type XCG are displayed in ENOM as Message Type ‘(CAPDOC) Changed Capacity Notice’. Messages with type XDG are displayed as ‘(CAPDOCR) Renomination Restrictions.’
84909: ENOM should allow non-dbo schema names in SQL Server
Fixes a bug where ENOM could not connect to a SQL Server database. This occurred if the ENOM objects were not in the dbo schema.
83200: Simplify TextBox Validation
Some config screens have had as you type validation (which turned the text red until valid) replaced with a validation popup when you click save. On the ‘File’ > ‘Local Settings’ screen ‘Notification’ tab, the validation checking the sound file exists. On the ‘Maintenance’ > ‘System’ screen ‘General’ tab, the validation checking the logo file exists. Also as you type validation on the ‘Maintenance’ > ‘Message Rules’ screen that checked email addresses contained the ‘@’ symbol has been removed.
83676: Error if ENOM Oracle user is not the schema owner
Fixes a bug where ENOM could not connect to an Oracle database. This occurred if the user it was connecting as had permissions on schema objects but was not the schema owner.
82436: [Matching and Balancing] Remove Balancing hubs support from ENOM
Support for Balancing Hubs has been removed from ENOM+. Balancing Hub-related settings have been removed from the Shipper Code and Location configuration screens. The Balancing Hubs tab has been removed from the Matching and Balancing configuration screen.
The “Hub Transit” nomination type is no longer available as an option. Any existing Matching and Balancing data that was processed using this nomination type will be be removed. This will only affect data for the Fluxys network prior to the introduction of the ‘Entry/Exit Model’ in 2012. Please contact us before upgrading if you have any concerns about issues this may cause.
79964: [Matching and Balancing] Support Code Mapping for Quantity Type in contract messages
In ENOM+ Code Mappings can be configured to match Quantity Nature attributes. This makes it possible for Matching to match Quantity Nature values on REQRES (BDR) messages to different Quantity Type values in REQEST (SDR) messages. This change applies to V4 XML messages only.
69584: Support v4.6 DVGW NOMRES messages with a validity period of less than 24 hours
ENOM now supports decoding within-day NOMRES messages (v4.6 DVGW ‘HCN’ messages), as used by NCGVHP when no day ahead nomination has been made.
68917: [REQEST/REQRES] Enable hourly BDR/SDR contents to be emailed
ENOM now supports forwarding v4 XML REQEST and REQRES (BDR and SDR) messages via email in HTML format. The HTML format for these messages can also be generated and saved to a folder. .
68919: [REQEST/REQRES] Enable daily BDR/SDR contents to be emailed
82435: [Matching and Balancing] Remove Journey Shrinkage from ENOM
The journey shrinkage functionality has been removed from ENOM+. This was used to model the pre-2012 Fluxys point to point network.
81813: Update German ALOCAT ENOM message types
DVGW ALOCATs of type ‘X7G’ (in DVGW terms: ‘Corrected Allocation: Billing Calorific Values’) now decode in ENOM as ‘TDAs’ (TSO’s Definitive Allocation). Previously these messages decoded as ‘TPAs’ (TSO’s Provisional Allocation). As a result, the Output ENOM XML for this message type has changed the value of the attribute for ‘report_type’ to be ‘definitive’, instead of ‘provisional’.
79904: XML files with too many locations fail to be added to the XML Queue
ENOM XML files with a long list of locations no longer need to be ‘Automatically sent’. If users wish, they can now use the ‘XML Queue’ and be manually sent from there.
81613: File/Folder config paths no longer being validated relative to the ENOM Client location when being used by the ENOM Service.
The ENOM Client no longer validates that it can access file and folder path configuration settings that are used by the ENOM Service. Folder dialogs have also been removed as they were browsing folders on the ENOM Client Computer rather than the ENOM Service computer.
7.00.520: ENOM as a Service
The ENOM Client no longer performs any polling of configured ‘Outboxes’ or ‘Inboxes’ for the sending/receiving of raw Edigas messages. The new ENOM Service performs these tasks, and must be installed, configured and running in order for message processing to occur.
- As a result, the Send/Receive user settings have been changed - there is no longer the option to grant an ENOM user the ability to ‘Send/Receive Messages Automatically’. Sending and receiving messages is now automatically done by the ENOM Service.
- The ENOM Client no longer processes any Input XML files to generate ‘raw’ Edigas messages, nor will it generate XML files on receipt/sending of raw Edigas messages. These Tasks are also performed by the ENOM Service.
- As a result, the option for specific ENOM Users to process input ENOM XML has been removed.
- The ENOM Service will only use the ‘System XML Inbox’. It will no longer be possible to use or configure a locally set XML Inbox (previously set from >File>Local Settings).
- Message Rules are now processed by the ENOM Service. Any trigger (message sent or received) and the resultant action (email notification, Output ENOM XML file generated, HTML file generated) is now carried out by the ENOM Service.
- Message sending and receiving is now handled concurrently. This means that ENOM will poll Inboxes for new messages whilst simultaneously processing messages to Outboxes from the ‘Unsent’ queue.
7.00.520: ENOM Service writes to Windows Event Log
By default the ENOM Service writes its Critical Warnings to the Windows Event Log. Additional debug logging and email notifications and warnings can be enabled using the Log4Net settings in the EnomService.exe.config file.
7.00.520: ENOM Service Licence check
The Service will perform its own licence check, and generate warnings when the licence is close to expiring (at 1 month, and then daily 2 weeks prior to expiry). Licences will expire at midnight UTC on the licence expiration date.
7.00.520: ENOM Service to use database schema checker
The ENOM Service will check the ENOM Database for errors following an upgrade, using the ENOM Schema Checker. If errors are found, the Service will not start and instead will write a schema report to the directory specified in the EnomService.exe.config file. The target directory can be modified by editing the appropriate value in the ‘<appSettings>’ element.
7.00.520: Various settings removed
Various settings have been removed from the >Maintenance>System>General screen as a result of both the Service and removal of legacy features.
7.00.520: Use of App.config files
Both the ENOM Service and the ENOM Client now have their own ‘App.config’ file, which contains some mandatory information, such as the Database connection string(s), and some optional settings, such as Log4Net logging. These files are contained inside the install directory for the ENOM Client and/or ENOM Service, and should not be removed or renamed.
The ENOM Client App.config file is named ‘Enom.exe.config’, and the ENOM Service App.config file is named ‘EnomService.exe.config’.
7.00.520: Database Connection Strings in the App.config files
The ENOM Client application.exe shortcuts no longer contain the database connection string or debug logging information. This information is held in the Enom.exe.config file.
Users with multiple ENOM Databases configured can select from the databases in the App.config file when opening the ENOM Client application, or an ENOM Client.exe shortcut can be given a default database to connect to (still named in the Enom.exe.config file).
7.00.520: ENOM Service Log4Net support
When configured, the Log4Net settings in the EnomService.exe.config file will also generate additional notifications for users, informing them of changes to the Enom Service status, and any problems experienced.
7.00.520: Support shared configuration in a network file
When using multiple ENOM Clients you can share the configuration in a network location by moving the ENOM.exe.config file to this network location, and replacing it in the installation directory with a simple ENOM.exe.config file that redirects to this network location.
The network file can contain a user’s database connection string, Log4Net logging and notification configuration.
7.00.520: Support shared connection strings in a network file
Network config files can share the connection string for a database to a single network file, used by both ENOM Client and ENOM Service.
7.00.520: Support encryption of database connection strings in App.config files
The App.config files for the ENOM Client and ENOM Service support encryption of the database connection string(s), using the ‘GMSL Connection String Tool.exe’, which is included in the installation.
This tool allows a user to load and edit connection strings from the App.config files, and to generate a unique encryption key to encrypt the connection string.
When using network shared configuration files, the tool must be also be used to import the encryption key to the required PCs, so that each installation of the Client or Service can decrypt the string.
7.00.520: Support back-up App.config files
Back-up App.config files can be specified in the event that the primary file becomes inaccessible. The ENOM Service must be restarted in order for it to switch back to a Primary file.
7.00.520: System Notifications
ENOM Service will generate relevant ‘System Notification’ emails that were originally generated by the ENOM Client for support users, in the event of problems experienced by ENOM related to infrastructure etc.
75754: Support multiple ENOM services pointing at the same ENOM database.
Multiple instances of the ENOM Service can be run on the user’s database at any time, allowing for back-up/redundancy.
75798: Service status
The ENOM Client now shows the status of the background service in the top right corner of the main ENOM screen. This display informs users when the ENOM Service is successfully connected to the ENOM Database. If there is a potential problem and/or the ENOM Service is not connected to the Database, the Service Status reports this.
76361: ENOM Activity Log
‘The ENOM Client no longer has the ‘FTP Log’, ‘XML Log’ or ‘Email Log’. These have been replaced with an ENOM ‘Activity Log’, which summarises Edigas messaging and ENOM XML processing activities that the ENOM Service has performed. Errors and failures in these processes are also reported.
This log has various features:
- This log has an auto-refresh every 20 seconds, or the user can force a refresh action.
- The log will identify the Message Box involved in each activity.
- Where possible, the log will identify the ENOM Recipient for each message sent/received.
- The log identifies when the ENOM Service has failed to perform a messaging action.
7.00.520: Replace Local Setting Notifications
The Activity Log replaces the ‘Notifications’ pop-up windows that were set locally for each ENOM client to alert users of specific ENOM actions (‘Messages sent successfully’, ‘Messages failed to send’, ‘New Message received’).
Instead, users can set the Activity Log to pop-up or appear when events occur. These settings are still set locally to each ENOM Client, but are set on their own tab in the ‘Local Settings’ screen. This screen also allows users to highlight specific types of activity in the log with user-chosen colours.
There are now 2 ENOM installers, one for installing/updating the ENOM Service, and one for installing/updating ENOM clients.
7.00.520: ENOM Service FTP dependency
The ENOM Service’s FTP functionality contains a dependency on the Microsoft Visual C++ Redistributable Package 2015. This package is included with the service installer and will be installed automatically.
22472: Move ENOM to use WodFTPDLX.NET
The third party FTP component ENOM uses has been updated. This was done to support newer Diffie-Hellman key exchange protocols. We recommend testing your Message Box settings work correctly with the new version.
82938: Support Windows Server 2016
ENOM now supports Windows Server 2016
76886: Support Oracle 12.2
ENOM now supports Oracle 12.2.
81345: Update .Net framework version
ENOM has been updated to use .NET Framework 4.7.2. This must therefore be installed on any machines running the ENOM client or service.
82540: Add option to the ENOM Client installer for Desktop and/or Start Menu shortcuts
The ENOM Client Installer now comes with options to create Desktop and Start Menu shortcuts on installation.
80408: Replace Hour Adjustment Value with Time Zone
The ‘Hour Adjustment’ setting for ENOM Recipients has been replaced with a more intuitive ‘Time Zone’ for each Recipient.
This change will be applied across all of your existing Recipients when the Database upgrade is performed. When providing the database upgrade script, the ENOM Team will ask you for the time zone that you run your own ENOM system in.
Each Recipient’s time zone is then calculated based on your own time zone and the existing ‘Hour Adjustment’ values set for your configured Recipients. ENOM 7 currently supports: UK time (GMT/BST), CET time (CET/CEST) and EET (EET/EEST), applying Daylight Saving Time as appropriate.
If your own ENOM system, or that of any recipients, is outside of these time zones, please contact us prior to attempting to install ENOM 7.
ENOM+ customers should check that the correct ‘Time Zone’ is set for their activities under the ‘Matching and Balancing’ configuration on the >Maintenance>System>General screen. By default, this is set to ‘CET/CEST’, as most users will be checking matching for recipients in CET Europe.
80462: Client/service should fetch all date-times from database
ENOM now stores Audit Dates and Time Stamps in the database in UTC, previously these were stored in the local timezone of the computer running the ENOM Client.
Where appropriate ENOM converts this to a local time for the user.
Time Stamps in outgoing enom xml messages are also now in UTC, these previously used a mixture of timezones.
In Matching (ENOM+ customers), creation times for a nomination/confirmation message are still shown in the local time (with the adjustment from UTC shown) of the sender.
7.00.520: Handling different time zones
As a result of the changes to handling time zones: all ENOM Clients, the ENOM Service and the ENOM Database can now operate from PCs running in different time zones.
81626: Resend the same message (v5 SDT, v5 TPD XPD and EPD, v4 DVGW CDTs) for a period of multiple days
ENOM can send the same message for multiple days, this functionality is available on Edigas v5 PRODOCS (TPD, EPD and XPD) and on certain NOMINTS: Edigas v5 SDT; DVGW v4.4 CDT; DVGW v4.5 CDT.
81586: Remove Send Immediately option in System config
The ‘Send Messages Immediately’ option has been removed from the System screen. The ENOM Service will process outgoing messages for sending immediately as standard, including messages created in the ENOM client UI.
81364: Oracle - VARCHAR2 columns to use CHAR instead of BYTE
Upgraded Oracle ENOM databases now measure the maximum amount of data stored in varchar2 columns in characters rather than bytes. This is to improve support for databases using multibyte character sets.
7.00.520: Support for running database upgrade scripts
We only support running Database Upgrade Scripts in sqlcmd (SQL Server) and SQL*Plus (Oracle). Please contact the ENOM team before using other applications.
73521: Drop Support for Jet Provider for Access Databases
ENOM no longer supports the Jet provider for Microsoft Access databases.
76135: Clicking on rules in Message Rules cause ‘…save changes?’ window to pop up
The message rules pop-up window that asks ‘Do you wish to save changes?’, it’s ‘Cancel’ button now takes you back to the rule that was just changed.
7.00.520: Correction of labels on GTS Balacing Info screen
The two labels displaying the time ‘Last Updated Prognosis Values’ on the GTS Balancing Info screen have been corrected to make the labelling accurate; one continues to display the last time the prognosis values were updated, and the other has been corrected to ‘Last Updated Accountable Values’, indicating when the allocated account data was updated.
77376: [v5.1 ACKNOW] Make receiving document version optional
ENOM now decodes v5.1 ACKNOW messages that do not use the referenced message version number, but only reference the original message’s creation time. This change supports v5.1 ACKNOW messages used by Open Grid Europe.
77918: [v5.1 ACKNOW] - Support Rejection_ConnectionPoint when no coding scheme attribute is given
ENOM now decodes v5.1 ACKNOW messages that are missing the ‘codingScheme’ attribute on a <Rejection_ConnectionPoint><identification> element.
This is to support decoding ACKNOW messages sent by Gaz-Systems.
77622: Support v2.1b APERAK messages from NCG
ENOM now supports v2.1b BDEW APERAK messages as used by NCG.
77039: [Release Notes] Add support for TLS 1.2
The Release Notes buttons in ‘Help’ > ‘About’ now support using TLS 1.2 in order to support access to the GMSL Release Notes server in the future. The labels for accessing the release notes have been updated to better reflect the options for viewing them.
75295: Schema checker ignores auto-generated Oracle ‘sys_’ columns in indices
Columns added automatically to ENOM database indices by Oracle (e.g. for Extended Statistics) could sometimes cause the Schema Checker to incorrectly report inconsistencies with the ENOM database schema. The Schema checker has been updated to ignore such columns when running ENOM using Oracle.
76000: Support encoding v5 NOMINTs to TAG
ENOM now encodes v5 NOMINTs to TAG with the issuer market role code ‘ZSY’ (Balance Area Responsible).
72359: [v5.1 NOMRES] Support Message Type ‘07G’
ENOM is now able to decode v5.1 NOMRES messages with message type ‘07G’. These messages appear as TSO’s Processing Notifications (TPNs), which indicate the nominations that a TSO has successfully received from a shipper.
74461: ENOM supports the new format of NCG APERAKs
For DVGW APERAK messages ENOM now decodes messages with RFF lines below the ERC line. ENOM also now translates the error code Z31 ‘Transaction is rejected by the recipient’ and the freetext code AA0. These are used by NCG from 4th July.
74293: Allow ‘ZZZ’ to be used as a recipient coding scheme
ENOM now supports ‘ZZZ’ as a code list identifier when decoding recipients on incoming messages. ENOM treats any recipient codes using this code list identifier as EIC codes.
72811: Opening Message Rules filters configuration can be very slow
There have been some changes made to improve the performance of the Message Rules especially the configuration screens.
74565: Prevent ENOM lockstrings from containing localised dates
Under certain circumstances when using Windows regional settings other than English ENOM could fail to remove database lock strings. This has now been fixed.
74024: Improve ENOM performance sending emails using SMTP servers without TLS encryption
If the SMTP server used by ENOM did not support encryption or was incorrectly configured, this could cause ENOM to send emails slowly, or the sending to fail.
To avoid this issue, ENOM now attempts to use TLS encryption only when the setting is enabled under the email configuration on the ‘System’ screen.
72425: [ENOM Client] Renew lost database connection
When ENOM is disconnected from the database it will now try to automatically reconnect.
71091: Unable to view Raw Edigas Message in UI
Fixed a bug that meant some xml messages did not display correctly in the ‘Raw Message’ tab of the ‘Message Properties’ screen.
72031: Error using international time separators
Fixed a bug where the message viewer did not function correctly if the ‘Windows Regional’ setting for the time separator was not the ‘:’ character.
71214: [M&B Processing] Use UTC Creation Time for determining message order
Matching and balancing now uses the UTC creation time, rather than local creation time, when determining relative message order. Previously this had led to some messages not being marked as ‘Confirmed’, because the corresponding confirmation message had an earlier local time than the original outgoing message.
68809: [EDI Messages] Support Escape Character
To support the use of free text sections in MOGO16 messages, ENOM now supports an ‘escape character’ in EDI format messages, read from the UNA segment of the message if specified, otherwise it will default to using “?”.
68411: Remove line breaks from ENOM email subjects
Fixed a bug where certain ENOM notification emails were rejected by the outgoing email server due to line breaks in the email subject.
70790: Errors closing ENOM caused excessive writing to the log file
A bug has been fixed whereby in certain situations, if an error occurred closing ENOM, a rogue ENOM process would write to the ENOM log file in an infinite loop.
This had performance impacts on the PC, the network and any ENOM instances sharing the same log file.
69590: Allow ENOM to use Windows Active Directory user accounts
ENOM can now be configured to allocate user permissions to Active Directory users on your network domain.
31038: [M&B] Use REQEST and REQRES messages
ENOM now supports processing ‘nomination’ data from REQEST (v3 EDI, v4 DVGW, v4 XML BDR/BWR), and ‘confirmation’ data from REQRES (v3 EDI, v4 DVGW, v4 XML SDR/SWR) messages, for use in Matching and Balancing.
28714: Files to be processed in chronological order by ‘Last Modified’ time
ENOM now processes files in order according to their reported last modified time, rather than alphabetically by name. This change applies to raw messages processed via the FTP and Windows folder message boxes, and to XML files processed via the ENOM XML interface.
66538: Improve M&B background processing
We have made some improvements to the background processing of Matching and Balancing.
66824: Support Authenticated SMTP with TLS in ENOM
ENOM now supports sending email using authenticated SMTP. Furthermore, communication with the SMTP server may be encrypted using transport layer security (TLS).
68045: [TCN v3] Enable column and row totals
Row and column totals will now be displayed for v3 Edigas TCN messages.
68626: Redesign Enom Closing screen code.
The ENOM closing form will now display which background tasks are tidying up.
68582: [NOMINT v4 Daily] Period elements duplicated for messages with multiple capacity types
Fixed a bug in v4 NOMINT (SDT) messages with daily granularity where ENOM created duplicate nominations in the raw Edigas message for messages containing multiple capacity types for the same Location and Shipper combination.
44553: [UI] Improve performance for databases with large numbers of unread messages
The general performance of ENOM has been improved when there are a large number of unread messages.
64025: v5.1 Edigas messages for Snam Rete Gas
ENOM now supports v5.1 Edigas XML messages used by Snam Rete Gas. This includes v5.1 Edigas XML NOMINT (nomination), NOMRES (confirmation), ACKNOW (acknowledgement) and ALOCAT (allocation) messages.
67996: [v5.1 ALOCAT] Support hourly granularity for day long validity periods
ENOM now supports decoding v5.1 ALOCAT (TDA, TDDA, TPA, TDPA) messages with hourly granularity for message periods of up to 1 day. Previously such messages were supported for messages of a single hour only.
65415: [v5.1 NOMINT] Change release attribute
ENOM now supports encoding and decoding v5.1 Edigas XML NOMINT (SDT, SMT) messages according to release 3 of the Edigas specification. The “release” attribute generated when creating these messages has been updated accordingly.
67551: Rename tabs in Message Properties
The “Raw Message” and “Enom XML” tabs in Message Properties have been renamed to “Raw Edigas Message” and “Internal ENOM Format”, respectively.
67287: [Local Settings] Unexpected error when ‘Notify when messages are sent’ enabled
The behaviour when Notifications are set from File > Local Settings has been modified. This should fix bugs where unexpected errors were seen in some circumstances.
The notification pop-up will no longer take the focus from other Windows applications and the ENOM Windows taskbar icon will flash if there is a new notification.
67457: MOGO16 - Support starting buffer balance, buffer nomination values and free text
ENOM can now decode the new version of the MOGO16 “Maersk Production Forecast” messages. Additional codes denoting the ‘Buffer Nomination’ and ‘Starting Buffer Balance’ are now supported, along with the display of additional text information from Maersk.
This feature is only enabled for customers with an appropriate licence.
67926: Selection of v5 Edigas message identification formats
The ‘Nomination Encoding’ tab on Maintenance > Recipients has been updated to prepare for additional types of v5 Edigas message identification formats to be supported in future versions of ENOM.
66725: Schema Checker ignores auto-generated Oracle “sys_” columns
Columns added automatically to ENOM database tables by Oracle (e.g. for Extended Statistics) could sometimes cause the Schema Checker to incorrectly report inconsistencies with the ENOM database schema. The Schema checker has been updated to ignore such columns when running ENOM using Oracle.
66139: [AVAILY] Enable AVAILY contents to be emailed
ENOM now supports forwarding daily and weekly AVAILY (v3 EDI SDA, v3 EDI SWA, v4 XML SDA and v4 XML SWA) messages via email in HTML format. The HTML format for these messages can also be generated and saved to a folder.
66302: Support v4 XML CONTRL messages
ENOM now supports decoding CONTRL messages in v4 XML format. Note that the ENOM XML produced for other CONTRL messages has been updated. The specific changes are detailed in new versions of the XSD documents relating to these messages.
66306: Email log to appear in ENOM’s debugging log
Information written to the Email Log screen in ENOM is now duplicated in the ENOM log file when logging is enabled.
66590: [Maersk messages] MOGAPP doesn’t reference the correct message ident
MOGAPP and NOGAPP (acknowledgement) messages generated by ENOM now correctly reference messages with identification numbers longer than 6 digits.
64575: Support SQL Server 2016
ENOM can now be used with SQL Server 2016 using SQL Server native client version SQLNCLI11.1.
62793: ENOM slow processing of ENOM XML files
Reported slow performance relating to the processing of ENOM XML files has been addressed. The overall performance of ENOM to process ENOM XML files, FTP processes and email rules has been increased.
65696: Compress messages to reduce size of database
Raw message data is now stored in the ENOM database in a compressed format, to reduce the amount of storage space required. New messages will be saved in this format automatically. Existing messages can be compressed using the ENOM database tool.
65052: Support v5.6 DVGW IMBNOT
ENOM is now able to decode v5.6 DVGW IMBNOT messages.
51281: v5.1 Edigas messages for GTS
ENOM now supports v5.1 Edigas XML messages as used by GTS. This includes v5.1 Edigas XML NOMINT (nomination), NOMRES (confirmation), ACKNOW (acknowledgement), PRODOC (programme document), PROCON (programme confirmation), CLRCON (clearing confirmation), BALDOC (balancing agreement document) and BALCON (balancing agreement confirmation) messages.
64724: Support v5.9 DVGW ALOCAT
ENOM is now able to decode v5.9 DVGW ALOCAT (TDDA, TDPA, NDDA, TPA, TDA and NDA) messages.
66080: [v4 XML APERAK] Change to reason codes
The reason displayed when viewing a v4 XML APERAK message will now only capitalise the first letter of the first word. Previously the first letter of every word was capitalised. This change will also affect the ENOM XML files, where the description attribute will now always be lower case.
66085: [v5A XML BALCON] Change to status in RBAN and SBAN messages
The ‘Status’ displayed when viewing a v5A XML BALCON (RBAN and SBAN) message will now only capitalise the first letter of the first word. Previously the first letter of every word was capitalised. This change will also affect the ENOM XML files, where the status attribute will now always be lower case.
64910: v5.1 ACKNOW - Support multiple reason codes
ENOM now supports multiple reason codes for v5.1 ACKNOW (acknowledgement) messages. When a single ACKNOW message contains reason codes which correspond to different acknowledgement statuses, the status displayed in the Message Viewer is the one with the highest priority, in the order ‘Rejected’, ‘Accepted with remarks’, ‘Accepted’.
65244: Changes to BALCON (RBAC and SBAC) messages
RBAC (Receiver’s Balancing Agreement Confirmation) and SBAC (Supplier’s Balancing Agreement Confirmation) messages have had their ‘Message Format’ updated from ‘Edigas v5 (XML)’ to ‘Edigas v5A (XML)’.
This will affect the ENOM XML for these messages.
65185: Changes to BALDOC (RBAN and SBAN) messages
RBAN (Receiver’s Balancing Agreement Notice) and SBAN (Supplier’s Balancing Agreement Notice) messages have had their ‘Message Format’ updated from ‘Edigas v5 (XML)’ to ‘Edigas v5A (XML)’.
This will affect the ENOM XML for these messages.
64671: Support TLS 1.2 for GTS B2B services
ENOM now supports using TLS 1.2 for the GTS B2B services to download POS and SBS data. This will be required when GTS drop support for TLS 1.0. As a result, at least version 4.5.2 of Microsoft .NET Framework must be installed on each PC running ENOM/ENOM+. Further, Windows Vista and Windows Server 2003 are no longer supported.
64434: Resend for option should take the time zone of the recipient into consideration
When creating and resending messages for a single gas day, or creating and editing external nominations, the time zone information configured for the recipient is now used to calculate the correct gas day for today or tomorrow.
64408: Support acknowledgement messages from Enagas
ENOM now supports receiving v5.1 Edigas XML ACKNOW messages with both milliseconds and time zone information in the creation time.
62898: [Message Rules] Ability to customise email alerts by filtering out messages based on time of day
Email message rules can now be configured to ignore messages that are not for within-day until a user-specified hour. After the specified time, the message rule will trigger for any messages regardless of whether they are for within-day, day-ahead or any other time period.
64437: ENOM can attempt to process the same ENOM XML file multiple times
In some circumstances, ENOM attempted to process an ENOM XML file after it had already been imported, meaning the second attempt would fail. This has been fixed, so that ENOM only attempts to process the file once.
63899: [Compare Messages] Error switching between messages with different shipper codes
Fixed a bug that caused an error in Compare Messages (Matching) when changing to view historical messages containing different shipper codes.
63789: v5 XML messages, unit cut off
A bug has been fixed which was causing the units dropdown box to be partially hidden on some v5.1 Edigas XML messages.
63908: Decode messages from Dunkerque LNG with the correct interpretation of credit/debit
Messages from Dunkerque LNG will now display credit as negative and debit as positive.
63953: Support Windows 10
Using ENOM on Windows 10 is now supported.
63709: Edigas messages for GAZ-SYSTEM S.A.
ENOM now supports Edigas messages as used by GAZ-SYSTEM S.A. This includes v4 and v5.1 Edigas XML NOMINT (nomination), v4 and v5.1 Edigas XML NOMRES (confirmation), v5.B and v5.1 Edigas XML ACKNOW (acknowledgement) messages.
61705: [Compare Messages UI] Improve performance
Changes have been made to try and improve the performance of the ‘Compare Messages’ screen when initially opened. In some circumstances, this screen was noticeably slow when opening.
63288: ENOM freezing after opening
A bug has been fixed where email notifications caused ENOM to lock. This lock initially occurred just after starting ENOM.
63502: [Message Boxes] FTP inbox temp folder errors
Fixed a bug where relative temporary folder paths were not working for FTP message boxes (i.e. the complete path would need to be specified rather than just the additional temporary folder).
62363: Edigas messages for Eustream
ENOM now supports the Edigas messages used by Eustream. This includes v4 Edigas XML NOMINT (nomination), v4 Edigas XML NOMRES (confirmation) and v5.1 Edigas XML ACCSIT (imbalance) messages.
63383: Unexpected error when resending
A bug has been fixed where pressing the Resend button on a Message could cause an error.
51609: [FTP] Error returned during uploading may cause incorrect message to be marked as sent
When using ENOM with FTP message boxes, in some circumstances the same message would be sent twice while another message would not be sent at all. The code associated with sending and receiving via FTP has been rewritten in an attempt to avoid such issues occurring.
61219: Make it more obvious when there are unsent messages
The ‘Send/Rcv’ button has been moved to the right end of the top toolbar.
If there are unsent messages, then ‘Unsent’ followed by the number of unsent messages will be displayed to the right of the ‘Send/Rcv’ button. This additional ‘Unsent’ count will not be displayed when there no messages waiting to be sent.
This new ‘Unsent’ label is for information only. Unlike the ‘Unsent’ count in the bottom toolbar, it cannot be used to show the unsent messages in the Message Viewer.
61580: [CLRCON] Enable CLRCON contents to be emailed
ENOM now supports forwarding CLRCON (CCC, HCC and ECC) messages via email in HTML format. The HTML format for these messages can also be generated and saved to a folder.
61222: Email notification for pending user expiry
ENOM will now send notification emails if an ENOM user is due to expire within 14 days, or has expired.
This is enabled from Maintenance > System > Email as part of the ‘ENOM System Notifications’ setting.
62611: [Message Viewer] Highlight profiled v5 BCD in Message Viewer
v5.1 Edigas XML BCD (BIDDOC) messages will now be highlighted correctly in the Message Viewer when they contain a profiled flow.
61875: [External Nominations] Make default create date consistent with Available Message default create date
Externally Nominated Data, when created from ‘Create New’, will now default to tomorrow’s gas day.
61737: [Balancing UI] Align Balance Detail totals
On the ‘Balance Detail’ screen, the column totals and row totals now line up with their respective values.
38265: [Messages Boxes] Prevent errors when adding Message Boxes with multiple instances
ENOM now correctly synchronises Message Box configuration changes across all open instances of ENOM.
61325: Support v5.1 messages without an xmlns attribute
ENOM now supports decoding v5.1 Edigas XML messages with no namespace. This is needed for messages received from GRTgaz.
60570: Fluxys IMBNOT and LIMITS messages from Balansys SA
Imbalance messages will continue to work when the balancing role for the BeLux market area passes from Fluxys Belgium to Balansys SA.
61544: [Compare Messages UI] User should be able to choose whether daily or hourly view is default
A system setting has been added (Maintenance > System) to choose whether the Compare Messages screen defaults to show daily values or hourly values.
61406: [Compare Messages UI] Ignored ‘Confirmed’ hourly values are not greyed out
If a whole row is ignored in the Matching > Compare Messages screen, then the hourly values section for that row will now also be displayed as ignored. Additionally, if all rows in the Matching > Compare Messages screen are ignored, then the row in the Matching screen will now be ignored as well.
61496: [Compare Messages UI] Column headers and numbers not displayed in full
A bug has been fixed in Matching > Compare Messages, where the columns were sometimes too small to read the values, when changing the messages to compare.
61497: [STOLIMITS] Storage LIMITS isn’t displayed alphabetically in Message Type list
ENOM will now display ‘STOLIMITS’ in the correct place in alphabetical lists.
53732: [Fix] ‘Notify when messages sent’ notification causing ENOM to freeze
A change has been made that stops the ‘Notify when’ options in File > Local Settings from blocking the background processes (e.g. sending and receiving messages) that ENOM runs.
61674: [Bulk Operations] Reprocess M&B results ‘only latest’ doesn’t use the latest
Fixed a bug in Message > Bulk Operations which meant that the ‘Only Latest’ checkbox had no effect on the ‘Re-Process Matching and Balancing Results’ option. Regardless if ‘Only Latest’ was selected, all messages for the selected period would be reprocessed. If ‘Only Latest’ is ticked now, it will only reprocess the latest messages.
61015: Only Latest doesn’t differentiate between outgoing and incoming messages
Selecting ‘Only Latest’ on the Message Viewer now takes the recipients of the messages into consideration when there are both incoming and outgoing versions of the same message type.
60838: [M&B UI] Advanced Rules doesn’t sort by recipient or location correctly
A change has been made to Maintenance > Matching And Balancing so that the tabs in that screen now sort the columns correctly when rows are sorted by Location or Recipient.
61590: [APR UI] Quantities should be right aligned
Values in the ‘Quantity’ column for all APR messages (v4 XML, v4 EDI and v5.1 XML) now right align.
58650: v5.1 Edigas messages for TIGF
ENOM now supports v5.1 Edigas XML messages as used by TIGF. This includes v5.1 Edigas XML NOMINT (nomination), NOMRES (confirmation and interruption), ACKNOW (acknowledgement), LIMITS (storage limits) and ACCSIT (account position) messages.
60851: Support v5.8 DVGW ALOCAT
ENOM is now able to decode v5.8 DVGW ALOCAT (TDDA, TDPA, NDDA, TPA, TDA and NDA) messages.
60279: [UI] Matching to display up to 5 different statuses
Matching can now use up to 5 different statuses (case 59956). As a result, the ‘Compare Messages’ screen has been redesigned.
When opening the ‘Compare Messages’ screen, by default, only end of day values for all statuses (i.e. Nominated, Confirmed, Processed by Adjacent TSO, etc.) will be displayed. Mismatches will continue to be highlighted.
Double clicking a row, or selecting a row and clicking the ‘View Hourly’ button, will change the ‘Compare Messages’ screen to display the hourly profile for that row. An end of day total for the selected hourly profile is included.
When in the hourly view, any other shipper’s hourly values can be viewed by selecting the relevant shipper from the displayed list. Double clicking a shipper, or selecting a shipper and clicking the ‘View Daily’ button, will change the ‘Compare Messages’ screen to display daily values again.
59956: Matching to use up to 5 different statuses
When ENOM+ processes matching information it will now also take into account the status ‘Processed by TSO’ from confirmation messages.
In the ‘Compare Messages’ screen, up to five columns may now be shown. The number of columns will depend on the statuses received in the confirmation messages.
- The first column will always show ‘Nominated’ values.
- The second column will show the statuses ‘Scheduled’ or ‘Confirmed’. If both are received in a message, then ‘Scheduled’ will be displayed.
- The third column will show the statuses ‘Processed by Adjacent TSO’, ‘Accepted by Adjacent TSO’ or ‘Matched’. If a message contains more than one of these statuses, then only one will be used and in the following priority order (highest to lowest):
- ‘Processed by Adjacent TSO’
- ‘Accepted by Adjacent TSO’
- The fourth column will show the status ‘Nominated by Counterparty’.
- The fifth column will show the status ‘Processed by TSO’.
59865: Auto ignore ‘Processed by TSO’ matching rule
There is a new Auto Ignore ‘Rule Type’ for Matching called ‘Processed By TSO’. This can be configured from the ‘Maintenance’ > ‘Matching and Balancing’ > ‘Auto Ignore’ tab. When the rule is configured, Matching will ignore values in confirmation messages with the status ‘Processed By TSO’.
59381: Blank cell in Clearing Confirmation messages
Fixed a bug where some zeros were displayed as blank when viewing v4 XML CLRCON (CCC, ECC and HCC) messages.
57940: Support change of direction for v4 REQEST messages
ENOM now supports a change of direction within v4 XML REQEST (BDR, BWR and BWF) and v4 DVGW REQEST (BDR) messages.
57942: Support change of direction for v4 REQRES messages
ENOM now supports a change of direction within v4 XML REQRES (SDR and SWR) and v4 DVGW REQRES (SDR) messages.
59878: Unable to create RBAN or SBAN messages from new
A bug was introduced in v6.17.251 that prevented Edigas v5 Receiver’s Balancing Agreement Notice (RBAN) and Supplier’s Balancing Agreement Notice (SBAN) messages being created from new. This has been fixed.
57054: Improve performance of balancing screen when using SQL Server
In some situations the performance of the balancing screen was poor when running ENOM using Microsoft SQL Server. The SQL query used has been updated to retrieve the balancing data from the database more efficiently in such situations.
57934: Support direction in REQEST messages
ENOM now supports specifying Direction in v4 DVGW and v4 XML BDR, v4 XML BWR and v4 XML BWF messages.
Direction is an optional column that can be included in the message template from Maintenance > Available Messages or by using an optional ‘direction’ attribute on the input ENOM XML.
The ‘direction’ attribute has not been added to the output ENOM XML.
When opening a REQEST message in ENOM, if there are zeroes on any row, then the ‘Direction’ column will be displayed.
57937: Support direction in REQRES messages
ENOM now supports specifying Direction in v4 DVGW SDR, v4 XML SDR and v4 XML SWR messages.
Direction is an optional column that can be included in the message template from Maintenance > Available Messages or by using an optional ‘direction’ attribute on the input ENOM XML.
The ‘direction’ attribute has not been added to the output ENOM XML.
When opening a REQRES message in ENOM, if there are zeroes on any row, then the ‘Direction’ column will be displayed.
56270: v5 Edigas messages for GRTgaz
ENOM now supports v5.1 Edigas XML NOMINT (nomination) and NOMRES (confirmation) messages as used by GRTgaz.
58541: Location encoding overrides do not work with shipper display aliases
ENOM now behaves correctly if an Encoding Override is configured using a Shipper Display Alias.
58663: NOGAT NOGO messages no longer decode
If using ENOM v6.15.050, v6.16.025 or v6.17.251, NOGAT messages could not be read. This has been fixed.
57650: [M&B Processing] Threading issue causes ENOM background processes to stop.
Fixed a bug that could stop Matching and Balancing processing.
58896: Automatic login not always suppressed by holding ‘Ctrl’ key
Under some circumstances ENOM did not detect that the ‘Ctrl’ key was pressed when logging in, meaning that automatic login could not be suppressed. This has been fixed.
56528: Support v5 Edigas messages for Enagas
ENOM now supports Enagas specific v5.1 Edigas XML messages. Daily, weekly, monthly and quarterly nominations can be created, which can then be manually uploaded to the Enagas SL-ATR system.
Please note that Enagas do not support Edigas for all types of nominations.
58283: [Message UI] New values incorrectly populated with zeros when extending monthly message period
When changing the period for v4 XML AVAILY (SMA, SQA) messages to include months with a greater number of days, the newly-added periods defaulted to a value of ‘0’. This has been changed so these now default to use the value that was previously last in the message, consistent with v3 EDI and v4 XML NOMINT (SMT) messages.
58140: [Message UI] Unit combo box position is inconsistent
The ‘Unit’ drop down box was previously on the left-hand side of the message for v3 EDI and v4 XML NOMINT (SWT, SMT) messages, and for v3 WSN messages. This has now been moved to the right-hand side to be consistent with other messages.
57408: [Message UI] Capacity Type column appears when it shouldn’t
In some circumstances, ENOM would incorrectly display a ‘Capacity Type’ column in Edigas v5 NOMINT (SDT) messages. This has been removed.
39481: Display a warning if a message is sent with a blank shipper code
ENOM now displays a warning if there is no reference data at all for a nomination row (i.e. Shipper, Capacity Type or Direction columns) in a NOMINT (SDT or CDT) message.
56066: Support v2.1a APERAK messages from NCGVHP
ENOM now supports v2.1a BDEW APERAK messages as used by NCGVHP.
56036: [M&B] Improve speed of balancing screen
Changes have been made to improve the performance of the balancing screen.
56121: Support SQL Server 2014
ENOM can now be used with SQL Server 2014 using SQL Server native client version SQLNCLI11.1.
56389: Acknowledgement messages may refer to a duplicated NOMINT
When an acknowledgement (ACKNOW, DELCON, APERAK, MOGAPP, NOGAPP and CONTRL) message was responding to multiple messages with the same identification, only the first such message was updated. This has been fixed. This bug was introduced in ENOM version 6.16.025 during the changes made for case 55654 (update database structure for acknowledgement messages).
56033: [UI] REQEST, REQRES and AVAILY messages created from new always have decimal places
ENOM will now correctly display the number of decimal places configured for the unit used in the message, when creating DVGW REQEST (BDR) messages; v4 XML REQEST (BDR, BWF and BWR) messages; DVGW REQRES (SDR) messages; v4 XML REQRES (SDR and SWR) messages and v4 XML AVAILY (SDA, SWA, SMA and SQA) messages.
54957: Support Oracle 12c
ENOM can now be used with Oracle 12.1c
55582: Support v5.5 DVGW IMBNOT messages
ENOM is now able to decode v5.5 DVGW IMBNOT messages.
55577: Support v5.7 DVGW ALOCAT messages
ENOM is now able to decode v5.7 DVGW ALOCAT (TDDA, TDPA, NDDA, TPA, TDA and NDA) messages.
55708: Support v4.5 DVGW CHACAP messages
ENOM is now able to decode v4.5 DVGW CHACAP (CHACAP and CHACAPR) messages.
55243: Support v4 IMBNOT messages from Fluxys without no incentive limits
From 1st October 2015, Edigas v4 XML and Edigas v4 EDI IMBNOT messages sent by Fluxys will no longer have the no incentive limits (upper and lower) present. ENOM will now decode and display these changed IMBNOT messages.
55244: Support v5 LIMITS messages from Fluxys without no incentive limits
From 1st October 2015, Edigas v5 XML LIMITS messages sent by Fluxys will no longer have the no incentive limits (upper and lower) present. ENOM will now decode and display these changed LIMITS messages.
55699: Support v4.6 DVGW NOMRES messages
ENOM is now able to decode v4.6 DVGW NOMRES (TDT, TMN, HCN and HDT) messages.
55611: Encode v4.5 DVGW 55G NOMINT (CDT) messages
ENOM is now able to create v4.5 DVGW NOMINT (CDT) messages.
56063: [DVGW NOMINT] Contract ref can be filled out and sent
Previously for v4.4 DVGW NOMINT (CDT) messages, an available message could be set up with a message format that allowed a contract ref, if it was then changed to be a message format ‘DVGW v4.4 (EDI)’ the previous contract ref would remain but be greyed out. The greyed out contract ref would then be used on the message.
This has been corrected as contract refs are not allowed on DVGW NOMINT messages.
55654: Update database structure for acknowledgement messages
In some circumstances, ENOM would fail to associate an acknowledgement (ACKNOW, DELCON, APERAK, MOGAPP, NOGAPP or CONTRL) message with the message that it was responding to. The way ENOM stores information about acknowledgement messages has been changed in an attempt to avoid such issues.
53880: Allow Recipient Default Hour Adjustment to have a different value from a specific time
ENOM now has an option to set an additional ‘Default Hour Adjustment’ on the ‘Maintenance’ > ‘Recipients’ screen. This enables you to configure a new default adjustment to take effect from a specific UTC time. When enabled, times for this recipient after the specified UTC time will use the new default adjustment instead of the old default or any location overrides. This optional configuration has been designed to support the change to the UK gas day.
54271: [NOMRES] Decode 16G as 17G for NOMRES messages from NCGVHP
ENOM is now able to decode a status of 16G as ‘Nominated By Shipper’ in Edigas v4 XML, Edigas v4 EDI and DVGW NOMRES (TDT, TMN, HDT and HCN) messages. This is only supported in messages from NGCVHP. 16G usually means ‘Confirmed’, but NCGVHP are using it to confirm the values nominated by the shipper.
54767: [NOMRES] Support ZPC (total output) decomposition quantity (capacity type)
ENOM is now able to decode the Decomposition (Capacity Type) code ‘ZPC’ as ‘Total Output’ in Edigas v4 XML NOMRES (TDT) messages. This is required for Corrib messages.
45608: [Oracle] Reduce number of simultaneous open cursors used by ENOM
When using ENOM with an Oracle database, in some circumstances the client would be disconnected with the error “ORA-01000: maximum open cursors exceeded”. ENOM has been updated to retain fewer open cursors in an attempt to avoid such issues.
53681: Increase detail in ENOM log files
More detail has been added to the ENOM log files concerning the referencing of acknowledgment messages.
53735: [Message UI] Auto-populate Internal Shipper column when resending messages
When resending v3 and higher NOMINT messages (CDT and SDT only), if the message contains a single, unique Internal Shipper, any new rows added will now contain the same Internal Shipper value by default.
53710: [Message Viewer] Display Internal Shipper for NOMINT and NOMRES messages
ENOM now includes an ‘Internal Shipper’ column in the Message Viewer, populated for NOMINT (SDT and CDT) and NOMRES (HDT, HCN, TMN and TDT) messages (v3 and higher). This is also used when determining which messages to display when the ‘Only Latest’ option is selected.
37062: [Message Boxes UI] Port numbers do not save correctly when containing a thousand separator
Fixed a bug in ‘Maintenance’ > ‘Message Boxes’ where ENOM saved port numbers with a thousand separator in the database. The port number will no longer display thousand separators.
51745: [ALOCAT] Status code “10G” should translate as “Deemed” on non-DVGW allocation messages
For all non-DVGW allocation messages, the status code 10G is now translated as “Deemed”; DVGW allocation messages will continue to translate 10G as “Replacement Value”. This affects both the display of the message in ENOM and the output ENOM XML.
52685: Support encoding version 4.4 DVGW NOMINT (CDT) messages
ENOM is now able to create v4.4 DVGW NOMINT (CDT) messages.
33055: [M&B] Allow balances to be configured by internal shipper
ENOM can now be configured to separate balances by internal shipper. This can be set up in ‘Maintenance’ > ‘Matching And Balancing’ > ‘Advanced Rules’ (previously ‘Advanced Matching Rules’). If such a rule is configured then internal shippers will be considered when determining the latest messages for the balance.
52455: Support receiving DELCONs for sent MOGAPPs
ENOM now supports receiving a DELCON message for a sent Maersk MOGAPP message.
43970: v5.1 Edigas messages for Fluxys
ENOM now supports the v5.1 Edigas XML messages required to operate as a shipper or an exchange operator in the Fluxys network - this includes Fluxys, Huberator, Fluxys LNG and Fluxys Storage.
ENOM can create:
- NOMINT - SDT (Shipper’s Daily Transit)
- BIDDOC - BCD (Bid Confirmation Document)
ENOM can decode:
- ACCSIT - APR (Account Position Report) and IMBNOT (Imbalance Notice)
- ACKNOW (Message Acknowledgement)
- ALOCAT - TPA (TSO’s Provisional Allocation)
- LIMITS (Imbalance Limits)
- NOMRES - TDT (TSO’s Daily Transit)
- PUBLIC (Publication Document)
51168: Support additional reason codes for ACKNOW messages
All possible reason codes from the Edigas code list are now supported for both the new v5.1 ACKNOW and the previously supported v5A ACKNOW messages. The reason codes below now display as “Remarks” in the Ack column of the Message Viewer; previously they showed as “Rejected”.
- 04G (Received After Deadline)
- 11G (Message Delayed)
- 36G (No Match, Counterparty Prevailed)
- 37G (Reduced Nominated Quantity)
- 63G (No Counterparty Nomination Received)
- 64G (Mismatch)
- 71G (Volume Prearranged)
- 72G (Volume Post-arranged)
- 73G (Mismatched and Volume Post-arranged)
- 74G (Damping Incorrect, Mismatched and Volume Post rearranged
- 82G (Contractually Binding)
- 83G (Contractually Binding Quantities Maintained)
- 84G (Mismatch In A Linked Nomination)
51630: [Message UI] Use the time zone adjustment of the ‘From’ Recipient when displaying IMBNOT/IMBNOTR messages in HTML in all instances
IMBNOT and IMBNOTR messages for 23 and 25 hour days were not always displaying correctly when viewed in the UI in HTML. This has now been fixed so that the time zone adjustment of the ‘From’ Recipient is always used.
52716: [UI] Message Properties does not resize correctly
The Message Properties screen now scales correctly when opened from the Message Viewer.
50783: Support version 4.5 DVGW NOMRES messages
ENOM is now able to decode v4.5 DVGW NOMRES (TDT, TMN, HCN and HDT) messages.
51232: [Locations UI] Prevent deleting Locations from causing an error
A bug has been fixed that caused an error when attempting to delete a Location, if a Custom Balance existed with Location set to <ALL>. This bug was introduced in ENOM v6.09.015.
51252: [Message UI] Use the time zone adjustment of the ‘From’ Recipient when displaying IMBNOT messages in HTML
IMBNOT messages that are displayed in the UI using HTML will now correctly use the time zone adjustment of the ‘From’ Recipient.
46004: [XML Log] Include line breaks in XML Log file
The XML Log file now contains line break characters between each line. This did happen previously, but had been broken in ENOM v6.00.48.
46017: [XML Interface] Reject BIDDOC messages with invalid lead times
Invalid lead times are now rejected when creating a BIDDOC message (BOD or RBD) via the ENOM XML interface.
47417: [Message Viewer UI] Prevent Message Viewer incorrectly showing messages as “Queued to be forwarded”
The Advanced tab on the Message Viewer screen now correctly shows “Queued to be forwarded” in the Forward Report column when appropriate.
49540: Send v4 XML REQRES messages as Release 2
Edigas v4 XML REQRES (SDR and SWR) messages are now encoded by ENOM with Release=”2”.
49866: [Quarterly AVAILY] Support 3-month AVAILY messages
Edigas v4 XML 3-month AVAILY (Seller’s Quarterly Availability) messages can now be viewed and created in ENOM.
48958: [Maersk] Support MOGO05 (Nomination Potential) messages - decode only
ENOM now supports receiving MOGO05 Nomination Potential messages from Maersk. It is not possible to create these messages. This feature is only enabled for customers with an appropriate licence.
48960: [Maersk] Support MOGO09 (Daily Allocation) messages - decode only
ENOM now supports receiving MOGO09 Daily Allocation messages from Maersk. It is not possible to create these messages. This feature is only enabled for customers with an appropriate licence.
48972: [Maersk] Support MOGO13 (Monthly Gas Export) messages - decode only
ENOM now supports receiving MOGO13 Monthly Gas Export messages from Maersk. It is not possible to create these messages. This feature is only enabled for customers with an appropriate licence.
39520: [Message Viewer] Disable ‘Hide Acknowledgments’ check box if a ‘Message Type’ is selected
The ‘Hide Acknowledgments’ checkbox on the Message Viewer will be disabled if a specific ‘Message Type’ filter is selected. If the ‘Message Type’ is set to <ALL>, then the user has the choice to either hide or show acknowledgments.
41441: [Bulk Operations] Fix issue with ‘Re-Process Matching and Balancing Results’ not deleting old matching results
If you add a new Advanced Matching Rule and select ‘Re-Process Matching and Balancing Results’ from ‘Message’ > ‘Bulk Operations’, ENOM now deletes all old matching results in addition to re-calculating the new results.
39718: [Bulk Operations] Improve progress bar display
The progress bar on the ‘Message’ > ‘Bulk Operations’ screen is now indicative of the percentage completed.
49510: [MS Access] Prevent database upgrade failure when upgrading from ENOM v5.18.68 or earlier
A bug has been fixed that caused an MS Access database upgrade to fail if you were upgrading from ENOM v5.18.68 (Database version 2.005) or earlier. This bug was introduced in ENOM v6.07.408.
48193: Support the non-decomposed value in Corrib NOMRES messages - decode only
ENOM is now able to decode the non-decomposed value (i.e. the value without a Capacity Type) as a new Capacity Type ‘Implied Rate’ in Edigas v4 XML NOMRES (TDT and TMN) messages. This is only supported in messages associated with Corrib.
47840: Support multiple units in incoming NOMRES messages - decode only
ENOM is now able to decode daily Edigas v4 XML NOMRES (TDT, TMN, HCN and HDT) messages that contain hourly values with multiple units. It is not possible to create these messages with multiple units.
45555: Support additional end user category in BALDOC and BALCON messages
ENOM now supports the end user category ‘GMN’ (Net gas losses) in Edigas XML BALDOC (RBAN, SBAN) and BALCON (RBAC, SBAC) messages.
33732: Make v4 XML TIN messages respond with the opposite direction and swapped shipper codes
When the ‘Respond’ button on an Edigas v4 XML DELORD message (TCN) is selected to create an Edigas v4 XML DELRES (TIN) message, the sign will now be reversed. Additionally the shipper and internal shipper codes will be swapped.
47990: Prevent DELCON messages throwing an error if decoded before referenced message
ENOM will no longer cause an error to display when decoding a DELCON message if the message it references is not yet in the database.
36179: [Message Boxes UI] Change ‘Box Enabled’ label to ‘Use FTP Settings’
The ‘Box Enabled’ label on the ‘Maintenance’ > ‘Message boxes’ screen has been renamed to ‘Use FTP Settings’. This better describes the functionality.
47834: Support additional Decomposition (Capacity Type) codes in Corrib NOMRES messages - decode only
ENOM is now able to decode additional non-Edigas-standard Decomposition (Capacity Type) codes in Edigas v4 XML NOMRES (TDT) messages. These additional codes are only supported in messages associated with Corrib.
47631: Support additional Contractual Offtake Type codes in Corrib AVAILY messages - decode only
ENOM is now able to decode additional non-Edigas-standard Contractual Offtake Type codes in Edigas v4 XML AVAILY (SDA, SWA and SMA) messages. These additional codes are only supported in messages associated with Corrib.
47634: Support multiple units in incoming AVAILY messages - decode only
ENOM is now able to decode Edigas v4 XML AVAILY (SDA, SWA and SMA) messages that contain daily Contractual Offtake Possibility values with multiple units. It is not possible to create these messages with multiple units.
48066: Support multiple units in incoming ALOCAT messages - decode only
ENOM is now able to decode Edigas v4 XML ALOCAT messages of type 96G (TDDA and TDA) that contain daily values with multiple units. It is not possible to create these messages with multiple units.
47781: Support v4 XML monthly NOMINT messages: Shipper’s Monthly Transit Forecast (SMT)
ENOM is now able to encode and decode v4 XML monthly NOMINT messages. These are called Shipper’s Monthly Transit Forecast (SMT) messages.
48395: [Message UI] Use the Decimal Places setting of the appropriate Unit when displaying ALOCAT messages in HTML
ALOCAT (TDA, TDDA, TPA and TDPA) messages that are displayed in the UI using HTML now correctly display values with the number of decimal places specified by the appropriate Unit, configured in the ‘Maintenance’ > ‘Units’ screen.
48293: [Message UI] Remove the Totals row from the Contractual Offtake Possibility sections of AVAILY messages
The Totals row has been removed from the Contractual Offtake Possibility sections of Edigas v4 XML AVAILY (SDA, SWA and SMA) messages.
47369: Support version 4.4 DVGW CHACAP - Changed Capacity Notice
ENOM is now able to decode v4.4 DVGW CHACAP Changed Capacity Notices.
47370: Support version 4.4 DVGW CHACAP - Renomination Restrictions
ENOM is now able to decode v4.4 DVGW CHACAP Renomination Restrictions messages.
46166: Fix the display of Release Notes in ENOM
ENOM will now display the release notes in ‘Help’ > ‘Current Version Release Notes’ and ‘Help’ > ‘Latest Version Release Notes’. This stopped working in version 6.06.017.
35385: [Message UI] Extend shipper display aliases to REQEST/REQRES messages
Shipper Display Aliases configured in the ‘Maintenance’ > ‘Shipper Codes’ screen will now be used in REQEST and REQRES Messages.
45057: [Message UI] Combine Decode Warning dialogs
When a Decode Failure occurs, ENOM will no longer display two separate dialogs. Instead, a single Warning dialog will now be displayed which contains the Decode Failure reason.
44888: [Message Viewer] Display the entire name of Locations in the Message Viewer > Externally Nominated Tab drop down
It will now always be possible to view the entire name of a Location in the ‘Location’ filter on the ‘Externally Nominated’ tab of the Message Viewer. While selecting, the option will always be long enough to show the entire name. Once selected, the drop down box will resize to fit the entire name.
If, as a result, it is not possible to view all the filter options and the ‘View’ button, then a scroll bar will appear; allowing use of the screen at low resolutions.
27014: [Balance Detail UI] Fix reference columns on Balance Detail screen
Changes have been made to how the information on the ‘Balance Detail’ screen is displayed.
When ‘Location View’ is selected (default option):
- The ‘Location’, ‘Nom Type’, ‘From/To’, ‘ENOM Shipper’ and ‘Contract Ref’ columns will remain fixed and visible when scrolling the rest of the columns.
When ‘Shipper View’ is selected:
- The ‘Location’, ‘Nom Type’, ‘From/To’, ‘ENOM Shipper’, ‘Contract Ref’ and ‘Shipper/Alias’ columns will remain fixed and visible when scrolling the rest of the columns.
44926: [Balance Detail UI] Prevent unexpected error when changing to Location View
In some situations an error was displayed when changing from the Shipper View to the Location View on the Balance Detail screen. This error will no longer occur.
44552: [Message Viewer] Prevent ACKNOW code 03G being incorrectly shown as ‘Rejected’
ENOM will now correctly interpret Edigas v5 ACKNOW messages with reason code 03G, meaning ‘Processed After Operator Validation’, as having status “Accepted”. “Accepted” will now also display in the ‘Ack’ column for the message acknowledged by the ACKNOW in the Message Viewer.
43174: [Email Notifications] Allow a semicolon at the end of a list of email addresses
If there is a semicolon (;) at the end of a list of email addresses in the ‘ENOM System Notifications’ > ‘Email Address’ field on the ‘Maintenance’ > ‘System’ > ‘Email’ tab, then ENOM will no longer prevent emails from being sent.
44887: [Message Viewer] Display the entire name of Locations and Contract References in the Message Viewer drop down
It will now always be possible to view the entire name of a Location or Contract Reference in the ‘Location’ and ‘Ref’ filters on the Message Viewer. While selecting, the options will always be long enough to show the entire name. Once selected, the drop down box will resize to fit the entire name.
If, as a result, it is not possible to view all the filter options and the ‘View’ button, then a scroll bar will appear; allowing use of the screen at low resolutions.
The ‘Hide Acknowledgment Messages’ check box has been renamed to be ‘Hide Acknowledgments’.
32235: [Message UI] Display the entire name of Locations when adding them to messages
When selecting a Location to add to a message, the length of the display has increased in order to display the entire name of the Location.
42991: [Message Encoding] Correct Edigas v4 XML AVAILY and REQEST element order
Edigas v4 XML AVAILY and REQEST messages will now respect the element order defined in the Edigas specifications.
43324: [Locations UI] Prevent duplicate locations from causing a message decode error
Messages will now open if they include an EIC, DVGW or EAN location code that has been duplicated in the ‘Maintenance’ > ‘Locations’ screen. The ability to configure such duplicate location codes may be removed in a later release.
44295: [Logging] Restore deleting of old logs
When attempting to write to the current log file, ENOM will now delete other log files that are more than 5 days old.
30543: Implement version 4.2 DVGW REQEST messages
ENOM is now able to encode and decode v4.2 DVGW REQEST messages.
43348: Implement version 4.2 DVGW REQRES messages
ENOM is now able to encode and decode v4.2 DVGW REQRES messages.
43602: [Balancing UI] Correct refresh behaviour of grid after adding Balance
After adding a new Balance, ENOM will now open the correct Balance Detail when you double click on a row in the Balancing Screen.
43936: Improve error on XML Log when duplicate shippers are used
The error message displayed in the XML Log when duplicate shippers are used has been improved.
43324: [Message UI] Messages containing a location configured multiple times will no longer decode
When trying to open a message that contains a location with a code that has been entered more than once into the ‘Maintenance’ > ‘Locations’ screen, the message will not be decoded.
An error will be displayed until the duplicate code is removed from the ENOM configuration.
38785: [Logs] Improve error reporting in XML Logs
Improvements have been made to the errors displayed in the XML Log.
- The error displayed when a Message Rule tries to write a file to an inaccessible location.
- The error displayed when processing ENOM XML, where ENOM does not support the specified message version and format.
39714: [Logs] Produce logs when messages are written to the Unresolved or Trash folder
ENOM will now produce a log file for each message that is put into the Unresolved or Trash folder. Unresolved logs will contain the same text as the decode log in the user interface. Trash logs will contain information explaining why the file is not a valid message.
40061: [ENOM XML] Remove blank statuses from ENOM XML for Edigas v4 PROCON messages
The ENOM XML produced for Edigas v4 PROCON messages will no longer include blank ‘status’ attributes. Instead the ‘status’ attribute will be absent if this information is not included in the message.
43066: [ENOM XML] Correctly set the doc_type attribute of Edigas v4 CONTRL messages
The ENOM XML for Edigas v4 CONTRL messages will now have the doc_type attribute set to the value “CONTRL”.
40732: [ENOM XML] Treat missing days or hours in ENOM XML for Edigas v4 ALOCAT messages as ‘0’ values
If ENOM receives ENOM XML to create an Edigas v4 ALOCAT message, any days or hours without values within the message period will be treated as ‘0’ values.
42811: [HTML & UI] Allow correct interpretation of Reconciliation Notices for Edigas v4 (EDI) IMBNOT messages
Edigas v4 (EDI) IMBNOT messages with Type 16G (Reconciliation Notice) will now be displayed as ‘(IMBNOTR) Reconciliation Notice’ messages. This affects the HTML generated from these messages.
Note: The attribute ‘reconciliation_notice=”true”’ already existed in the ENOM XML for these messages. The ENOM XML has therefore not changed.
40108: [Message Boxes UI] Prevent fatal crash from occurring when using inaccessible network path on MS Access
When using an MS Access database, ENOM will no longer crash when attempting to create a folder for a Message Box when the network location specified is not accessible. ENOM did not experience this issue with a SQL Server or Oracle database.
40111: [Message Boxes UI] Allow Message Boxes to be deleted
ENOM will no longer display an error when attempting to delete an inactive Message Box from the ‘Maintenance’ > ‘Message Boxes’ screen.
40114: [M&B Config UI] Allow Balances to be deleted
ENOM will no longer display an error when attempting to delete a Balance from the ‘Maintenance’ > ‘Matching and Balancing’ > ‘Balances’ tab.
43212: [Message Rules UI] Prevent error being displayed when For/Except rows are deleted and saved in the Message Rules screen
ENOM will no longer display an error when rows in the ‘For’ and ‘Except’ screens of ‘Maintenance’ > ‘Message Rules’ are deleted then saved.
36718: [Licence] Prevent users saving an invalid licence
ENOM will no longer allow users to save an invalid licence.
40169: [Viewer UI] Prevent Edigas v3 BWF messages displaying as Edigas v3 BWR messages
ENOM will no longer incorrectly display Edigas v3 BWF messages as Edigas v3 BWR messages.
40003: [Printing] Prevent ‘Out of Memory’ exception for Edigas v4 SMA messages
ENOM will no longer display an ‘Out of Memory’ exception when printing Edigas v4 SMA messages.
39934: [Message UI] Prevent error when sending/resending Edigas v3 REQEST messages with blank values
ENOM will no longer display an error when trying to send an Edigas v3 REQEST message from the XML Queue or when trying to resend one, if a row contains blank values. Blank values will be sent as ‘0’.
42699: [Message UI] Prevent Edigas v4 AVAILY and REQEST messages from resending 25 hour day messages incorrectly
Edigas v4 AVAILY and REQEST messages no longer change the values of the 25th hour of a 25 hour day to be the same as the 24th hour, when clicking the ‘Resend’ button.
43189: [Message UI] Ensure all messages use the ENOM standard calculation for the default date when resending
When resending Edigas v2 DWM, RWM, SWA, TRN, TWM or TWR messages or Edigas v3 BWOF, TMC or TWM messages, ENOM will now use the standard calculation for when to resend the message for, rather than defaulting to the date of the current message.
17711: [Message UI] Prevent bugs when resending Edigas v2 BWOF messages for 23 or 25 hour day
Edigas v2 BWOF messages no longer clear the grid when resending 23 hour day messages or display an error when resending 25 hour day messages.
43167: [Message UI] Prevent monthly messages from experiencing an error in February when using Italian Windows regional settings
During February, in years that do not begin on a Tuesday:
- ENOM will no longer display an error when opening Edigas v2 SMT messages from the XML Queue.
- ENOM will no longer display an error when resending any monthly message.
During February in years that do begin on a Tuesday:
- The date will now correctly default to March when resending any monthly message.
These issues only occurred when using Italian Windows regional settings.
ENOM did not experience these issues when using English, German or French Windows regional settings.
41155: [M&B Processing] Prevent ‘M&B Processor already exists’ error
ENOM should no longer throw the error: “Error processing M&B Data: M&B Processor already exists”.
In the case that the error still occurs, the error reporting behaviour has changed so that the errors will appear in the M&B Processing Log, along with further information about when they occurred, instead of appearing as an error pop up box.
41388: [IMBNOT] Interpret negative sign for DVGW IMBNOT messages
DVGW IMBNOT messages will now correctly interpret and display negative signs ‘-‘ for quantity values.
40426: Support OGE CHACAP messages
ENOM is now able to decode OGE CHACAP messages.
40585: CHACAP messages should show row totals
Row totals are now displayed for v4 CHACAP messages.
40570: Increase maximum shipper code length
ENOM will now allow Edigas shipper codes to be up to 50 characters in length.
39353: Support monthly AVAILY messages
Monthly AVAILY messages containing daily or hourly values can now be viewed and created in ENOM.
39355: Support hourly values in weekly AVAILY messages
Weekly AVAILY messages containing hourly values can now be viewed and created in ENOM.
39356: Support Contractual Offtake Possibility
ENOM now supports Contractual Offtake Possibility in v4 Edigas XML AVAILY and v4 Edigas XML REQEST messages.
39357: Support the sending of REQRES messages with ‘Fully Expanded’ hours
It is now possible to send REQRES messages that contain fully expanded hours, rather than grouping together consecutive hours that have the same value. This is configured on the ‘Maintenance’ > ‘Recipients’ screen > ‘Nomination Encoding’ tab by setting the ‘Hourly Values’ field to ‘Fully Expanded’.
39862: Support v5.6 DVGW ALOCAT messages
Version 5.6 DVGW ALOCAT messages are now supported.
33037: [Message Rules] Improvement to ‘fail to write file’ message
Error information will now be displayed in the XML Log if ENOM is unable to generate ENOM XML or HTML for a Message Rule. More information about why ENOM could not write the file, such as the Message Rule name and folder location, will also be included.
Further, a bug has been fixed so that now all error message text in the XML Log is displayed in red text, not just the first line.
35429: [GBIT] Change Portfolio Edigas ID title
In the ‘Message’ > ‘GTS Balancing Info’ screen, on the ‘Config’ tab, the ‘Portfolio Edigas ID’ field has been relabelled to ‘Portfolio Edigas ID (GTS Shipper Code)’.
34896: [Logs] Add X-axis scroll bar to Log screens
The Email Log, FTP Log and XML Log now have a horizontal scroll bar in order that longer messages can always be read.
39551: [Bulk Ops UI] Allow whole error message to be seen
When Exporting Messages or ENOM XML using the ‘Message’ > ‘Bulk Operations’ screen, there will now be a horizontal scroll bar on the progress screen in order that the entire message of every row can be read.
36262: [Notifications] Remove fax and text message functionality
It is no longer possible to have ENOM send faxes or text messages. The ‘Other Notifications’ tab on the ‘Maintenance’ > ‘System’ screen, containing the configuration previously set up for this, has been removed.
34663: [Message UI] Add total row for each status for NOMRES messages
NOMRES messages now have a status totals row. This row contains the total for all the values for that status across all Locations within the message.
35453: [Recipients] Improve warning when deleting a Recipient with Available Messages set up
If you try to delete a Recipient from the ‘Maintenance’ > ‘Recipients’ screen that has Available Messages configured for it in the ‘Maintenance’ > ‘Available Messages’ screen, then ENOM will now inform you that the relevant Available Messages will be deleted, and ask if you wish to continue.
37487: [UI] Rename the menu items for Release Notes
The menu items in the ‘Help’ menu have changed from ‘Release Notes’ to ‘Current Version Release Notes’ and from ‘Check for Upgrades’ to ‘Latest Version Release Notes’. The behaviour of these menu items has not changed.
33415: [Message Viewer UI] Fix ‘Expected’ Ack status functionality
The ‘Expect to receive an Acknowledgment’ functionality configured on the ‘Maintenance’ > ‘Recipients’ screen > ‘Acknowledgments’ tab has been fixed. Messages sent to such Recipients will now display ‘Expected’ in the Message Viewer if they haven’t received a corresponding Acknowledgment message.
34949: [M&B Reprocess] Only Reprocess Matching and Balancing data within selected period
If the ‘From Gas Day’ and the ‘To Gas Day’ in the ‘Message’ > ‘Bulk Operations’ screen are set to be the same value, then performing ‘Re-Process Matching and Balancing Results’ will now only reprocess that day’s data.
34717: [Licence expiry] Prevent email being sent if expiring licence has been updated by another ENOM
If you update your ENOM licence, without closing all your ENOMs, then those other ENOMs will no longer continue to send emails warning of pending licence expiry.
34876: [GBIT Expiry] Prevent email being sent when no certificate is specified
ENOM will no longer send a notification email warning about the expiration of the Certificate for the ‘Message’ > ‘GTS Balancing Info’ screen if the Certificate Name field on the ‘Config’ tab is blank.
36970: [Message Viewer UI] Standardise display across all tabs
The sizes of the ‘View’ button and the date picker have been made the same across the three tabs of the Message Viewer.
39169: [Message UI] Add Resend for today/tomorrow dialog to open windows list
The ‘Resend this message for…’ window that appears when you are selecting which day to Resend a message for, now appears in the open windows list under the ‘Window’ menu. This window will only appear if you have ‘Ask’ set as the value for ‘Resend Messages For’ on the ‘General’ tab of the ‘Maintenance’ > ‘System’ screen.
39232: [Units UI] Improve decimal places field validation
You can now only enter whole numbers into the ‘Decimal Places’ field on the ‘Maintenance’ > ‘Units’ screen. Thousand separators are also prohibited.
39618: [Message UI] Prevent non-contiguous cell pasting
ENOM now prevents the user from pasting into a non-contiguous cell selection. E.g. ENOM will throw a warning if you select one cell, select a second cell that is not adjacent to the first, and then try to paste into both of those cells.
39708: [Message UI] Prevent duplicate Combo Box values when pasting
Copying and pasting values into Combo Box columns will not paste the value as upper case if the Combo Box already contains the value being pasted, regardless of the case of the letters. This prevents duplicate values appearing in Combo Boxes differing only by case.
33749: [Viewer] Correct Message Name/Description labelling inconsistency
The field ‘Message Name’ and the column ‘Message Description’ on the Message Viewer and XML Queue have been renamed to be ‘Message Type’.
35500: [Units UI] Change title of Units screen
The title shown at the top of the ‘Maintenance’ > ‘Units’ screen has been changed from ‘Units Maintenance’ to ‘Units’.
35776: [Shipper Codes UI] Change title of Shipper screen
The title shown at the top of the ‘Maintenance’ > ‘Shipper Codes’ screen has been changed from ‘Shippers’ to ‘Shipper Codes’.
20131: Migrate the ENOM UI to VB.NET
The ENOM UI has been migrated from VB6 to VB.NET. All ENOM code not from third parties is now written in .NET languages.
36551: SQL Server 2012 Support
SQL Server 2012 and the SQL Server 2012 native client (SQLNCLI11.1) are now supported.
35598: [Balancing] Improve Performance of Balancing screen
The performance of the Balancing screen has been improved for SQL Server and Oracle databases.
31882: [Messages UI] Improve NOMRES messages open and close time
The time to open certain NOMRES messages has been improved.
18246: [XML Queue UI] - Enable multiselect of entries
It is now possible to select multiple entries in the XML Queue and then Read, Send or Delete them en masse. In order to prevent the unintentional selection of entries, ENOM will no longer automatically select an entry when the XML Queue opens or when a new item appears.
33762: [UI] Improve Error Messages when connecting to a missing database
The error message given when ENOM is unable to connect to the database is now more informative.
39221: [UI] Improve Error Messages when unable to create folder
The error message given when ENOM is unable to create a folder is now more informative.
35987: Ability to search for long strings in Combo and List Boxes
Text searching has been altered for some Combo and List Boxes. ENOM will now search for ‘WA’ if ‘W’ then ‘A’ is typed when an active Combo or List Box is opened.
34042: [Messages UI] Refactor how messages are printed
Dotted lines now appear at the edge of printed pages to indicate the continuation of a table.
37483: Allow all messages to be auto ignored in Matching And Balancing
A new ‘Maintenance’ > ‘Matching And Balancing’ > ‘Auto Ignore’ > ‘Rule Type’ has been implemented called “All Messages”. This allows all transit messages to be ignored even if they have a mismatching nomination or confirmation associated with them.
37187: [Message Rules] Prevent deleting of Location used by Message Rule
It is no longer possible to delete a Location that is being used in a Message Rule. If you try to delete such a Location then a warning will be displayed.
33794: [M&B Config UI] Matching And Balancing - implement sorting
It is now possible to sort the columns in the ‘Maintenance’ > ‘Matching And Balancing’ screen.
35945: [M&B Config UI] Change the ‘Close’ button behaviour when there are duplicate rows
Closing the ‘Maintenance’ > ‘Matching And Balancing’ screen, with duplicate rows present on any tab, will now open the ‘Save changes’ dialog box. The screen previously warned about duplicate rows prior to displaying the ‘Save changes’ dialog box.
38133: [M&B Config UI] Create an ‘Add Row’ button for Balance Properties
Rows are now added and removed from the Custom Balance grid of the ‘Maintenance’ > ‘Matching And Balancing’ > ‘Balances’ > ‘Balance Properties’ screen using the ‘Add Row’ and ‘Delete Row’ buttons.
38240: [M&B Config UI] Implement highlighting for Custom Balance rows
The whole Custom Balance row in the ‘Maintenance’ > ‘Matching And Balancing’ > ‘Balances’ > ‘Balance Properties’ screen will now be highlighted when any cell of that row is selected.
37756: [FTP Log] Prevent crashing when error thrown during FTP error reporting
ENOM should no longer crash if an error occurs while it is trying to report errors in the FTP Log.
36669: [XML Queue UI] Prevent Time or Unit of messages from being accidentally changed
ENOM no longer initially selects the time or the unit when viewing a message from the XML Queue. This means that it is no longer possible to accidentally change the time or unit of such messages with the mouse wheel when first viewing them.
38151: [M&B] Reprocessing Matching And Balancing results shouldn’t ignore externally nominated data
ENOM will now correctly reprocess Matching And Balancing data contained in External Nominations when performing ‘Reprocess Matching And Balancing Results’ on the Bulk Operations screen.
21142: [Modal Forms] Prevent ENOM crashing when Modal forms conflict
An error no longer occurs, and ENOM no longer crashes, when two forms which require immediate attention are open simultaneously. For example, if a warning popped up to indicate that a message had failed to send, while you were in the ‘Message Properties’ screen trying to select the folder to save a message to, then previously ENOM would crash.
35625: [Bulk Operations] Fix ‘Export Messages’ path bug
When using ‘Export Message Files’ on the Bulk Operations screen, ENOM no longer omits the final ‘' causing the path to be incorrect. For example, trying to export ‘SDT.edi’ to ‘C:\folder\subfolder’ will no longer export ‘subfolderSDT.edi’ to ‘C:\folder’.
38588: [UI] DateTimePicker locking up
The arrow buttons for date and time pickers on message forms should no longer become disabled. For example, using the left and right arrows on the keyboard should no longer disable them.
32696: [Messages UI] Prevent scrolling causing column misalignment
Using the horizontal scroll bar when viewing a message will no longer cause the columns to become misaligned with the column totals.
33948: [UI] Make Maintenance screens update automatically when Recipient or Location names are changed
Changing the name of a Recipient or a Location will now automatically update the ‘Maintenance’ > ‘Contracts’ and ‘Maintenance’ > ‘Shipper Codes’ screens if they are open. ENOM will similarly update any open tab of the ‘Maintenance’ > ‘Matching And Balancing’ screen, apart from the ‘Balances’ tab.
34891: [Bulk Ops] Clear Matching screen and Balancing screen when Reprocessing Matching And Balancing
If either the Matching screen or the Balancing screen are open, then they will clear when performing ‘Reprocess Matching And Balancing Results’ on the ‘Message’ > ‘Bulk Operations’ screen.
33796: [M&B Config UI] Advanced Matching Rules rows should be unique
Rows in the ‘Maintenance’ > ‘Matching And Balancing’ > ‘Advanced Matching Rules’ tab must now be unique.
33797: [M&B Config UI] Editing Combo Boxes should cause ‘Save changes’ dialog box to appear upon closing screen
Changing the value of a Combo Box in the ‘Maintenance’ > ‘Matching And Balancing’ screen and then closing the screen will now always show the ‘Save changes’ dialog box.
33121: [Units] Units Screen should remember its position
The ‘Maintenance’ > ‘Units’ screen now correctly remembers its previous position upon reopening.
34020: [Messages UI] Increase the width of drop down lists on message forms
Combo Box drop down options on message forms will now always be wide enough to fully display each item when creating a message.
33785: [M&B Config UI] Allow use of tab key to close Matching And Balancing screen
It is now possible to close the ‘Maintenance’ > ‘Matching And Balancing’ screen by tab selecting the ‘Close’ button and pressing the ‘Return’ key.
28232: [UI] Fix ‘Create’ button tooltip on Windows 7
The ‘Create’ button on the main screen will now display the ‘Create New’ tooltip in all operating systems.
39118: [Messages UI] Prevent column totals losing alignment when resizing
When resizing a message the column totals will no longer lose alignment with the columns above.
34817: [UI Compare Messages] Prevent buttons overlapping on resize
The minimum size of the Compare Messages screen no longer causes the buttons to overlap.
36513: [XML Queue] Retain selection when additional files are dropped in
When new entries appear in the XML Queue, the entry previously selected now remains selected.
20594: [Installation] Remove restart request when upgrading
ENOM will no longer ask you to restart your computer upon installation or when upgrading.
36855: [EnomData] Prevent ‘Cannot open any more tables’ error
ENOM no longer causes the Microsoft JET Database Engine Error “Cannot open any more tables” when editing Contracts in the ‘Maintenance’ > ‘Contracts’ screen.
37213: [Externally Nominated Data] Fix spelling mistake in warning when Externally Nominated Data has been deleted
The error message displayed when trying to view Externally Nominated Data that no longer exists has been corrected.
37121: [UI] Fix ‘System Info’ button in Windows 7
The ‘Help’ > ‘About’ > ‘System Info…’ button now works correctly in Windows 7.
36857: [Contracts] Prevent error when deleting Recipient of Contract
Deleting a Recipient that is used by a Contract, when the Contract screen is open, now correctly displays that said Contract has had its Recipient removed, rather than displaying the Database ID for the deleted Recipient.
37404: [Shipper Codes UI] Update Hub Code when Location is changed
ENOM now correctly updates the Hub Code in the ‘Maintenance’ > ‘Shipper Codes’ screen when the relevant Location is edited in the ‘Maintenance’ > ‘Locations’ screen.
37652: [Closing ENOM] Prevent ENOM from closing when invalid unsaved changes are made in Maintenance screens
When attempting to close the application, ENOM no longer continues to close if invalid changes have been entered but not yet saved in ‘Maintenance’ screens.
38099: [M&B Config UI] Select row after pressing ‘Add’
Pressing ‘Add’ in the ‘Matching And Balancing’ screen now causes the new row to be highlighted and the left most cell to be selected.
38161: [Messages UI] Prevent adding of special characters to newly created rows
It is no longer possible to enter the following characters into the left hand side of message grids: < > * & ^ % $ ? "
37841: [Messages UI] Prevent duplicate Capacity Type options
Duplicate options no longer appear in the ‘Capacity Type’ column of the ‘Priorities’ section of a NOMINT message when a ‘Capacity Type’ is added to the top grid.
37802: [Messages UI] Correct options for the Capacity Type column in Priorities grid
‘Priorities’ grids in NOMINT messages now offer the correct options for the ‘Capacity Type’ column.
37147: Fix ENOM XML display for APERAK messages from Gas Connect Austria
The ENOM XML of APERAK messages will now correctly display in the ‘Message Properties’ screen and will correctly save, even when the ‘ReasonText’ attribute contains character entities, e.g. ‘&quot;’
33783: [M&B Config UI] Improve Matching And Balancing tab order
The tab order on the ‘Maintenance’ > ‘Matching And Balancing’ screen has been improved.
39196: [M&B Config UI] Prevent error when entering non-numeric values into Journey Shrinkage
ENOM no longer throws an error when trying to enter a non-numeric value into the ‘Shrinkage’ column of the ‘Journey Shrinkage’ tab of the ‘Maintenance’ > ‘Matching And Balancing’ screen.
37642: [Messages UI] Prevent BDRv2 response error
When pressing ‘Respond’ on a v2 BDR message, ENOM will once again correctly create a v2 SDR.
37013: [Message UI] Remove unnecessary highlighting in TDT messages
When viewing TDT messages, Amounts or Shippers will no longer be highlighted.
38282: [Messages UI] Remove Resend button from NOGO messages
NOGAT Output messages (NOGO) no longer display the Resend button.
37781: [Available Messages UI] Improve behaviour when changing Message Type of an Available Message
Changing the Message Type of an Available Message now clears the configuration from the Advanced screen.
39128: [UI] Make input box titles consistent
The titles to the ‘Add New’ screens when adding items to the Maintenance screens have been made more consistent.
33318: NOMINT and NOMRES messages, important changes to ENOM XML interface
There have been some important changes made to the ENOM XML interface for the creation of v3 EDI, v4 EDI & v4 XML NOMINT messages and the creation of v3 EDI, v4 EDI & v4 XML NOMRES messages.
If you use the ENOM XML interface for the creation of messages of these types, then you are strongly advised to perform testing before installing on a live environment, to make sure that your ENOM is still correctly configured. In particular you should ensure that the ENOM XML you drop into ENOM is still accepted, and that the messages produced by ENOM are as expected.
Changes include, but are not limited to:
- The attributes ‘use_qualified_values’ and ‘always_input_output’ on <nomination> elements are now only accepted in ENOM XML that is used to create v3 EDI NOMINT messages. If they are so used on any other messages then the ENOM XML will be rejected. The relevant XSD files have been updated accordingly.
- Using the values ‘use_qualified_values = “false”’ and ‘always_input_output = “false”’ together on <nominations> elements in ENOM XML to create v4 EDI or v4 XML NOMINT messages, when creating v4 EDI or v4 XML NOMRES messages, is no longer accepted by ENOM.
- Where values are specified in the encoding attributes (‘use_qualified_values’ and ‘always_input_output’), ENOM will create messages using those values, as long as validation checks are passed. Previously it was possible for values to be specified and ENOM would send messages with different encoding than that specified.
- If there are conflicts within the ENOM XML, or between the ENOM XML and Encoding Overrides settings in ENOM, then the ENOM XML will be rejected.
Please also refer to release notes for case 34383 and case 34642.
34383: [Nomination Encoding] Rejecting certain direction combinations
When creating a v3 EDI, v4 EDI or v4 XML NOMINT message or a v3 EDI, v4 EDI or v4 XML NOMRES message:
- Rows whose values in the left hand columns are duplicated in another row, are no longer accepted.
- Rows whose left hand columns differ only by the value of the direction column, are only accepted if one row has the value ‘input’, the other row has the value ‘output’ and only if the Recipient’s ‘Default Encoding’ is either ‘Positive input and output’ or ‘Positive input or output’.
These new validations also affect these message types if the messages are created via ENOM XML.
34642: [Nomination Encoding] Conflict with Location Overrides should have warning
When creating a v3 EDI, v4 EDI or v4 XML NOMINT message or a v3 EDI, v4 EDI or v4 XML NOMRES message:
- If a row contains values that disagree with the ‘Entry/Exit’ settings of an ‘Encoding Override’ on the ‘Maintenance’ > ‘Recipients’ screen, then it will not be possible to send the message.
This also affects messages created via ENOM XML, if there is a conflict then the ENOM XML will be rejected.
34720: [UI Grids] Remove direction in all NOMINT and NOMRES messages if there is a conflict
When creating a v3 EDI, v4 EDI or v4 XML NOMINT message or a v3 EDI, v4 EDI or v4 XML NOMRES message:
- It is no longer possible to have values in the right hand grid that conflict with the value of the ‘Direction’ column in the same row of the left hand grid. e.g. If the value in the ‘Direction’ column of a row is ‘Output’ and a positive value is entered into the right hand columns of that row, then the value in the ‘Direction’ column of that row will become blank.
34731: [Message UI] UI encoding CDTv3 as OR error
ENOM only supports creating v3 CDTs if the default encoding of the ‘To’ Recipient on the ‘Maintenance’ > ‘Recipients’ screen is set to ‘Positive input and output’. It is no longer possible to create v3 CDT messages if the default encoding of the ‘To’ Recipient on the ‘Maintenance’ > ‘Recipients’ screen is not ‘Positive input and output’.
33498: [Nomination Encoding] ENOM XML direction encoding preserved in the UI
The ENOM XML structure is now more accurately displayed when viewing as a message from the XML Queue. For example, if ENOM XML is sent to ENOM with an input value of zero and an output value of zero for the same location and shipper, then when viewing the message from the XML Queue, ENOM will display two rows with the direction specified. Previously ENOM would merge these rows.
21709: “Matching” screen in ENOM+ now also uses “Processed By Adjacent TSO” values
When ENOM+ processes Matching information, it now takes into account all of the following statuses from Confirmation messages:
- ‘Scheduled’, ‘Confirmed’, ‘Processed by Adjacent TSO’, ‘Nominated by Counterparty’, ‘Accepted by Adjacent TSO’ and ‘Matched’.
For any particular Location, a maximum of two statuses are used for matching. A mismatch for either of these two statuses means that the Location is mismatched.
In the ‘Compare Messages’ screen, three columns may now be shown in each half of the screen, rather than always just ‘Nominated’ and ‘Confirmed’.
- The first column will always show ‘Nominated’ values.
- The second column will show the statuses ‘Scheduled’ or ‘Confirmed’. If both ‘Scheduled’ and ‘Confirmed’ are received in a message then ‘Scheduled’ will be displayed.
- The third column will show the statuses ‘Processed by Adjacent TSO’, ‘Nominated by Counterparty’, ‘Accepted by Adjacent TSO’ or ‘Matched’. If a message contains more than one of these statuses then only one will be used and in the following priority order (highest to lowest):
- ‘Processed by Adjacent TSO’
- ‘Nominated by Counterparty’
- ‘Accepted by Adjacent TSO’
If the additional statuses for the third column are not received in the message then only two columns will be displayed.
34952: [M&B] Auto ignore processed by adjacent TSO
There is a new Auto Ignore ‘Rule Type’ called ‘Processed By Adjacent TSO’. This can be configured on the ‘Maintenance’ > ‘Matching and Balancing’ > ‘Auto Ignore’ tab.
When the rule is active Matching ignores values with the status ‘Processed By Adjacent TSO’ in Confirmation messages. The Recipient, Location and (optionally) Shipper that this rule is applied to can be specified as per other Auto Ignore rules. This is required for confirmation messages from Gassco for any transactions.
35043: [Auto Ignore] Remove the All rule
It is no longer possible to set up an Auto Ignore rule of ‘Rule Type’ “All” in the ‘Maintenance’ > ‘Matching and Balancing’ > ‘Auto Ignore’ tab. Any rules already configured of this type will be replaced, by the database upgrade script, with three rules with the same configuration, except with Rule Types “Nomination”, “Zero Nomination” and “Confirmation” respectively.
35068: [DVGW ALOCAT] Support version 5.5
ENOM now supports the receiving of v5.5 DVGW ALOCAT messages.
35069: [DVGW IMBNOT] Support version 5.4
ENOM now supports the receiving of v5.4 DVGW IMBNOT messages.
32273: [UI] Message Matching renaming
The wording of the option ‘Message Matching’ on the ‘Message’ menu has been changed to ‘Matching’.
The ‘All Balance Summary’ screen has been renamed to ‘Balancing’.
The wording of the option ‘All Balance Summary’ on the ‘Message’ menu has been changed to ‘Balancing’.
33572: [UI] Recipients and Recipient Details naming
The ‘Recipient Details’ screen has been renamed to ‘Recipients’.
31746: “Unsent” in status bar corresponds to “Queued” in the Message Viewer drop down menu
The ‘Queued (All)’ option on the ‘Viewer’ screen has been renamed to ‘Unsent (All)’.
31106: [Message Boxes] Update browse button
The ‘…’ (browse) button for the ‘Maintenance’ > ‘Message Boxes’ screen now starts browsing from the path specified, even if it is a Network location.
32701: [DVGW ALOCAT] XBG message type is displayed with same ENOM message name as the X5G message type
DVGW ALOCAT messages with code XBG in their BGM segment now appear as “(NDA) Network Definitive Allocation Notice” and “(NDDA) Network Daily Definitive Allocation Notice” in the UI. This distinguishes them from “(TDA) TSO’s Definitive Allocation Notice” and “(TDDA) TSO’s Daily Definitive Allocation Notice”.
33830: [Recipient Details] Change default nomination encoding on creation
By default, new recipients now use ‘Positive input or output’ as their Default Encoding.
34933: [CHACAP UI] Direction is displayed as injection or withdrawal
The ‘Direction’ column now displays ‘Input’ instead of ‘Injection’ and ‘Output’ instead of ‘Withdrawal’ for (CHACAP) Changed Capacity Notice messages, in line with the values in the ENOM XML.
33087: [Notification and minimisation] The ‘Notify when messages are sent’ Notification causes issues when ENOM is minimised
The ‘Notify when messages are sent’ and ‘Notify when messages fail to send’ popup windows caused an issue when ENOM was minimised. ENOM would not maximise, and would steal focus from other applications when the warnings popped up. This issue has been resolved.
33652: Ungroup days in MOGO16 XSL
The HTML and ENOM XML produced from (MOGO16) Maersk Production Forecast messages no longer groups together identical values over consecutive days. Rather, the value for each day is always shown separately, even when it is the same as an adjacent day.
34536: [Oracle bug] In Oracle you can’t open Fluxys IMBNOTs
It is again possible to open IMBNOT messages from Fluxys on ENOMs connected to an Oracle database.
33736: [UI] +/- Quantity Delivered not supported for v4 messages error should link to recipient
The message informing users that v4 EDI & v4 XML NOMINT messages and v4 EDI & v4 XML NOMRES messages cannot be sent using ‘+/- Quantity delivered’ encoding has been made clearer.
33737: ‘+/- Quantity delivered’ not supported by v4 messages error can be bypassed by blank v4 message
It is no longer possible to send v4 EDI or v4 XML NOMINT messages from the UI which contain locations, but no shippers, when the ‘To’ Recipient is configured to have ‘Default Encoding’ of ‘+/- Quantity delivered’ on its ‘Maintenance’ > ‘Recipients’ > ‘Nomination Encoding’ tab.
31990: [Cannot find Recipient message] It isn’t clear enough how to get rid of it.
The warning that is shown when opening a message that does not have both its ‘To’ and ‘From’ recipient configured in the ‘Recipients’ screen has been made clearer.
34459: [XML Log] NDDA error with non-DVGW Default Message format set on Recipient could be improved
NDDA messages can only be created in version 5.4 DVGW format. The error message shown when a NDDA message is created from ENOM XML and the Recipient is not configured correctly in ENOM, is now more informative.
34457: [FTP Log] Unable to see entire error message
Some error messages in the XML Log have been changed to be on multiple lines. This ensures that the whole message can be read.
29580: [.NET migration] Move Units Maintenance form
The ‘Maintenance’ > ‘Units’ screen has been migrated to .NET. In doing this there have been various bug fixes and improvements made to this screen.
32378: [NOMINT messages] Duplicate input/output in direction column
When resending NOMINT messages that include the ‘Direction’ column, the drop-down list to select a new direction no longer contains duplicate entries.
33386: [M&B] Rows in balances that differ by internal shipper are classed as duplicates
Rows in a ‘Custom Balance’ in the ‘Maintenance’ > ‘Matching and Balancing’ > ‘Balances’ (tab) > ‘Balance Properties’ screen can now be configured such that they differ only by ‘Internal Shipper’.
31889: [M&B Processing] Auto popup window not populating ‘Unprocessed Messages’ list
The ‘M&B Processing’ window now correctly populates the ‘Unprocessed Messages’ section if the ‘File’ > ‘M&B Processing’ window is not open when an error during Matching and Balancing Processing occurs.
32259: [CEGH v3 NOMRES] Allow Z11 as a Reference Code Qualifier in RFF section
ENOM now accepts the Reference Code Qualifier ‘Z11’ in the RFF section of v3 NOMRES messages. You will no longer get a warning when viewing these messages. This affects messages received from CEGH.
34410: [v5 ACKNOW] Accepted reason codes
ENOM now correctly interprets the ‘ReasonCode’ ‘02G’ in v5 ACKNOW messages. 02G is interpreted as ‘Processed Automatically’. Any message that receives this response in an ACKNOW message will display as ‘Accepted’ in the ‘Message Viewer’.
33687: [M&B] Reprocessing messages loses data
Re-Processing Matching and Balancing Results using the ‘Message’ > ‘Bulk Operations’ screen no longer deletes the data for the Gas Day immediately after the ‘To Gas Day’ date.
33791: [M&B] Hour adjustment cannot be set to negative
It is now possible to set the ‘Hour Adjustment’ for ‘Matching and Balancing’ on the ‘Maintenance’ > ‘System’ > ‘General’ tab to a negative number.
34276: [Message Encoding] Lower case decode issue
ENOM now ignores the letter case (upper or lower) of Locations and Shippers when deciding if a row should be encoded using an Encoding Override from the ‘Maintenance’ > ‘Recipients’ > ‘Nomination Encoding’ tab of a Recipient.
34286: ‘View Message’ from XML Queue for ALOCATs incorrect
ALOCAT messages now correctly display times when viewed from the XMLQueue.
34472: [Message UI] NOGI05 Resend Row Totals incorrect
The ‘Total’ column in (NOGI05) NOGAT Platform Advised Flowrate messages, now correctly displays the total for each row, when resending a message.
32077: [Message UI] NOGI01 not displaying commas in amount field
NOGI01 messages correctly show thousand separators.
32132: Ability to send Edigas v4 (XML) ACKNOWs from ENOM XML
ENOM can now encode and send Edigas v4 (XML) ACKNOW messages from ENOM XML.
32703: Ability to send DVGW v5.4 (EDI) ALOCATs from ENOM XML
ENOM can now encode and send DVGW v5.4 (EDI) ALOCAT messages from ENOM XML.
32678: Subcontract References in IMBNOT Messages
To support IMBNOT messages used by Gas Connect Austria, Subcontract References in IMBNOT messages are now decoded. This affects the HTML generated from these messages.
32680: Support for Edigas v4 (XML) Reconciliation Notices
To support IMBNOT messages used by Gas Connect Austria, Edigas v4 (XML) IMBNOT messages with Type 16G (Reconciliation Notice) will now be displayed as such. This affects the HTML generated from these messages.
32678: ENOM XML changes for IMBNOT Messages
The ENOM XML generated from IMBNOT messages will include Subcontract References when present in the message. It will also include Shipper Aliases in the ‘shipper_imbalances’ section when configured.
32680: ENOM XML changes for Edigas v4 (XML) IMBNOT Messages
The ENOM XML generated from Edigas v4 (XML) IMBNOT messages with Type 16G (Reconciliation Notice) will include the new attribute ‘reconciliation_notice = “true”’ on the ‘imbalance_notice’ element.
32733: Nomination Encoding in Edigas v4 (EDI) NOMRES Messages
Edigas v4 (EDI) NOMRES messages now respect the ‘Default Encoding’ setting on the ‘Nomination Encoding’ tab of the ‘Maintenance > Recipients’ screen.
32958: Nomination Encoding in Edigas v4 (EDI) NOMINT Messages
For Edigas v4 (EDI) NOMINT and Edigas v4 (XML) NOMINT messages, a single element in the ENOM XML with direction ‘INPUT’ or ‘OUTPUT’ for a message to an AND encoded recipient will now be correctly encoded as AND.
33167: Display of Shipper Aliases in IMBNOT Messages
Configured shipper aliases are now always displayed when viewing IMBNOT messages. This affects the HTML generated from these messages.
29584: [ENOM+] Matching and Balancing Processing
The Matching and Balancing processing screen has been migrated to .NET. This includes some work to prevent the application from freezing while messages are being processed for Matching and Balancing results.
27943: [ENOM+] Splitting up Messages by internal shipper
A new tab has been added to the ‘Maintenance > Matching and Balancing’ screen called ‘Advanced Matching Rules’. This allows nominations to be split up in Matching by contract reference or by internal shipper. This replaces and extends the Contract Ref Matching functionality. This will aid with the matching of DAC nomination and confirmation messages from Open Grid Europe.
30285: [ENOM+] Balancing uses the global adjustment
Balancing now includes messages irrespective of their time zone. The hour adjustment that is used when viewing Balancing is configured in ‘Maintenance > System > Balancing Hour Adjustment’. Initially this will be set to the most commonly used recipient hour adjustment as part of the database upgrade. This will be useful for Balances which include messages for multiple time zones. For example, values for 6am UK Time and values for 7am CET will be displayed in Balancing in the same hour.
29449: Support for IUK (Multiple Time Zones)
To support Edigas messaging with IUK, recipients can now have ‘Hour Adjustment Overrides’. These are configured in ‘Maintenance > Recipients’.
29695: Allocation Performance Improvements
Performance improvements have been made to the decoding and display of Allocation messages.
29576: Email Technology and Logging
A new ‘Email Log’ screen has been added. All messages related to email notifications appear on this screen, along with much more diagnostic information. In addition, ENOM now uses the built in .NET classes for Email notifications, which makes the system more robust.
29687: Redesign ‘Notify Failure’ Option
The ‘Maintenance > System > Email > Notify Failure’ option has been redesigned and renamed ‘ENOM System Notifications’. The previous functionality remains but it now also sends emails if either the ENOM license or GTS Balancing Info certificate is near expiry.
29561: Improved Error Messages for ENOM XML
XSD reports are now included in the XML log when ENOM fails to decode ENOM XML files.
29496: Move .XSL files to be an embedded resource
The ‘XSL Path’ setting on ‘Maintenance > System’ has been removed. The XSL Transformations are now embedded within the application files.
29538: Remove NOGAT Allocation Timestamp Setting
The NOGAT ‘Allocation Timestamp’ setting on ‘Maintenance > System > Decoding’ has been removed. NOGAT messages now always use UTC for this value.
29721: Message Viewer ‘Only Latest’ now checked by default
The ‘Only Latest’ check box on the message viewer is now checked by default when it is opened.
29748: Sorting quantities columns on Message Screens
Quantity columns on most message forms can now be sorted by value. This sorts by positive numbers first, then negative numbers and then zeros. This has been done to make comparing messages easier.
31200: [Message UI] Message statuses sorting for status (bottom) grid
Status columns on most message forms can now be sorted alphabetically. This has been done to make finding mismatches in the Status grid easier.
31636: [Recipient Details Grid] “Add/Delete” buttons should display “Add/Delete Row”
Nomination Encoding Overrides set in ‘Maintenance > Recipients > Nomination Encoding’ are now added and removed using ‘Add Row’ and ‘Delete Row’ buttons.
29777: Date Change Should Increment the Month
Incrementing or decrementing the date on message forms will now correctly roll over the month and year where applicable.
29134: Printing Shipper Codes
Printed messages now contain shipper aliases as well as shipper codes in the format: SHIPPER CODE (ALIAS).
24324: Path validation on message box
Path validation on text boxes is now done in the background. This will prevent ENOM from locking up while entering paths.
30810: ALOCAT Creation time when not UTC
ALOCATs with ‘CreationTimeStamp’ not in UTC now decode correctly. This affects EKB (Viking) allocations.
30812: ENOM XML in the Inbox
ENOM will now give a more descriptive warning if an ENOM XML file is incorrectly dropped into a messaging inbox.
29739: [External Nominations] Edit for tomorrow option
The ‘Edit’ button on the ‘External Nominations’ screen now respects the settings on ‘Maintenance > System’ to decide what date the new external nomination will be for.
29741: ‘Resend For’ screen sometimes appears in the wrong place
The ‘Resend Message For…’ popup box should now always appear in front of the ENOM main screen.
30975: ENOM XML for APERAK Messages (doc_no_date)
ENOM XML for Edigas v4 (XML) APERAK messages now include the new attribute ‘doc_no_date’ if the message being matched contains such a date in their Identification field. This affects Edigas v4 (XML) APERAKs sent by Energinet.dk.
30975: Edigas v4 (XML) APERAKs displaying wrong date
Edigas v4 (XML) APERAKs used by Energinet.dk should now always display the correct gas day.
30977: Edigas v3 (EDI) APERAK incorrectly shows Rejected
Edigas v3 (EDI) APERAKs now correctly use the code value on the BGM segment to determine if the message is Accepted, Accepted with Remarks, or Rejected. This mainly affects APERAKS received from CEGH.
30977: Edigas v3 (EDI) APERAK Decodes ‘Semantic Error’
Edigas v3 (EDI) APERAKs now correctly decode the error code ‘41G’, meaning ‘Semantic Error’.
30977: ENOM XML for APERAK Messages (has_remarks)
ENOM XML for various APERAK messages now include the new attribute ‘has_remarks’ which signifies whether the message has remarks or not. This affects all Edigas APERAKs, BDEW APERAKs, NOGAT APERAKS (NOGAPP) and Maersk APERAKS (MOGAPP).
31287: Increase Maximum Length of ‘Source’ Values
The maximum length of the ‘Source’ attribute in ENOM XML has been increased to 50 characters.
31244: Maersk Allocations (MOGO11 and MOGO14) Handling Monthly Totals
MOGO11 and MOGO14 Messages now correctly distinguish between values which are per day, and values which are totals for the whole month. This involves significant changes to the message screen and the ENOM XML for these messages.
29867: [UI] Recipient > Message Defaults not wide enough
The ‘To NAD Code’ and ‘From NAD Code’ fields in ‘Maintenance > Recipients > Message Defaults’ have been widened.
18419: Make ‘Message Rules’ grid auto resize
The grid containing the names of the Message Rules in ‘Maintenance > Message Rules’ now automatically resizes to be wide enough for the longest rule name.
30462: ALOCAT messages received from Fluxys not always shown as the same ENOM message type
The decoding of ALOCAT messages now correctly distinguishes between TDPAs (for daily ALOCATs) and TPAs (for other periods of time).
30313: Out of memory error with EnomDatabaseTool
The Enom Database Tool no longer experiences an “Out of Memory Exception” or “Query timeout expired” error when cloning very large databases.
31799: [Nomination Encoding] Zero decoded incorrectly when viewed and sent from message queue
The ‘Direction’ column is now present when you open a message from the XMLQueue if its value can disambiguate the encoding of the zeroes in a row.
28880: [ENOM+] Use of TMN Messages in Matching
TMN messages are now used in Matching if no TDT has yet been received.
28150: GATE ALOCAT Messages
ENOM now supports Allocation messages sent by GATE.
28938: Support for Daily Values in TMC Messages
TMC messages as used by GRTGaz now correctly display the daily values present in the message.
29636: DVGW v4.3 (EDI) NOMRES Messages
ENOM will now decode DVGW v4.3 (EDI) NOMRES messages which do not contain an ‘RFF’ field.
30289: Report Type for DVGW IMBNOT Messages
The ENOM XML for DVGW IMBNOT messages now contains the new attribute ‘dvgw_report_type’. This allows external systems to distinguish between ‘provisional’ and ‘definitive’ DVGW IMBNOTs.
29946: Make hours clearer on ‘GTS Balancing Info’ screen
The ‘GTS Balancing Info’ screen and the grid display for Fluxys IMBNOT messages now display ‘10:00 - 11:00’, rather than just ‘10:00’.
28578: Merge ‘Email Notifications’ feature into ‘Message Rules’
The Message Rules screen can now be configured to send email notifications. This replaces and extends the functionality previously on Maintenance > System > Email.
28580: Emails for Maersk messages
Email Notifications for some Maersk Messages now display the message within the email.
29987: Email subjects for email notifications
The subject text for email notifications now contains much more information about the message.
28234: Add ENOM XML ‘Decode Warnings’ to XML Log
The ‘XML Log’ now contains much more logging information if an XML file cannot be imported correctly. Previously this information was only available in the log files.
28343: ENOM Database Tool
ENOM is now distributed with the ‘Enom Database Tool’. This allows a live database to be cloned for use in testing, automatically removing anything which might interfere with the live system. This tool can also be used to migrate Access databases to Oracle or SQL Server.
29217: Support ‘&’ character in Message Box Paths
Message Box paths once again correctly allow various special characters, including the ‘&’ character.
28152: Support Allocation Scheme 04G
ALOCATs containing ‘AllocationScheme’ 04G will now correctly decode as ‘Pro Rata’ rather than ‘04G’. Note this also affects the ‘quantity_type’ output in the ENOM XML.
29039: Interaction with Short Date Format Setting
ENOM now behaves correctly regardless of the ‘Short Date Format’ windows setting. Under certain conditions this could prevent DELCONs matching up correctly, and could also cause issues with Document Number generation.
20981: Duplicated Messages Issue
Various issues have been fixed around the message saving process. This previously caused ENOM, under some circumstances, to send the same message twice in quick succession.
28731: Index on Creation Timestamp
The message table now contains an index on the ‘CreationTimestamp’ field. This allows the message viewer to return results more quickly under certain circumstances.
29726: Renamed Labels on Maintenance > System > Transport
The labels on the message box lists have been changed to be clearer. The labels now read ‘Unused Message Boxes’ and ‘Active Inboxes’.
29541: SDR Response to a BDR has incorrect dates
An issue has been fixed where the SDR created using the ‘Respond’ button on a BDR message would not be for the correct day by default.
28030: [ENOM+] Add menu item to ‘Create Externally Nominated’
A new menu item called ‘Create Externally Nominated’ has been added to the ‘Message’ menu. This provides access to the creation of Externally Nominated Data.
28489: Edigas v4 (XML) NOMINTs Direction Support
ENOM now supports the use of the ‘Direction’ column in Edigas v4 (XML) NOMINT messages. This is required for certain situations in GRTGaz nominations where both Input and Output are nominated simultaneously.
26119: Edigas v4 (XML) NOMINTs Priorities Support
ENOM now supports ‘Priorities’ in Edigas v4 (XML) SDTs. This is used in notices to Fluxys.
26120: Fluxys Edigas v4 (XML) IMBNOTs
ENOM now supports Edigas v4 (XML) IMBNOTs as used by Fluxys from 1st October 2012. This includes graphs of the current market position and limits, and allows the display to refresh automatically.
28816: Edigas v4 (EDI) DELORDs without contract reference
Edigas v4 (EDI) DELORD messages now decode if the contract reference is omitted. This is to allow DELORDs from Open Grid Europe to be correctly decoded.
28990: Support for ‘Line Contract’ in Edigas v4 (XML) SWT messages
Edigas v4 (XML) SWT messages now support Line Contracts.
27328: Move GTS Balancing Info Tool into ENOM
The GTS Balancing Info Tool has been moved to inside the ENOM application. It can be opened using the ‘Message > GTS Balancing Info’ menu item.
27922: Warning message when recipients are not configured (Edigas XML Messages)
ENOM will now warn you when opening an Edigas XML message if either of the recipients are not configured. Note that EDI messages already warn about this.
27028: Performance improvements to Message Resizing
Performance improvements have been made to the tabbed grid resize code. This allows all message forms to resize faster and more smoothly.
27840: Performance improvements to Recipients screen
Performance improvements have been made to the Recipients maintenance screen.
27171: Performance improvements to Shipper Codes screen
Performance improvements have been made to the Shipper Codes maintenance screen.
27409: Add Raw UNB Codes to ENOM XML
All ENOM XML files generated by ENOM now contain the 4 additional attributes ‘rawfromunbcode’, ‘rawfromunbcodelist’, ‘rawtounbcode’ and ‘rawtounbcodelist’.
26552: Remove support for ENOM legacy files
ENOM no longer supports the use of .in and .out files. These were last used with ENOM v4, and could be used to generate a small number of Edigas v1 (EDI) and Edigas v2 (EDI) messages.
29305: Reject +/- Encoding in Edigas v4 (XML) NOMINTs
Edigas v4 (XML) NOMINTs will now refuse to send if they are configured to use the encoding ‘+/- Quantity Delivered’. This encoding is not supported by the Edigas v4 specification. Previously the message was encoded using the ‘OR’ encoding which often lead to confusion.
27627: Use of Credit and Debit in ACCPOS messages
ACCPOS messages now use the sender of the messages to determine what credit (ZPE) and debit (ZPD) mean. Normally credit represents a positive value and debit represents a negative value. For messages from Fluxys the opposite convention is used.
28010: [ENOM+] Entering Externally Nominated Data from Balance Detail
The ‘No Data’ text on the balance detail screen has been replaced with ‘Add Data’, to make it clearer that you can double click on it to Add Data.
27809: Edigas v3 (EDI) SWA Nomination grid does not update dates when resending
Edigas v3 (EDI) SWA messages now correctly update dates along the top of the grid when the resend button is pressed.
27847: Copy and paste ignoring white space
Spaces are now removed from the start and end of each entry when pasting values into messages.
27964: ALOCATs and IMBNOTs do not display Contract Reference
ALOCAT and IMBNOT messages now correctly display the message contract reference on the message screen.
26781: ALOCATs and IMBNOTs do not use Decimal places setting
ALOCAT and IMBNOT messages now correctly respect the settings on the ‘Maintenance > Units’ screen when deciding how many decimal places to display.
23355: ALOCATs and IMBNOTs incorrectly display Zero Values
ALOCAT and IMBNOT messages now correctly display zero values as ‘0.00’ instead of ‘.00’.
28043: ENOM XML for Single Hour ALOCATs on a 25 hour day
The ENOM XML for ALOCAT messages now contains the start and end times in UTC, as well as in local time. This is to solve an issue related to messages containing only a single hour on the 25 hour day.
27811: Message List in ENOM shows a MOGO03T
MOGO03T has been removed from the various message lists in ENOM, as this message type is not used.
28148: Allocated values incorrectly displayed as confirmed
The DAS and MAS message screens now correctly put confirmed values in the confirmed column, and allocated values in the allocated column. The ENOM XML remains unchanged.
28488: Message Date Picker made wider
The date picker on all message forms has been made wider. This allows ‘Mars’ to be correctly displayed when using French regional settings.
23968: DVGW-ALOCAT 5.4
DVGW-ALOCAT 5.4 is now supported. These will be used in German networks from 1st April 2012.
23969: DVGW-IMBNOT 5.3
DVGW-IMBNOT 5.3 is now supported. These will be used in German networks from 1st April 2012.
25540: IMBNOT from Energinet.dk
Edigas v4 XML IMBNOT as used by Energinet.dk is now supported.
26981: ACCPOS from Energinet.dk
Edigas v4 XML ACCPOS as used by Energinet.dk is now supported.
25542: APERAK from Energinet.dk
Edigas v4 XML APERAK as used by Energinet.dk is now supported.
25742: Sending v4 XML APERAK messages for Energinet.dk
Edigas v4 XML APERAK can now be automatically sent in response to v4 XML NOMRES, v4 XML ALOCAT, v4 XML IMBNOT and v4 XML ACCPOS messages. This is configured in the Acknowledgments tab of the Recipients screen. This is a requirement for shippers who exchange Edigas messages with Energinet.dk.
27579: Changes to ENOM XML for IMBNOT Messages: Extra Attributes
The extra attributes ‘system_operator’ and ‘supplier_code’ now appear on the ‘imbalance’ node for ENOM XML from DVGW v5 IMBNOT messages. Their values will be blank (e.g. ‘supplier_code = “”’) as these attributes are currently only used in ENOM XML from Edigas v4 XML by Energinet.dk.
27579: Changes to ENOM XML for IMBNOT Messages: Quantity Type Changes
The words ‘Credit’ and ‘Debit’ no longer appear in the ‘quantity_type’ attributes in the IMBNOT ENOM XML. Instead, quantities that have a credit quantity type will be positive and those that have a debit quantity type will be negative. (See case 27877 below for notes concerning IMBNOT messages sent by Fluxys)
27877: Changes to ENOM XML for IMBNOT Messages: Quantity Type Changes (Fluxys)
For all IMBNOT messages sent by Fluxys: The same as case 27579 directly above, except that the opposite convention for signing quantity values will be used. This is to ensure that long positions are displayed as positive and short positions are displayed as negative.
27601: Changes to ENOM XML for ACCPOS Messages
Edigas v4 XML ACCPOS messages now decode the direction code ZPE (Credit) as positive and ZPD (Debit) as negative. Previously the opposite convention was used.
27578: Changes to ENOM XML for ALOCAT Messages
The roles of ZES (Shipper) and ZSH (Internal Shipper) now decode correctly. Previously ZES (Shipper) was decoded as ‘Internal Shipper’ and ZSH (Internal Shipper) was decoded as ‘Shipper’.
The role ZSO (System Operator) is now decoded separately under the attribute ‘system_operator’, not under ‘shipper’. If the role ZSO is not used then ‘system_operator=””’ will be included in the ENOM_XML.
25783: Changes to Maersk messages
A number of required changes have been made to Maersk messages.
24859: Sending v3 MOGAPP messages for Maersk
Edigas v3 MOGAPP messages can now be automatically sent in response to Maersk messages. This is configured in the Acknowledgment tab of the Recipients screen.
26598: Sending ACKNOW messages
It is no longer possible to manually send an ACKNOW when viewing a BIDACT. ENOM can be configured to send them automatically. This is configured in the Acknowledgments tab of the Recipients screen.
26364: Display of hour names
IMBNOT and ALOCAT messages (TPAs, TDPAs, TDDAs & TDAs) no longer refer to ‘Hour Number’ in the display. Instead they display the relevant date and time. (e.g. 01 Dec 06:00). This does not affect the ENOM XML
27410: Warning should be given if recipient not found
A warning will now be given when opening a message if the recipients cannot be identified.
27473: Upgrade to Microsoft .NET Framework 4.0
ENOM is now deployed with the .NET Framework v4.0. The ENOM installer will offer to download and install this if it is not already installed.
26957: Quantity status 57G in v4 NOMRES messages
The Quantity Status 57G in v4 NOMRES messages will be decoded as ‘Rejected’, rather than ‘Other’. Note that there is no change to the ENOM XML.
25977: ALOCAT UI displays incorrect hours
IMBNOT and ALOCAT messages (TPAs, TDPAs, TDDAs & TDAs) now correctly display times for messages which do not start at 06:00.
12846: Selecting locations by entering first letter
When adding locations to messages, pressing a letter key no longer automatically adds the first location starting with that letter. Instead, the list will remain open with the corresponding location selected.
21116: [ENOM+] Support for internal shippers in matching and balancing
Matching and Balancing now supports Internal Shippers. This affects all matching and balancing screens.
21116: [ENOM+] Redesign of the ‘Mappings’ functionality
The ‘Location Code Mapping’ and ‘Shipper Code Mapping’ screens have been merged into a single ‘Code Mappings’ screen. This new screen also supports Internal Shipper Code Mappings.
22010: [GBIT] Version link
The GBIT tool now contains a ‘Help > About’ screen which shows the version number of the tool.
20134: Migrate ‘Tabbed Grid’ to VB.NET
The ‘Tabbed Grid’ on which most messages are displayed has had its functionality improved and updated to be more intuitive.
20134: Migrate ‘Message Header’ to VB.NET
The ‘Message Header’ at the top of every message screen has had its functionality improved and updated to be more intuitive. This includes improvements to the date pickers to make them more robust.
20134: Migrate ‘ENOM Textbox’ to VB.NET
The ‘Enom Textbox’ used on a large number of screens has had its functionality improved and updated to be more intuitive.
21184: Remove Fixed Rows from Advanced Message set up
The ‘Fixed Rows’ checkbox has been removed from the ‘Advanced’ sub menu of the Available Messages screen. Other functionality on this screen (including adding default rows) remains unchanged.
25083: Make the ‘source’ attributes clear in the UI
The ‘Message Properties’ screen now includes the ‘Source’, ‘Source Ident’ and ‘Source Text’ if the message was created by an external system via the ENOM XML interface.
25474: Enable BALDOC messages to be sent for a period longer than one day
Balancing Agreement messages for GTS can now be sent for any period of time rather than just a single day.
25868: Decoding IMBNOTs which don’t have a Contract Reference
ENOM will now allow an IMBNOT to be decoded if the message does not contain a contract reference.
26134: Schema Checker to correctly check the size of Oracle Number fields
The Schema Checker now checks the sizes of Oracle Number fields after an upgrade. The corresponding fields have been set to the correct size, fixing a ‘rounding’ issue on balancing screens in rare circumstances.
25696: [ENOM+] Window does not resize correctly
The compare messages screen now resizes itself when opened so that all the values can be displayed.
22578: [ENOM+] Line contracts not displayed in matching and balancing
Line contracts are now correctly displayed on the compare messages screen.
24988: Output ENOM XML not produced for NOGAPP messages
ENOM will now correctly output ENOM XML when it sends a NOGAPP message (NOGAT Acknowledgment) if it is configured to do so.
25354: Button text says ‘Response’ not ‘Respond’
The ‘Response’ button is now more accurately labeled ‘Respond’. This affects all messages containing this button.
25768: SDRv4 XML showing incorrect response header title
Message forms created using the ‘Respond’ button now have a more appropriate title.
25800: NOGAT Allocations from GDF Suez use UTC for allocation timestamp
There is now an option on ‘Maintenance > System’ which determines the interpretation of date fields on NOGAT Allocations. This is to allow a smooth transition of message supplier.
24527: Received Maersk messages always show decimal places
Maersk messages now correctly honour the decimal places settings on ‘Maintenance > Units’.
24531: CONTRL messages overwriting an APERAK message
ENOM will now correctly use the status from an APERAK message over that from a CONTRL message, regardless of the order in which the messages are received.
24942: ONTRAS control messages not recognised as acknowledgement
The message viewer will no longer display CONTRL messages if ‘Hide Acknowledgments’ is checked.
25425: MOGO03 XML Format doesn’t have unit
The ENOM XML for MOGO03 now correctly contains the unit values from the message.
25890: Zero EOD balance but non-zero hourly balances not highlighting correctly
Balances with a zero ‘End Of Day’ figure but with an imbalance for an hour within the day are once again highlighted on the ‘Balance Summary’ screen.
26066: ENOM outputting UNB Codes in ENOM XML
ENOM will now output 4 new attributes in the ENOM XML for Edigas v4 (XML) CHACAP messages: ‘rawfromunbcode’, ‘rawfromunbcodelist’, ‘rawtounbcode’ and ‘rawtounbcodelist’.
25621: CHACAP v4 XML outputs zero rather than null values
The ENOM XML for CHACAP messages will now output an empty string rather than a zero if the hour in question has no associated quantity.
26063: Support for ‘Nomination Encoding’ behaviour in Edigas v4 (XML) NOMINTs
The ‘Nomination Encoding’ configuration on the ‘Maintenance > Recipients’ screen now affects Edigas v4 (XML) NOMINT messages. This is required for the new GRTgaz messages to function correctly.
25483: Edigas v4 (XML) Allocations
ENOM now supports a number of additional codes in Edigas v4 (XML) ALOCAT messages. In addition, the performance of these messages has been improved.
24952: Option to restart document number at 1 every day
ENOM can now encode Edigas v4 (XML) messages with the Document Number restarting at 1 every day by including the date in the Identification. This will be required by GRTgaz, and is configured on the Maintenance > Recipients screen.
25751: GATE total incorrect for last hour
A bug has been fixed whereby the ‘total’ value in the Edigas messages when ‘Capacity Type’ is used would be incorrect if the value for the final hour of the day differed from the second last hour. This only affects messages for the GATE LNG terminal.
24732: NOGATs marked ‘Accepted’ when NOGAPP sent
ENOM will no longer incorrectly mark incoming NOGAT messages as ‘Accepted’ when an acknowledgment message is sent. Outgoing NOGAT messages will continue to be marked ‘Accepted’ when a NOGAPP is received.
25701: ACKNOW status of 35G should not show as Rejected
An ACKNOW status of 35G is now marked as ‘Remarks’ rather than ‘Rejected’. This code means ‘Counterparty Prevailed’.
24318: BDEW v2.0f APERAK and v1.3d CONTRL Messages
ENOM now supports BDEW v2.0f APERAK and v1.3d CONTRL messages as used by ONTRAS.
23099: Add hostname to failure emails subject line
Emails sent now include the hostname of the computer on which ENOM is running.
23067: DELCONs to be decoded using any codelists
DELCONs can now be decoded using any codelist specified for the recipients (values held in the header NAD fields).
23199: Response button on TCN v4 XML
Edigas v4 (XML) TCN messages now display a response button, which performs the same function as the equivalent Edigas v2 (EDI) message response button.
24102: NOGAPP messages sent automatically without the need to open the message
ENOM can now be configured to send the NOGAT APERAK response as soon as a message is received, as an alternative to when the message is opened. This is configured on the Maintenance > Recipients screen.
21189: ENOM support for the new Maersk messages (Based on Nogat)
ENOM now supports a number of message types for the new TYRA East gas field. This involves significant changes to the behaviour, XML and user interface for the custom NOGAT messages (NOGIxx and NOGOxx). These new Maersk messages require a new license key to activate.
24263: Sort Capacity Types Alphabetically
The options for the Capacity Type field on Edigas v4 (XML) NOMINT messages are now sorted alphabetically. This field is used for GATE messages.
21245: Hour adjustment not applied to AllocationTimestamp in NOGAT Allocations
The ‘AllocationTimestamp’ in NOGAT Allocations is now correctly converted to NOGAT local time. Previously the value was displayed in LET-1.
23057: Print doesn’t work for Edigas v4 (XML) REQRES
Printing now works correctly for Edigas v4 (XML) REQRES messages.
23058: Print doesn’t work for Edigas v4 (XML) AVAILY
Printing now works correctly for Edigas v4 (XML) AVAILY messages.
23499: Using Gas Day on Sent/Recvd radial options
The message viewer once again uses calendar day when sorting by Sent/Recvd date, rather than gas day.
24046: [ENOM+] Cannot link to Confirmation message from Compare Messages
Confirmation messages can once again be opened from the compare messages screen when there is no corresponding nomination message.
24116: Values do not copy across on SWR v4 (XML) messages
Edigas v4 (XML) SWR messages now correctly copy values across the grid by default.
20956: NOGAT messages incorrectly named in ENOM
NOGO09 and NOGO11 were incorrectly labelled as ‘Upstream’, and NOGO10 and NOGO12 were incorrectly labelled as ‘Downstream’. This issue has been corrected both in the user interface and in the ENOM XML.
23918: DVGW v5.3 ALOCATs (Gaspool)
ENOM now supports DVGW v5.3 ALOCATs as used by Gaspool.
9304: [ENOM+] Ability to enter a “dummy” value into Balances
ENOM+ now allows the entry of ‘Externally Nominated’ data. This is configured on the ‘Matching and Balancing’ Maintenance screen, on the new ‘Externally Nominated’ tab.
23050: [ENOM+] Bulk Operations
The Bulk Operations screen has been updated to include the new ‘Delete All Externally Nominated Data’ option.
22559: [ENOM+] Create Data button
The ‘Create’ button now allows ‘Externally Nominated’ data to be created in addition to messages. This is only enabled if you have at least one Externally Nominated configuration.
22467: [ENOM+] Externally Nominated Data Viewer
The Externally Nominated tab has been added to the ENOM+ viewer. This allows Externally Nominated data to be viewed and filtered in the same way that messages are.
18371: AllocationScheme codes for Edigas messages
Edigas v4 (EDI and XML), DVGW v4 (EDI), and DVGW v5 (EDI) ALOCAT messages now support a much larger number of quantity status codes. Existing codes remain unchanged.
14740: Add user permission for ‘XML Polling’
A new user permission has been added which enables or disables the polling of a folder for ENOM XML. This is set to enabled by default.
18112: FTP Log tabs in Alphabetical Order
The FTP Log has been changed so that it uses a combo box to distinguish message boxes instead of tabs.
20811: Compare Message Screen not Sorted
The compare messages screen is now sorted when first opened.
21677: Schema Checking warning box
The ENOM Schema Checker will now display a progress box when it is running a check showing the current action and process bar.
18063: Filepath highlighting in red when folder doesn’t exist
Paths in the ENOM maintenance screens are now colored red if the folder does not exist.
22079: [GBIT] How is creation time used in the web services?
The GBIT tool should now always query with the correct creation time regardless of what time zone you are in. This sometimes caused the wrong set of results to be returned by the GTS web services.
22080: [GBIT] Time used to display the values returned by GTS
The GBIT tool has had its internal use of times reviewed. This was done to ensure it continues to work correctly after the 25 hour day.
22261: [GBIT] Error opening Access databases on a network drive
The GBIT tool will now correctly open Access databases if they are held on a network share which isn’t mapped. In other words, if the path starts with “\”.
23128: TCN respond button error
The ‘Response’ button on Edigas v2 (EDI) TCN messages should now work correctly.
23016: Priorities are not displayed once a message has been sent with a shipper alias
Shipper Aliases should no longer interfere with the display of Priority values on Edigas v4 (EDI) NOMINTs as used by Fluxys.
21404: Allow Use of & Character in Paths
ENOM should now correctly allow the use of the ‘&’ character in all paths.
18186: FTP log claiming complete but incomplete
The FTP log will now display “Completed with errors” if an FTP operation finishes unsuccessfully.
20701: Zero out a row when changing to same shipper
The ETM Tabbed Grid used on most message forms will no longer zero out a row if a shipper code is reselected.
21743: Print doesn’t work for Edigas v4 (XML) REQESTs
Edigas v4 (XML) REQEST messages can now be printed.
22058: Support for ‘BuyerRole’ and ‘SellerRole’ in ENOM
Edigas v4 (XML) contract notices will now correctly decode the BuyerRole and SellerRole attributes, provided they are set to ‘BY’ or ‘SE’ as appropriate.
22220: Rogue Apostrophe on Hourly Status on GTS confirms
There is no longer an extra apostrophe on the label for Edigas v4 (XML) NOMRES messages with an hourly status breakdown. This includes GTS confirmation messages.
21718: [ENOM+] Balancing performance improvements
There have been some significant performance improvements to the ENOM balancing summary screen.
17317: Make FTP Log message ‘Check’ clearer
Outboxes are now “checked for unsent messages” in the FTP log, instead of simply being “checked”.
22786: Increase Edigas v4 (XML) NOMINT Release number to 4
The ‘Release’ number used in Edigas v4 (XML) NOMINT messages has been increased from ‘3’ to ‘4’ as required by GATE. This affects all Edigas v4 (XML) NOMINT messages, and has been integration tested with GTS, EKB and NAM.
22834: GATE confirms don’t work
Edigas v4 (XML) NOMRES messages now support multiple status codes per hour and a reasontext value per hour, as required by GATE.
20501: GATE NOMRES
Edigas v4 (XML) NOMRES messages (TDT, HCN etc) can now use the ‘Capacity Type’ column, as required by GATE. This attribute will be generated within the ENOM XML if applicable.
20507: GATE NOMRES - quantity status
Edigas v4 (XML) NOMRES messages (TDT, HCN etc) can now use the Quantity Status field in the message. This affects most messages from GTS, including TTF TDTs and the new GATE messages.
Note that the ENOM XML for these messages has similarly changed to include the new ‘statuses’ section.
20500: GATE NOMINT
Edigas v4 (XML) NOMINT messages (SDT, CDT) can now use the ‘Capacity Type’ column, as required by GATE. This attribute will be generated within the ENOM XML if applicable.
20240: M&B Config screen rewrite
The ‘Maintenance -> Matching and Balancing’ screen has been rewritten to make it more usable and consistent with the rest of ENOM.
21740: Changed Message Properties Text
The font used to display EDI on the message properties screen has been changed to be more readable. In addition, the end of each line now displays the ‘ character.
21501: DVGW v4.2 NOMRES for Aequamus
ENOM now supports DVGW v4.2 ALOCAT messages as used by Aequamus.
20509: GATE matching - decomposition
Matching and Balancing screens now include the Capacity Type where applicable. This allows the message exchange with GATE to work correctly.
20350: Implement EKB (Viking) ALOCAT
TDPA and TDDA messages now support profiled GCV values as used in Edigas v4 (XML) ALOCAT messages from EKB. This appears as a separate section in ENOM and as an extra section within the ENOM XML generated.
20502: GATE NOMRES - decomposition
ENOM now supports the new ‘Decomposition’ element within Edigas v4 (XML) NOMRES messages as required by GATE. This is displayed in the UI as ‘Capacity Type’.
21100: ENOM should not start when provider is SQLOLEDB
ENOM will now give a warning if it is started using the SQLOLEDB provider as it has known issues. It is recommended to use the provider we support and test - SQLNCLI (SQL Server Native Client).
17463: [GBIT] Addition of colours on Grid Display
The GTS Balancing Info grid display now displays colours on the zone columns. This includes the SBS column to indicate which zone the SBS is in.
19811: [GBIT] Tool now contains a separate grid for the POS
In the GTS Balancing Info tool, the POS has been moved to a second grid to make it clearer if your POS has changed.
18053: [GBIT] Ability to hover the cursor over lines on chart and have the time displayed
The GTS Balancing Info tool grid will now display the quantity if you hover your mouse over it for a short period of time.
21699: Nomination encoding failure when resending with zero values for an ‘exit only’ location
A bug was fixed in Nomination Encoding where the ‘Exit Only’ points would sometimes encode a 0 value with a Z02 in some network notices.
In addition, the ENOM XML for NOMINT and NOMRES messages (SDT, CDT, TDT, TMN, HCN etc) will now correctly populate the ‘direction’ attribute where this bug applies.
21449: [GBIT] Grid Display & Log Tabs not displaying
The GBIT tool now uses an improved grid control. This ensures compatibility with 64 bit machines and allows use of the mouse wheel.
21451: [GBIT] Not refreshing automatically
The Prognosis values in the GBIT tool will now correctly refresh every 5 minutes.
21658: [XML] ALOCAT v4 (XML) Output ‘input’ and ‘output’ correctly.
In the XML generated by ENOM for ALOCAT v4 (XML) messages (NAM allocations), the ‘quantity_type’ field will now be correctly populated with ‘input’, ‘output’, ‘total input’ or ‘total output’. Note that a profile with a change of direction will now be output as 2 separate profiles, one with the ‘input’ and one with the ‘output’ values, rather than a single net profile.
21659: [XML] ALOCAT messages now output ‘Calculated’ instead of ‘07G’
In the XML generated by ENOM for ALOCAT v4 (XML) messages, ‘07G’ in the ‘quantity_status’ field is now translated to the more user friendly ‘Calculated’.
21081: [Locations] Loading Time
The performance of the various grid maintenance screens has been improved. This includes Shipper Codes, Contracts, Locations and M&B Maintenance.
21155: Can’t filter by Message name for NOGAPP message type
It is now possible to filter only NOGAPP messages in the ENOM Message Viewer.
20109: [GBIT] No label on volume
The GTS Balancing Info tool now displays the unit that the volumes are in on the appropriate axis.
18052: [GBIT] Time Zone shown on the GTS Balancing tool - CET, UKT or local time
The GTS Balancing Info tool now makes it clearer than all times are in GTS Local time (CET).
20881: Added a ‘Z’ to the ‘ReceivingDocumentDateTime’ for generated ACKNOWs
ACKNOWs generated by ENOM now correctly contain a ‘Z’ on the end of their ‘ReceivingDocumentDateTime’ value. These messages are used to respond to BIDACT messages from GTS.
17942: [XML] Make CONTRL and APERAK messages output ‘otherdoc_source’ in ENOM XML
CONTRL and APERAK messages now include source information in their generated XML to allow external systems in interface with this information.
19196: Include CLRCON messages in M&B
Clearing Confirmations from GTS can now be included in a custom balance. These quantities are treated as being both Nominated and Confirmed.
19404: Clear up how ENOM uses ‘Input’ and ‘Output’ in M&B
The ‘Compare Messages’ screen should now be a lot clearer when matching messages with both Input and Output quantities at the same Shipper code and Location at the same time.
19049: ETMTabbedGrids supports improved Copy & Paste functionality
The tabbed grids used on most message forms now allow a much greater variety of Copy and Paste functionality. Please note that it is no longer possible to paste a vertical column of numbers into a horizontal row. This allows a vertical column of numbers to be pasted in as a vertical column.
20351: View message save to path
When a file is saved to a local folder, the logging message now contains the path and message box name. This is in addition to the date/time and machine information present in previous ENOM versions.
20881: Incorrect spelling of category in Balancing Agreement messages
‘Reference Category’ is now correctly spelled on Balancing Agreement Messages.
18132: ACKNOWs generated in ENOM for BIDACT do not show correct date
ACKNOWs generated by ENOM should now have the correct date displayed, allowed them to appear for the relevant gas day in the message viewer.
19754: ENOM tabbed grids highlight ‘Tab Totals’ if decimal places are used
The ‘Tab Total’ on message forms will now only highlight a non-zero total, regardless of the decimal places settings used.
19807: Version number not printed when you print out an ENOM programme message
The version number is now correctly printed on Programme messages.
19424: Reword unread message when there is only 1 unread message
ENOM will now display ‘1 Unread Message’ rather than ‘1 Unread Messages’ in the appropriate situation.
20156: Add ‘BIDDOC Source’ fields to BIDACT XML format
The ENOM XML format for GTS Bid Activation messages has been changed to include 3 new attributes: ‘biddoc_source’, ‘biddoc_source_ident’ and ‘biddoc_sourcetext’. These attributes allow an external system to correctly identify which Bid Document message is being activated.
13078: ENOM Installation Improvement
The ENOM installer can now automatically upgrade from the previous version when installing a new one. It is therefore no longer necessary to manually uninstall the previous version.
15195: Implement Edigas v4 (XML) AVAILY
ENOM now supports Edigas v4 (XML) AVAILY messages: SDA and SWAs.
17462: [GBIT] Freeze Date column on Grid Display
The ‘Date’ column on the GBIT grid display now always displays.
18618: [UI] Message Rules hyperlink option names
The hyperlinks on the message rules screen have been redesigned to make them more readable.
18670: Nomination Encoding to support Un-grouping of hours
ENOM now supports the ‘ungrouping’ of hours within Edigas NOMINT messages as required by Net4Gas. This is configured on the ‘Maintenance > Recipients > Nomination Encoding’ screen.
18706: GTS new model - PROCON Status codes
Various codes in PROCON messages have been renamed in the UI to make their meaning clearer. This does not affect the XML interface. Affected Codes:
69G: “Damping Incorrect” changed to “Out of Balance” 71G: “Adjusted [Due to Damping Incorrect]” changed to “Adjusted [Out of Balance]” 74G: “Mismatch and Damping Incorrect” changed to “Mismatch and Out of Balance”
18832: Make ENOM deployment work with .NET Components
ENOM is now deployed with .NET components which means that the .NET framework v3.5 SP1 is now required to use ENOM. If the .NET framework is not yet installed ENOM will guide you through its download and installation.
19111: GTS new model - ACKNOW Status codes
Various codes in ACKNOW messages have been renamed in the UI to make their meaning clearer. This does not affect the XML interface. Affected Codes:
04G: “Processed After Deadline” changed to “Received After Deadline” 69G: “Damping Incorrect” changed to “Out of Balance”
20268: Nomination grid not updating when resending SWAv4
Weekly contract notices in Edigas v4 (XML) formats (BWR, BWF, SWA and SWR messages) now correctly update the grid titles when the ‘Resend’ button is pressed.
20149: ACKNOW code 78G should show remarks rather than rejected
ACKNOWs with code ‘78G’ (Counterparty Missing) now mark their corresponding message as ‘Remarks’ rather than ‘Rejected’, as the message has been accepted into GTS’s system.
19597: BIDDOC - Price label needs to be clearer
The ‘Currency’ combo box now also displays (Per ‘Unit’) to make it clearer what the values mean. For example: “Euros (Per kWh)”
18100: BDRv2/v3, SDAv2/v3 and SDRv2/v3 not highlighting for profiled account
Edigas v2 and Edigas v3 contract notices should now correctly highlight in the message viewer if they are profiled.
18766: Review ‘Qty Types’ on REQRESv4 XML
Edigas v4 (XML) REQRES messages now support the Shipper Offtake / Delivery (Z36) code.
18810: Acknow reason code is from the latest Acknow not the one selected
Opening an ACKNOW from the Message Viewer by double clicking on the ‘Ack’ column should now always open the correct message.
19174: Rename Local Settings Options
The Local Settings ‘XML’ screen and the System ‘XML’ screen have been redesigned to make the correspondence clearer.
18568: Misleading warning in BALDOC message
The message on BALDOC messages which informs the user that insufficient data has been entered has been clarified.
17780: ‘Local Settings’ XML-In folder should use locking
The ‘Local XML’ inbox now uses database locking, preventing various problems related to using both local and system XML inboxes at the same time.
18779: Global/Message contract and Line/Sub contract reference naming
‘Contract’ has been renamed ‘Line Contract’ across ENOM when a line contract is being referred to. The term ‘Contract’ now always refers to the message contract reference.
19006: Positive/negative only profiled nominations in REQEST messages
The message on Edigas v4 (XML) contract notices regarding a change of direction within a contract has been clarified.
19354: ENOM matching screen set up error - Auto ignore section
It is again possible to configure Auto Ignore rules at the shipper code level.
19036: Source and Location not displayed in XML Queue for v2 SDT
The XML Queue should now correctly display ‘Source’ and ‘Location’ information for Edigas v2 SDTs.
18393: DVGW shipper and operator type should be settings on the recipient
There is now an option on the ‘Maintenance > Recipients > Message Defaults’ screen to allow the DVGW options to be specified in ENOM as defaults, rather than requiring external systems to pass this data in with the XML file. This does not affect messages created in ENOM directly.
16508: The ENOM password stored in the registry shouldn’t be in plain text when auto login is chosen
Passwords saved using the ‘File > Local Settings > Auto Login’ option are no longer stored as plain text. Previously saved passwords are not affected by this change.
18293: Nomination Encoding on Line Contract Ref level
ENOM now supports Nomination Encoding at the Line Contract and Shipper Code level, as required by some CEGH messages.
18322: [Usability] Add option for XML Generation in Maintenance menu
A new option was added to the Maintenance menu to open the ‘Message Rules’ screen.
19060: BIDACT messages do not process efficiently
Fixed an issue where large BIDACT messages were taking a long time to process. They should now process at the same speed as other messages.
18455: Add Message Rules to the Maintenance Menu
A link to the Message Rules screen has been added to the Maintenance menu.
18242: REQEST and REQRES error messages
The message on REQEST and REQRES messages in Edigas v4 (XML) which informs the user that “The message cannot contain a change of direction” has been clarified.
18353: Cant delete rows in BALDOC and BALCON messages
It is now possible to delete rows in BALDOC and BALCON messages by double clicking on the row to be deleted.
18460: Make ‘Lock String’ field in database longer
The size of the ‘Lock String’ field has been increased from 50 to 150 characters, to prevent some problems when both the machine name and user name were both fairly long.
18250: ENOM balancing tool - Grid display are +ve/ -ve signs correct - confusing
In the GTS Balancing Info Tool, the positive buffer zone columns are now correctly labeled as maximum values, and the negative columns as minimums.
18262: Able to save Maintenance > System without an M&B Unit
It is no longer possible to save the data on the Maintenance > System screen with Matching and Balancing enabled, but without a unit selected.
18203: ACKNOW from GTS shows as rejected when it is accepted
The ACKNOW code meaning “Damping Incorrect” will now show up as ‘Remarks’ rather than ‘Rejected’, as when this message is displayed the message has been accepted into GTS’ system despite being out of balance.
18204: Cannot resize an ACKNOW message
The ACKNOW message screen can now be resized.
17505: Support SubContractReference in Edigas v4 XML NOMINT
ENOM now supports the use of the SubContractReference (Line Contract) in Edigas v4 (XML) and Edigas v4 (EDI) NOMINT messages.
17899: User ‘Grace’ period message changed
The ‘Grace’ period in which a user receives a warning of imminent user account expiry has been changed from 5 to 14 days. In addition the message has been clarified.
17987: Add status and reasontext to ACKNOW XML Generated
ENOM XML Generated for ACKNOW messages should now contain a code related to the status and reasontext contained within the ACKNOW message.
17883: Support SubContractReference in Edigas v4 XML NOMRES
ENOM now supports the use of the SubContractReference (Line Contract) in Edigas v4 (XML) and Edigas v4 (EDI) NOMRES messages.
17968: ACKNOWs should be also using the ‘DocNoDate’ to match
ACKNOW messages now also use the ‘DocNoDate’ field to match with the other message, to help prevent it from matching with incorrect messages when message are moved between systems.
18008: ALOCATTGs aren’t affect by message rules specifying them
ALOCATTG messages should now function correctly from the Message Rules screen.
18025: Include version number in message UI
The UI for messages which contain a version (Such as BIDDOC and PROCON) will now display the version number in brackets after the document number, as the document number alone does not uniquely specify the message.
18038: GTS Acknow message status window not showing all rejection status’s
ACKNOW messages should now correctly display all the status codes within the message if there is more than one.
16652: ENOM support for sending acknowledgments
ENOM can now be configured to automatically send a ACKNOW message in response to a BIDACT message whenever such a message is received, rather than requiring manual user intervention.
17474: GTS new model - Status code explanations should be changed
Some of the PROCON codes have been changed to make their text more closely match the meaning of the code. This affects both the UI, and the XML which ENOM generates.
17814: [GBIT] Enlarge config text boxes
In the GTS Balancing Info Tool, the text boxes on the Config screen show now correctly enlarge as the screen does.
17471: [GBIT] GTS Balancing tool needs a key on the POS and SBS tab
In the GTS Balancing Info Tool, the graph now has a key which shows what each colour represents.
17706: [GBIT] Tool attempts to poll services before it has database access
The GTS Balancing Info Tool will no longer attempt to poll the GTS web services before it has a database connection.
17795: DELCON and ACKNOW open as APERAK when double clicking Ack column
Double Clicking in the ACK column for a message acknowledged by an ACKNOW or DELCON will now correctly display the acknowledgment message.
15194: Implement Edigas v4 (XML) REQRES
ENOM now supports Edigas v4 (XML) REQRES message: SDR and SWR.
15204: Implement GTS Balancing Agreement Messages
ENOM now supports Edigas v4 (XML) GTS Balancing Agreement messages: Receiver’s Balancing Agreement Notice (RBAN), Supplier’s Balancing Agreement Notice (SBAN), and their corresponding confirmations (RBAC and SBAC).
16917: Message Rules Highlighting in red
The message rules screen will now highlight the links in red if the message rule is generating XML for ‘No Messages’, or ignoring ‘All Messages’.
17489: ‘Expect Acknowledgment’ for incoming message now per recipient.
The ‘Expect Acknowledgment Messages’ functionality for outgoing messages has been removed from the available message screen, and is instead now configured per recipient.
17490: ENOM XML from PROCONs should contain otherdoc_source_ident
The ENOM XML for PROCON messages now contains the source, source_ident and sourcetext of the PRODOC to which it is a response, to help other systems match the two up.
17212: ENOM XML from ACKNOWs should contain otherdoc_source_ident
The ENOM XML for ACKNOW messages now contains the source, source_ident and sourcetext of the sent message to which it is a response, to help other systems match the two up.
17704: Message Properties Title revisited
The message properties title now contains the ‘Sent/Rcvd’ data for the message, to help identify which message it is the properties of.
17698: ENOM XML output filenames msgid not fixed length
The ‘Message ID’ contained within the filename for ENOM XML files is now always at least 6 digits.
17409: v4 XML BDR - Daily Quantities section be displayed when unselected
BDR messages in Edigas v4 (XML) now correctly respect the settings on their ‘Advanced’ screen in Available Messages.
16732: After saving Multiple entries in Recipient Details screen, new entries disappear
A number of bugs surrounding the nomination encoding grid on the Maintenance > Recipients screen have been fixed. This grid should now behave more predictably.
17123: Can’t delete recipient if Location settings exist in Nomination Encoding
Recipients can now be deleted if they have corresponding nomination encoding data. The data in question is deleted too.
17811: Timing Issue
Fixed an issue on ENOM v5.7.55 where an ugly (but harmless) error message would sometimes appear on startup if the application was running slowly.
17563: M&B screens should automatically refresh when M&B processing is complete
The ENOM+ Matching and Balancing screens now automatically refresh when the processing is complete if a refresh is attempted when there are messages waiting.
17416: GTS Joint Tests - Total imbalance on entry programme is misleading
Programme Confirmation messages no longer contain totals for each hour, as this total does not have any meaning.
12931: ENOM supports BIDACT messages for GTS
ENOM now fully supports 2 types of ‘Bid Activation’ message required for participation in the ‘Bid Price Ladder’ in the new GTS model going live April 1st 2011. The ‘Lead Time’ and ‘Direction’ are now correctly copied across from the corresponding Bid Offer Document.
16916: M&B Log should pop up if there is an error processing a message
The M&B Log will now pop up onto the screen is there is an error processing a message.
17439: [Message Rules] Sort the ‘Message Types’ combo box
The ‘Message Type’ combo box on the Message Rules screen is now sorted alphabetically.
17440: [Message Rules] Add missing message types
The ‘Message Type’ combo box on the Message Rules screen now correctly includes ALOCATTG and MAS.
17455: SURI02 SURE Lifting Request message doesn’t allow zero nomination
SURI02 messages now allow a zero nomination to be made.
17461: Values not inverted on grid view of GTS BIT
The GTS Balancing Info tool’s ‘Grid Display’ now displays the correct sign: A positive number for a long quantity, and a negative number for a short one.
17270: Numbers displayed without commas in GTS balancing tool
The GTS Balancing Info tool’s ‘Grid Display’ now uses thousand separators to make the values more readable.
17302: Response button on BDR not working
The ‘Response’ button should now work correct on netconnect control energy message, as in ENOM v5.7.45 and earlier.
16679: ENOM support for receiving ACKNOWv5
ENOM now supports receiving ACKNOWv5 messages.
16949: Change Message Rules UI to say ‘Sent’ and ‘Received’
The ENOM ‘Message Rules’ now correctly displays ‘Sent’ and ‘Received’, rather than ‘Incoming’ and ‘Outgoing’.
16951: Reduced Minimum size of Reference Columns on most grids
The minimum column width for columns on most message screens has been reduced.
16595: Holding the ‘Ctrl’ key should prevent AutoLogin
It is now possible to hold down the ‘Ctrl’ key to prevent ENOM from automatically logging in to allow logging in as a different user.
15193: Implement Edigas v4 (XML) REQEST
ENOM now supports Edigas v4 (XML) REQEST messages.
15527: Create an ‘Rules’ based system for XML generation
The ‘Enom XML’ generation now has a more sophisticated system of ‘Rules’ to control Enom XML generation. This is configured on the ‘System’ Maintenance screen.
16528: Add Autoignore rules at the Shipper Code level
Enom now supports ‘AutoIgnore’ rules at the shipper code level, rather than purely at the location level. Four rules have been automatically added, as required for Programme Matching with GTS.
16773: NAM ALOCAT’s don’t correctly decode the first hour.
ALOCAT messages in Edigas v4 (XML) as used by NAM should now correctly display the quantity value for the first hour of the day.
14140: Program Matching in Enom+
Enom can now match Programme Documents and Programme Confirmations as used by GTS from 1st April 2011, and for Joint Testing in December, January and February.
15467: Implement DELORD and DELRES messages in Edigas v4 XML
Enom now supports some Edigas v4 (XML) DELORD and DELRES messages as required by GTS.
15941: Program vs Programme
‘Program’ messages have been renamed ‘Programme’ in the user interface, in line with the GTS business documentation. The Enom XML interface remains unchanged.
14560: Moving M&B Processing to a Seperate Timer
Matching and Balancing Processing is now a separate process, and therefore should no longer interfere with message sending.
14596: Add ‘Send/Rcv Messages Manually’ Permission to Users
A new permission has been added to the Users screen, which can be used to prevent users starting the FTP process manually using the ‘Send/Rcv’ button.
15614: XML Messages from Enom should use UTF-8 instead of ISO-8859-1
Edigas v4 (XML) messages now use ‘UTF-8’ encoding, instead of ‘ISO-8859-1’.
15997: Enom should be able to read text file headers as sent by NAM
Enom can now correctly handle messages with a ‘Byte Order Mark’, such as those produced by the Energy Components system at NAM.
16080: Implement ‘SubContractReference’ for CHACAP messages from NAM
Enom now supports the ‘SubContractReference’ field for CHACAP messages, as used by the Energy Components system at NAM.
16081: CLRCON XML now has ‘number’ attribute on ‘nomination’
The Enom XML produced from a CLRCON message now has an additional ‘Number’ attribute, to make it simpler to identify which <nomination> element belongs with which <price> element.
15818: Make ‘XML Queue Focus’ configurable
The ‘XML Queue’ should no longer take focus when an Enom XML file is received. In addition, whether the screen pops up at all in response to receiving an Enom XML file is now configurable on the ‘Maintenance -> System’ screen.
16131: Changed ‘Release Notes’ menu item names
The ‘Release Notes’ menu items have had their names changed to ‘Release Notes’ and ‘Check for Upgrades’.
14430: Add XML Filename to message properties screen
The message properties screen now also contains the file name of the ‘Enom XML’ file produced.
11823: xml queue Send button needs an ‘Are you Sure’ message
The XML Queue will now prompt the user with an ‘Are you sure’ message when they try and send a message.
14108: TabbedGrids round ‘amounts’ when ‘Decimal Places’ set to 0
The TabbedGrid on most message forms should no longer round values if the ‘Decimal Places’ of the related unit is set to zero.
14226: v4 NOMINT messages output ‘dvgw_operator_type’ and ‘dvgw_shipper_type’ for non-dvgw messages
The ‘Enom XML’ generated by Enom should no longer generate a ‘dvgw_operator_type’ or ‘dvgw_shipper_type’ for non-dvgw messages
16130: Changed ‘Only Latest Messages’ SQL on Oracle to be faster
The performance of the message viewer on Oracle when ‘Only Latest Messages’ is checked has been greatly improved.
15608: BDR Response button doesn’t respect regional settings
Clicking the ‘Response’ button on a BDR v3 should now correctly copy the numbers to the SDR message regardless of the settings on the client machine.
16226: DELORDv4 and DELRESv4 messages can encode lower case characters
DELORD and DELRES messages in Edigas v4 (EDI) should no longer be able to encode lower case characters in their status field if an unrecognized status is input from the Enom XML interface.
15849: Edigas v4 (EDI) and DVGW v4 (EDI) SDTs now support nomination encoding options
SDTs in both Edigas v4 (EDI) and DVGW v4 (EDI) encodings now support the ‘Nomination Encoding’ options configured on the Recipients screen.
15936: Balancing Performance Improvements
The first stage of improving the Performance of Matching and Balancing processing has been implemented. More tweaks to come!
15937: GTSBalancingInfo tool for Joint Testing
The GTSBalancingInfo tool bundled with Enom has been updated to include a graphical display of the data, and various other options as required by Stage I of the GTS Joint Test Period.
16062: Enom supports the new format of DVGW v5 ALOCATs from Gaspool
Enom can now decode the new ALOCAT and IMBNOT messages sent by Gaspool from 1st October.
15301: v3 SDTs add ‘Direction’ column to XML Popup
Bug fixed where the ‘XML Popup’ screen for Edigas v3 (EDI) SDTs would contain an unnecessary ‘Direction’ column.
10083: ‘All Balance Summary’ no longer groups by Location
The balance detail screen now has two available views. ‘Location View’ displays a summary per location, while ‘Shipper View’ gives a complete list of every shipper at each location contributing to the balance.
13470: Implement v4 XML ACCPOS Message for NAM
Enom is now able to read the example v4 XML ACCPOS Messages given by NAM.
13471: Implement v4 XML CHACAP Message for NAM
Enom is now able to read the example v4 XML CHACAP Messages given by NAM.
13472: Implement v4 XML ALOCAT Message for NAM
Enom is now able to read the example v4 XML ALOCAT Messages given by NAM.
13208: Can send messages from XML queue without Send Permission
It is no longer possible to send messages from the XML queue if the user does not have ‘Send Messages’ permission.
13295: Enom support for v4 XML SWT/TWT messages
Enom now supports SWT and TWT messages in Edigas v4 (XML) format.
13334: Implement v4 DVGW messages in the UI as used by Wingas
SDT v4 DVGW messages as used by Wingas should now work correctly. There are two new options on the Available Messages screen to support this: “DVGW Operator Type” and “DVGW Shipper Type”, as well as the corresponding attributes in the Enom XML format.
13402: PRODOC Exit programs use Z03 for zero values
Exit program messages will now always use Z03 for encoding zero values. Entry and Trade programs will continue to always use Z02 for this purpose.
13704: Can’t prevent users from deleting messages
The ‘Delete Messages (Bulk Operations)’ permission has been renamed ‘Delete Messages’, and now also prevents users from deleting messages from the message properties screen.
13756: XML v4 SDTs use ‘SV’ instead of ‘ZDG’ in GCV <MeasurementType>
SDTs created used Edigas v4 (XML) containing GCV information should now correctly encode the GCV type as ‘ZDG’ rather than ‘SV’.
13514: Delete messages from XML Queue possible for users without send permissions
Users without ‘Send’ permissions can no longer delete messages from the XML queue.
13362: Enom behaves badly if you try to view too many messages
Enom will now give a warning if you try to view more than 3000 messages at once.
7655: EIC Column on the Location Maintenance form.
The columns on the Location Maintenance screen have been reordered so that all the ‘Code’ columns are adjacent.
13365: GridBinder performance Improvements
The Contracts, Locations and Shipper codes maintenance screens should now have greatly increased performance and respond more quickly.
12366: Redesign of the Message Properties screen
The Message Properties screen has been redesigned to better incorporate the requirements of XML messaging.
12330: Make it obvious when you have messages in the XML Queue
The Enom status bar now displays the number of messages in the XML Queue if you have some.
13282: “Response” button on REQEST received from NetConnect Control Energy
The version 3 BDR message form now contains a response button which allows the user to send a version 3 SDR as a response.
11017: [DB] Enom behaves better when disconnected from database
Enom now behaves more cleanly when disconnected from the database: It disables itself, and displays a message stating that it needs to be restarted.
12254: Enom Supports v4 XML PRODOC Messages
Enom now supports the 3 types of ‘Program’ message, and the three corresponding types of ‘Program Confirmation’ message, as required by the new GTS model going live April 1st 2011.
12932: Enom supports ACKNOW messages for GTS
Enom now supports the sending of an ACKNOW message in response to a ‘BIDACT’ (Bid Activation) message.
13076: Enom Login Box Change / Feature request
The Enom login screen now also displays the name of the Enom you are trying to log in to.
13098: Rename the concept of ‘APERAK’ in the UI
‘Hide APERAKs’ on the message viewer has been renamed ‘Hide Acknowledgement Messages’, and the term ‘APERAK’ has similarly been replaced on most other forms where it appears.
10491: Enom Support for v3 “BWF”: Buyer’s Weekly Forecast Notice
Enom now supports Edigas v3 ‘BWF’ messages, ‘Buyer’s Weekly Forecast Notice’, which in some situations corresponds to the Edigas v2 BWR message.
12821: Make Enom poll ‘Folder’ message boxes instantly
‘Folder’ inboxes should now be polled as soon as a file is dropped in, rather than waiting for the poll interval.
12929: Enom supports CLRCON messages for GTS
Enom supports the 3 types of ‘Clearing Confirmation’ message required for the new GTS model going live April 1st 2011.
12930: Enom supports BIDDOC messages for GTS
Enom supports 2 types of ‘Bid Document’ message required for participation in the ‘Bid Price Ladder’ in the new GTS model going live April 1st 2011.
12933: Enom supports the POS and SBS web services for GTS
Enom now comes bundled with a tool called ‘GTSBalancingInfo.exe’, which allows you to check your POS and the current SBS as required by the new GTS model going live April 1st 2011. This currently only supports the requirements of certification, but will be expanded going forwards.
12748: Units screen now supports ‘Currency’
The Units screen in Enom now supports ‘Currency’ units, initially configured with just one unit: ‘Euros’.
12902: 3 main issues from usability testing.
The grids on message forms in Edigas version 3 or higher now display <Add> on the ‘new line’ row to make it clearer that you can add a new line by editing that box.
Also the ‘Click ‘+’ to add a new tab’ message on these forms has been changed to ‘Click ‘+’ to add a new location’, to make it clearer what the purpose of a tab is.
12975: Status Bar ‘Unsent’ messages doesn’t include ‘To Be Forwarded’ ones.
The status bar ‘Unsent’ count now includes messages which are waiting to be forwarded, as well as messages which haven’t been sent to their initial recipient.
12411: BDRv3 Daily messages cannot send zero values
Version 3 BDR messages using daily values now allow you to send zero values.
12450: [Codelists] Add support for ‘System Operator Code’ (ZSO)
A new codelist has been added for shippers, locations, NAD codes and UNB codes: ‘Edigas (ZSO)’. This uses ‘Edigas’ codes, but with the ‘ZSO’ qualifier instead of ‘321’ or ‘ZEW’.
12760: Entering a value on a tabbed grid causes flickering
Some ‘flickering’ of the tabbed grid used on message screens has been fixed. The message screens should now run more quickly and smoothly.
11946: [XML Messaging] Bulk Operations Changes
The text on the bulk operations screen have been changed to reflect support for XML messages.
11947: [XML Messaging] Changes to the Recipients Screen.
The Recipients screen ‘Message Defaults’ now use the ‘Message Format’ box instead of the default version, DVGW and content type boxes, making the screen simpler.
12500: DVGW messages have configurable ‘Operator Type’ and ‘Shipper Type’
DVGW messages from XML now support different header NAD qualifiers (As used by Wingas). This is currently only supported from the XML interface.
12502: Units screen allows you to rename a unit to an existing one
The Units screen previously allowed you to rename a unit to have the same name as an existing one, causing problems. This should no longer be possible.
12470: Deleting Available Message templates
The available messages screen will now ask you for confirmation before allowing you to delete a template.
11446: [Msg] New Message: ‘SWR’, version 3. Sellers Weekly Request Response
Enom now supports version 3 ‘Sellers Weekly Request Response’ messages (SWR).
11866: [EDI] Codelist Defaults for Locations and Shippers not configured in Enom.
Shipper and Location codes passed in from External systems by the XML interface which are unknown to Enom will now be assumed to be in their target codelist, instead of being encoded as Edigas codes.
11945: [XML Messaging] Message Properties Window Changes
The message properties window has been redesigned to include a display for XML messages, and a quick way to view the Enom XML for a message has been added.
11948: [XML Messaging] Changes to the Available Messages Screen
The available messages screen now combines the DVGW option with the version number and the content type to form a single ‘Message Format’, making the configuration of a message simpler.
12034: Enom Supports v4 XML NOMINT and NOMRES messages
Enom now support v4 XML SDTs and TDTs, as required from 1st October by GTS.
11969: ‘Point’ in message viewer should be ‘Location’
The ‘Point’ on the message viewer has been renamed ‘Location’ to be consistent with the rest of Enom.
11998: Tabbed Grid reference columns resize
Reference columns on tabbed messages grids should now automatically resize, allowing some of the longer line contract references and shippers to be read.
11283: Large values not fully visible in cells
Quantity columns in message grids should now automatically resize as the numbers get larger, allowing large values to always be read.
11342: REQRES v3 to support RFF+Z11 and RFF+CT
Version 3 SDR messages now support both RFF+Z11 and RFF+CT as required by NetConnect. The new option is configured on the available messages screen using the ‘Contract Ref Is Group’ option.
10460: Always output direction in XML for ‘OR’ encoding on v3 NOMINT and NOMRES messages.
Messages encoded with a ‘Positive Input or Output’ encoding should now always output the direction in the XML, allowing for positive and negative zeros to be distinguished.
11788: SDAv3 to support other quantity qualifiers
Version 3 SDA messages now support both ‘MOP’ and ‘Maximum quantity’ quantity qualifiers, corresponding to Z50 and ZAR in the EDI.
11505: Added support for ‘From’ email address in System
It is now possible to configure the ‘From’ email address which Enom uses when sending email notifications.
6340: Option added to XML to pop-up or automatically send individual messages.
A new attribute was added to the Enom XML to allow a particular message to be automatically sent, overwriting the default on the recipient.
10840: Clear up Enom Close.
Enom should now close more quickly and smoothly.
11013: Proxy IP Address supports up to 100 characters.
Proxy IP Address on the System screen now supports up to 100 characters, up from 20.
8347: XML Message Queueing for Popup Messages
The new ‘XML Queue’ feature replaces the old ‘XML Pop-up’ in Enom. If an Enom XML file is not automatically sent, then it is placed in an XML Queue. It can then be viewed from any Enom, sent, edited in the UI or deleted.
8730: “Compare Messages” screen closes after clicking “Ignore”
The Compare Messages screen now closes when the ignore button is pressed.
9834: Shipper Codes Combo should be sorted alphabetically.
Shipper Code Aliases are now sorted alphabetically, instead of sorting by the underlying code value.
9380: [M&B] Balance Detail: Sorting by column
It is now possible to sort the data on Balance Detail by double-clicking on Column headers.
10468: Improved behaviour of SchemaChecker against Oracle 9i
The Enom SchemaChecker now handles indexes properly on Oracle 9i.
9457: [EDI] Enom support for a non-numeric ICR
Enom now supports the use of non-numeric ICR numbers, as used by some systems which are not fully compliant with the Edigas MIG
9531: [M&B] Balance Detail: Enom supports Shipper Alias
If Shipper code Aliasing is configured, they are now used on the Balance Detail screen in Enom+
9363: [EDI] Development of BDEW 2.0b APERAK
Enom now supports BDEW 2.0b APERAK messages as used by NCGVHP.
9102: [UI Msg] Support for BDEW CONTRL Messages.
Enom now supports BDEW 1.3b CONTRL messages as used by NCGVHP.
9408: [UI Msg] Added “Z35” to BWR Decode to mean “Forecast Quantity”
Enom now supports the use of QTY+Z35 (Forecast Quantity) in Buyers Weekly REQEST notices.
9526: TINv3 message does not contain a total column in the UI
The TIN v3 message now has a ‘Total’ column in the Enom display.
9281: [UI Misc] Allowing the # character in Contract References
The ‘#’ character is now allowed in Contract References
8915: Location Code Maximum Length increased to 50
The maximum length for a Location Code is now 50 characters
9324: [Msg] ALOCATv4 to support 14G and 12G to mean “Average”
ALOCAT v4 messages now suppport 14G and 12G codes as “Average” values.
9335: Support for DVGW TDPA Messages.
NetConnect and Gaspool send DVGW-spec TDPA messages, which are now supported by Enom.
9343: [XML] Changing the name of files output by XML
Enom now uses a different system for naming XML files out of Enom:<Template Name>_<Message ID>_<FullFileName>.xml e.g: HCN_234_NOMRES.1.xml
9011: [Codelists] Add “EAN Number” to Maintenance->Shippers
Enom now supports the use of EAN numbers for Shippers, as well as EIC and DVGW codes
9012: New features in ALOCAT v4
Enom now supports the new DVGW ALOCAT messages used by Gaspool and NetConnect.
9254: Enom supports IMBNOT messages from NetConnect
Enom can now decode and display IMBNOT messages from NetConnect.
9108: [UI Msg] Implementing NetConnect CONTRL messages
Enom now supports CONTRL messages from NetConnect
9104: [Codelists] Add DVGW and EAN codes to Locations
Enom now supports the use of EAN and DVGW codes for Locations.
9018: [Codelists] Change “Use EIC UNB” to allow DVGW and EAN UNB tags on Recipients
Enom now supports the use of DVGW and EAN codes in the UNB segments for both incoming and outgoing messages.
9157: [UI Misc] Password boxes do not accept $
It is now possible to use the ‘$’ character in passwords in Enom, including logins for FTP.
9008: use_eic_locations XML attribute value is ‘Vrai’ or ‘Faux’ on French Regional settings
The use_eic_locations attribute of the <message> tag in Enom XML used ‘Vrai’ or ‘Faux’ on French systems. That is incorrect behaviour as it is not region-independent. This has been changed to ‘True’ and ‘False’.
3528: Matching and balancing to include contract references
Enom now supports the use of line contract references when creating a custom balance.
8348: Database Schema Diagnostics\Checking
Enom will now automatically validate the database schema after an upgrade, and will warn the user should there be any differences between its database and what Enom expects.
2270: Ability to create a custom balance using shipper code
Enom now supports the use of shipper codes when creating a custom balance.
8676: Use EIC codes for Locations in Edigas v3 NOMINT and NOMRES
Enom now supports the use of EIC codes for Locations in Edigas v3 NOMINT and NOMRES messages. This is required for NetConnect messages after the 1st of October.
8148: [Fluxys Transit] Enom supports Nomination Priority for Fluxys v4 NOMINT (SDT, SWT)
Enom now supports nominating with Priorities for v4 NOMINT (SDT, SWT) messages. This is for changes to the Fluxys network later this year.
8426: XML Log being overwritten not appended
Earlier versions of Enom had a bug causing the XML Log to be overwritten rather than appended. This is now resolved.
6639: Statfjord nomination notification changes
Changes to the SURE messages have been made so that Statfjord nomination notices are supported again.
7730: Indexes on Message table
Indexing has been improved on the Message table for customers using Jet\Access databases resulting in improved performance.
7783: REQRES v3
REQRES v3 messages have been implemented (SDR).
8131: [EDI] v4 CDTs to use encoding option in recipient’s screen
v4 CDT (Hub) messages now use the encodin options specified on the Maintenance->Recipients screen. This is required for Huberator on the 1st of October.
7227: [M&B] Add TimeZoneAdjustment for Matching and Balancing (to change hours correctly)
A Time Zone Adjustment can now be specified for Balancing. For balancing to work messages must all be for the same time zone.
7711: [UI Msg] SDA v3 to support daily amounts
The SDA v3 [AVAILY] message now supports daily amounts as well as hourly profiles.
7845: NOMRES v3 supports EGT003 in UNH
NOMRES v3 (TDT, TMN, HCN, HDT, DSR, TWT, WSR) supports EGT003 in UNH.
7687: [UI Msg] Added v3 AVAILY Messages
Edigas v3 AVAILY (SDA and SWA) messages have now been implemented.
6400: Rewrite Available Messages screen.
The Maintenance->Available Messages screen has been redesigned so that it is clearer and easier to use.
2852: New Units Maintenance screen
The Maintenace->Units screen has been redesigned so that it is clearer and easier to use. This new design highlights the Parent-Child relationships that the units have, and the difference between ‘Hourly’ and ‘Daily’ units.
5135: [UI Misc] Ability to copy and paste values into NOMINTs
It is now possible to use Ctrl-V to Paste into NOMINT messages (SDT, CDT, DSN, SWT etc). Rows\Columns can be pasted from Excel spreadsheets for example.
5715: “Matching” screen in ENOM+ to also look at “processed by adjacent tso” values
The “Matching” functionality in Enom can now match against different confirmation statuses as provided by the TSO.The Matching Response Status is now visible on the Matching screen as well as Compare Messages.
6787: [Build] Grid display conflict between CodeRunner and Enom
There was a conflict between the grid components used in CodeRunner and Enom. This has now been resolved.
7251: Added ‘Entry\Exit’ to Recipient-Location Encoding options
‘Entry\Exit’ has been added to the Location encoding options on Maintenance->Recipients.Entries are encoded using QTY+Z02, and Exits QTY+Z03.
7113: Enom to support use of ‘ZGW’ and ‘305’ recipient codelist (DVGW) in UNB segments.
If ‘ZGW’ or ‘305’ are used in the UNB (service header) segment of an incoming message, Enom will look up the Recipients as appropriate.A new field 'DVGW Code' has been added to the Maintenance->Recipients screen for use with the 'ZGW' qualifier.
7121: Modifications to decoding of TIGF ALOCAT messages to allow extra QTY+3 at LIN level
TIGF ALOCAT messages can have an extra QTY+3 specified at LIN level which was rejected as invalid previously. This check has now been removed in line with changes made by TIGF.
2835: Sorting shipper codes in message grids [Version 3&4]
It is now possible to sort nominations on messages by shipper code etc by double-clicking on the column header.
7002: Changes to NOMINT Message Encoding options settings (+ve-ve, Input And\Or Output)
The ‘Encode As’ option is now on the Recipient, along with the Recipient-Location Encoding options, and no longer on Available Messages.1) Sending messages via the UI (either Resend, Create New, or XML Popup): Enom ALWAYS goes to the recipient and uses the Encode Method specified there. If there is a specific method set for a location, then that overrides the recipient option. This means that how a previous message was encoded (when clicking Resend), or anything specified in the XML options, is overridden by the UI settings. 2) Sending messages via Autosend XML: Enom first looks to the Recipient Encoding option for defaults. Then, if in the XML the use_qualified_values attribute or the always_input_output attribute is set, then that overrides the Recipient Encoding option. Then, for each location, Enom looks first to the Recipient Location Encoding, and if that is set explicitly then the XML message level settings or recipient encode option is overridden by that. If it is specified at line level within the XML, then that overrides all.
7017: Sorting shipper codes in message grids [Version 2]
It is now possible to sort the nominations on messages by double-clicking on the column headers.
3786: Delivery Confirmation - New ‘DELCON’ Message
GMSL can now send ‘Delivery Confirmation’ messages to shippers to inform them when their messages have been successfully uploaded to the intended recipient.Enom will then change the status of the messages in the Message Viewer to 'Delivered' as appropriate.
6068: NOMINT and NOMRES with CVs per shipper code
It is now possible to send a CV for each shipper code in v3 NOMINT messages.This is only available via XML, not the Enom UI.
6527: Save button does not work in maintenance\system\xml tab
The ‘Save’ button on the Maintenance->System screen was not always correctly saving changes made to some of the fields on the ‘XML’ tab.This has been fixed.
6631: Allow Enom installer to configure program installation folder
At the request of a customer, it is now possible to choose the installation folder to be something other than “<Program Files>\Enom"
6670: Support for version 4 HDT’s in ENOM+ (Part 1)
Edigas v4 HDT messages from Huberator are now considered as ‘Confirmed’ values for the purposes of Matching and Balancing in Enom.Note: They are not truly the confirmed amounts, only matched.
6099: Option to disable XML generation for Outgoing messages (‘Boomerang’ effect)
An option has been added to enable\disable the generation of XML for Outgoing (from me) messages.If this is disabled then XML will not be generated when you send a message. This takes care of what some users describe as a 'Boomerang effect' in their external systems.
6495: Unexpected error occurs if XSL path is missing ‘' at end of path
There was an unexpected error occuring when attempting to view messages using the HTML viewer if the XSL path did not have a ‘' at the end of it.The '\' is now automatically added.
6290: XML generation of dates on non-english regional settings uses local setting instead of colon.
XML generated by Enom should be region-independent. In previous versions, the seperator character between parts of a time (e.g. “13:01:32”) would use the Windows setting. It is now fixed to use a “:” regardless of the region.
6060: Shortcut Encryption\Decryption security improvements
The Maintenance->Encryption option is now only available when the user logged into Enom has “User Maintenance” priviledge.The option to decrypt encrypted text has now been removed.
6115: ALOCAT v4 decoding non-specified hours within message period as zero’s
When decoding an Edigas v4 ALOCAT, Enom would display a zero for unspecified hours within the period. It now correctly shows a blank.
6190: IMD segments encoded with ‘ZEW’ instead of ‘321’ in Edigas v4 DELORD messages.
In previous versions of Enom, when creating an Edigas v4 DELORD message, Enom would use ‘ZEW’ as the codelist qualifier in IMD segments, instead of ‘321’. This has now been fixed.
6030: Addition of Location for CV in Edigas v4 NOMINT\NOMRES messages (for Fluxys)
The ability to specify a GCV Location has for Edigas v4 NOMINT and NOMRES messages has been added.A "location" attribute has been added to the <cv> tag in the XML, and a drop-down list has been added to the Enom user interface on the Edigas v4 SDT, TDT, SWT and TWT screens. This maps to a LOC segment in the first LIN loop of a message, after the MEA segment.
5631: Support for Fluxys\Zebra v4 DELORD, DELRES (TIN, TMC, TCN, TWM)
Enom can now encode and decode Edigas v4 DELORD and DELRES messages for exchange with Fluxys. This includes the TIN, TMC, TCN and TWM messges.
5334: Fluxys v4 Message Support
Enom now supports Edigas v4 NOMINT, NOMRES, ALOCAT and IMBNOT messages to and from Fluxys and Huberator.
3902: Prodis Storage Matching and Balancing
Matching and Balancing can now process Prodis Storage messages (PSN and PSR).
4136: BALL message viewer inside Enom
Incoming BALL messages can now be viewed from within ENOM as HTML using an XSL stylesheet.Double clicking on the BALL message will now display the message in HTML format.
4712: Fluxys APR message UNH change 1st October 2008
Fluxys changed the content of the UNH segment in APR messages on 1st October 2008 and changes were made to Enom in line with this.Enom previously warned the user that it was not as expected, but this has now been changed so Enom expects the new format. Old APR messages will now raise a warning that the UNH is not as expected. The message is decoded and displayed correctly regardless of the warning.
5030: Message parsing performance enhancements
The EDI parsing component in Enom has had changes made to improve performance reading large messages.For example, a client with a beta test version has reported that a very large monthly allocation message that previously took 10 minutes to decode now takes under a minute.
5312: Enom supports 14 character ICR numbers (for Fluxys v4)
Enom successfully processes and has been tested with incoming messages with 14 character ICR numbers. This is required for processing Fluxys v4 messages.
5072: ENOM can now read NOMRES messages from NCGVHP (missing IMD\Status)
NOMRES messages from Net Connect VHP had no IMD segment to specify the confirmation status, meaning the messages could not be read in Enom.Enom now assumes a status of 'Confirmed' where the IMD segment is missing, so the messages can be read and successfully processed.
4882: Configuration options to support Edigas v4\DVGW
A number of configuration screens have been changed in Enom to support Edigas v4, DVGW messages, and EIC codes.Maintenance->Recipients - EIC code added for each recipient - 'Code' renamed 'Edigas Code' for clarity - 'My Shipper Code' re-named 'From NAD Code' - 'To NAD Code' split out from 'Code' - Allow user to specify EIC codes for NAD codes - Send using EIC codes in UNB\Service Segments - Default 'Use EIC Locations' for XML\Available Messages Maintenance->Available Messages - Allows choice of v4 and DVGW message standards - Allows user to choose EIC codes for NAD codes - Allows user to choose EIC codes for Location codes Maintenance->Locations - This now has an EIC code for each location
4883: Enom supports use of EIC codes in UNB segments
Enom can now successfully process messages with EIC codes (and a mixture of EIC and Edigas codes) in the UNB segment.Enom can also create messages using EIC codes in both the 'To' and 'From' parts of the UNB segment.
4993: Enom supports the use of EIC Codes in header NAD segments (v4 messages)
Enom now supports the use of EIC codes in the header NAD segments in Edigas v4 messages, for both sending and receiving messages.You can use a mixture of EIC and Edigas codes for the 'To' and 'From' NADs.
4994: Enom supports the use of EIC codes for Locations in v4 messages
Enom now supports the use of EIC codes in LOC segments in Edigas v4 messaes, for both sent and received messages.
3341: Lesser rule on Matching screen - Enom+
Matching and Balancing only takes into account ‘Scheduled’ [ZCF] and ‘Confirmed’ [16G] amounts from confirmation [NOMRES] messages.
4131: Ontras APERAK
Enom can now accept APERAK messages from Ontras, and marks messages as ‘Accepted’ if appropriate. The ‘Expect APERAK’ functionality can also be used if Ontras agree to send ‘Accepted’ APERAKs.
2672: Single hour nominations for BWRs
Single hour nominations functionality is added for V2 BWR message. (see case 2162 for detail)
1912: Problem with ACCPOS XML
ACCPOS XML now contains the UTC date\time as well as the local, and the attribute is correctly named.
3830: Resending SURE Messages
Default date resending options now apply to SURE messages.
3479: RWE Storage - Sending TDT messages
When sending an outgoing TDT message, Enom was not using the correct Encode method (Input\Output or Net). This has been fixed.
2832: GRTgaz NOMRES
GRTgaz NOMRES message has been extended to contain 31G values
3238: ENOM+: Specify contract reference when configuring a network balance
You can now specify a contract reference when configuring a balance (e.g. a network).IMPORTANT: When upgrading to this release, you must Reprocess your Matching and Balancing Data for Todays Gas Day (for the next week), using the Message->Bulk Operations screen.
3350: TDT v3 can display more nomination response statuses.
TDT and TWT NOMRES messages can now display ‘Accepted by TSO’ and ‘Accepted by Adjacent TSO’ values as well as ‘Confirmed’ and ‘Processed by TSO’ etc. The grids have been arranged onto seperate tabs for each status.
3293: SDT Message with RFF+CT in LIN
NOMINT (SDT, SWT etc) and NOMRES (TDT, TWT etc) messages can now have a Contract Reference for each nomination in the message (ie at LIN level).
2410: ENOM+ Auto Ignore
New feature in ENOM+ that allows users to configure recipient-location-message type combinations where a matching record will be automatically flagged as ‘ignored’.The auto ignore applies to nominations where a confirmation is not expected or confirmations where a nomination is not made. If either of these two rules are broken the matching record will not be automatically ignored.
2525: Location level encoding
For V3 NOMINT Message templates it is possible to override message ‘encode as’ options at recipient/location level. Location ‘encode as’ options are configured in recipient maintenance.
2982: Resending Daily Messages
It is now possible to configure enom to specify the default gas day when resending daily messages. The options are ‘Today’, ‘Tomorrow’ or ‘Ask’ where ‘Ask’ will prompt the user to select between ‘Today’ or ‘Tomorrow’ after selecting resend.
2343: Fuel gas message
ENOM now supports a Fuel gas message (FGO)
2401: FTPS Support
Enhanced support for ENOM using FTP over SSL (FTPS).
3152: TCN daily values
ENOM can now display daily values for TCN messages
3093: ENOM+ Division by zero bug when calculating journey shrinkage.
Journey shrinkage is now limited to being greater than or equal zero and 1ess than one. The upgrade script will change to zero any existing journey shrinkages outside this range.
3077: Enom+ Matching - EON VHP (Lesser rule on v3 HCNs?)
For Matching and Balancing purposes, v3 HCN messages will be matched on the scheduled value.
2462: Version 3 NOMINT/NOMRES, Shipper/location ‘flow direction’
Version 3 NOMINT/NOMRES messages now handle ‘flow direction’ values per shipper/location. This allows the user to configure and specify non-aggregated INPUT and/or OUTPUT values.
1585: Viewing TIGF ALOCAT messages
It is now possible to view ALOCAT messages from TIGF.
1728: ENOM+ Additional sorting
Additional sorting has been added on the matching screen. It is now possible to order all columns within the gas day by double-clicking the column headers
2992: Contract reference data duplicating on Oracle platform
Contract ref values are saved and displayed in upper case. The Contract ref field on the ‘Available Messages’ screen has been changed to only allow entry of upper case characters.
2695: v2 BDR Response
It is now possible to create a v2 SDR message in response to a received v2 BDR message
2426: LGAZ message support
ENOM supports LGAZ message between FLUXYS and Shippers.
2637: Database connection string encryption
The database connection string is stored in the ENOM shortcut. For Oracle and SQL Server databases this is a security risk since the database username and password are visible. It is now posible to encrypt the connection string. In the shortcut if the connection string is encrypted then /e command line argument must be used. There is a maintenance screen in the ENOM application which allows users to encrypt and decrypt entered text.
2673: Possible to enter non-numeric daily value on v2 BWR
Single hour nominations functionality is added for: V2 BDR and SDR messages. V3 BDR messages (see case 2162 for detail)
2749: ENOM Not working with Oracle 8
There was an issue found where later releases of ENOM were not working correctly with Oracle 8. This issue has now been resolved.
2100: Shipper display alias
ENOM allows shipper codes to have a ‘display alias’. Each shipper code can have a display alias, these have to be unique and different from any existing shipper code value. The shipper maintenance screen has been updated to allow entry of display alias values. There is also a system parameter (maintained on the general tab of the system maintenance screen) which allows the display to be switched between actual codes and aliases.The following message screens have been modified to handle displaying shipper aliases: V2 CDT, SDT, HCN, HDT V3 CDT, SDT, DSN, DSR, HCN, TDT, TMN
2162: Single hour nominations
Currently ENOM copies across nomination values for the remaining hours of the day. It is now possible to just enter a value for a single hour. Entering a nominated value followed by the figure “h” will result in only that hours value being populated.This functionality is available for the following V1/V2 Message templates: CDT, DWM, HCN, RDC, RWM, SDA, SDT, SWA, TDC, TWM, TWR This functionality is available for the following V3/V4 Message templates: CDT, DAS, DSN, HCN, SDT, SMT, SWT, TCN, TDT, TIN, TMN, TWM, TWT, WSR
2558: Error creating XML when hourly values not specified in EDI
XML files are now generated with zero values for hours where no values are specified in an EDIG@S message
2285: XML Interface - ‘from_nad’ and ‘to_nad’ attributes if specified must have a value
The XML interface validation has been increased to ensure data integrity for matching and balancing purposes. The XML interface has two optional attributes ‘from_nad’ and ‘to_nad’. These attributes if supplied in the XML must not be empty, a value must be included.
2411: ENOM+ Matching messages using contract ref
ENOM+ Added matching functionality to allow messages to be matched using the message contract reference. This handles the case where there are two or more messages for the same recipient at the same location and the only difference is the contract reference. The user can configure to match on: 1. Recipient/Location/all contract refs 2. Recipient/Location/specific contract refs
2564: ENOM+ should not process TMN messages for matching and balancing purposes
TMN messages are not processed for matching and balancing purposes.
2459: Balancing screen is showing zero balance but double clicking shows an imbalance
Bug fixed on the balance detail screen. Values are now shown for each distinct configured journey identified by the contract ref.
994: GRTgaz Allocation messages
Edig@s V4 GRTgaz Allocation message available in ENOM
2184: ENOM+ Configuration auditing
ENOM+ stores and displays audit dates for matching and balancing configuration records. These can be used to identify whether incorrect mismatches could be due to an incorrect old configuration.
1712: ENOM+ shipper NAD mapping
ENOM+ It is now possible to map shipper NAD codes for message matching purposes.
2108: ENOM+ multiple shipper code balancing at hub
ENOM+ - More than one shipper code can be used to balance a hub.
2124: SURE/SEGAL - SURO02 and SURO05 multiple contract values
SURE/SEGAL - SURO02 and SURO05 messages have been modified to handle multiple contract values.
1508: ENOM+ Shipper Mapping functionality
ENOM+ has shipper mapping functionality. This allows the matching process to handle the case where the shipper on the confirmation is different to the shipper code provided on the nomination. It also allow a <blank> shipper code to be mapped to an actual shipper code.
1981: Improvements to database upgrade for Access
Improvements to Access database upgrade process, including progress reporting for ENOM users.
2187: ENOM+ complex message matching error
The matching process was not correctly matching complex messages where the location appeared many times within the body of the message. This has been resolved.
2073: Print preview missing hours
When printing messages, in some cases the hourly values at the end of the 2nd page were not printed. This issue has been resolved, values will be wrapped onto a 3rd page.
2050: Version 3 BDR does not have the option for an internal shipper
V3 BDR Edig@s messages have the option to include an internal shipper.
1715: TAQA - DSN internal shipper vs DSR shipper
ENOM+ Matching - When a message has only ‘internal shipper codes’ and no ‘shipper codes’ these codes will be used to match messages.
1506: ENOM+ All Balances (II)
ENOM+ Balancing - To handle rounding issues the number of decimal places used for balancing is configurable. This is entered on the system maintenance screen when selecting to enable Matching and Balancing functionality.
2105: Hide tab totals grid on V3 HCN GUI
The tab totals grid is not displayed for the V3 HCN message.
2136: SURE/SEGAL Messages (O02 and O05) - Unit will be different for dry and wet gas qty.
SURE/SEGAL Messages (O02 and O05) - ENOM allows different unit identifiers to be entered for each quantity.
2123: Deleting a Network leaves Hub shipper codes hidden
If you have Shipper codes set up as Hub shipper codes and then delete the Network which the shipper codes are in they will still appear in the drop-down on the CDT, but you can’t see them anywhere in Maintenance->Shippers.Deleting a network will now delete all the shipper codes in that network as well.
2003: ENOM - V3 CDT + HCN change of shipper codes in BY, SE segments
V3 HCN - Bugfix - NAD+BY and NAD+SE had the incorrect shipper codes. They were the wrong way around. This is now resolved
Option added to Maintenance->System to enable matching and balancing functionality, and to select balancing unit.Maintenance->Matching and Balancing screen added to configure balancing, journey shrinkage and hub codes for use by matching and balancing functionality.
819: Message Viewer - Display locations
ENOM displays list of locations for version 3 messages in the Message Viewer window.
820: Message Viewer - List latest messages.
ENOM allows the user to list only the latest message of a type, location and recipient for a gas day.
821: Apply shrinkage for Fluxys network
When messages are being matched, ENOM will apply shrinkage correctly for the Fluxys network, as set up by user in Maintenance->Matching and Balancing->Journey Shrinkage.
822: Apply the lesser rule
When messages are being matched, and more than one quantity for the same shipper and location appears in a TDT message (they will have different quantity types such as “confirmed” and “processed by adjacent TSO”), the lower one is to be used for matching (lesser rule applies).
825: Highlight different gas days
In grids where rows are displayed for more than one gas day and in date order, the cell backgrounds will be in alternating colours such that data for one gas day can be distinguished easily from that for another.
813: Display matching status
ENOM will display the matching status of locations.
814: Compare messages (EOD only)
Double-clicking on a row on the Message Matching screen opens a Compare Messages screen. The user can select a nomination and confirmation message from the history of relevant messages.The screen shows the EOD nominations for all the shippers on the messages, and highlights any mismatched rows. Transporter flags from the confirmation message are displayed if present. The user can toggle showing numbers with shrinkage (fuel cost) applied or not.
815: Compare messages (Hourly)
Double-clicking on a row in the Compare Messages screen brings up a comparison of the hourly nominations for that shipper code. Any mismatches are highlighted.
816: Balance Detail
A new Single Balance screen has been added, which allows users to view their nominations in a network, sub-network etc. Nominated and Confirmed values are available, as well as shrinkage (fuel cost) calculation applied.
817: All Balance Summary
A new All Balances screen has been added, which allows users to view their EOD nominated and confirmed for all their balances (networks, sub-network etc). The screen shows the values for the selected gas day and the day ahead.
917: Number format
In all matching and balancing screens, numbers are formatted using the number of decimal places specified in Maintenance->Units for that unit.
795: Unable to see negative sign on GRTgaz confirmations
Users have not been able to see if a nomination is negative if the number has 8 digits on TDTs from GRTgaz, as the number over-runs the column width.In Maintenance->Units it was specified that kWh\day should have no (0) decimal places, but Enom was showing 2. The number of decimal places for the specified unit was not being shown, hence the overrun. This has been fixed, so the number is formatted correctly and the -ve sign is now visible.
1748: ENOM+ configuration
When matching and balancing configuration is modified the user is alerted that they should re-process matching and balancing data using bulk operations.
1699: Incorrect status of “Matched”
ENOM+ matching was incorrectly matching nominations to confirmations when the confirmation message only contained a subset of data from the original nomination. This has been resolved.
1928: V3 CDT - Centrica testing bug
Bug fixed when trying to zero a ‘sell’. a zero value is treated as positive and so was not being sent in the EDI as a zero ‘sell’, this is resolved by always sending both a ‘buy’ and a ‘sell’
879: SURE/SEGAL messaging
SURE/SEGAL Messages available in ENOM. The following 3 messages are implemented: SURI02, SURO02, SURO05.
1515: ENOM+ ignore mismatch
In Matching and Balancing, mis-matched and pending messages can be updated as “not requiring attention” and removed from the list of messages requiring attention on the message matching screen.
1761: Balance Details Screen - hourly totals recalculated on form resize
1768: Encountering error decoding edigas when viewing a version 3 BDR created through the GUI.
1771: Unable to decode v3 BWR created through ENOM GUI
1836: TCN V3 Message not displaying ‘confirmed’ grid
1686: ENOM+ Problem re-processing M&B data
1689: ENOM+ incorrectly determining latest message when matching
1690: Message Viewer - filter Latest Message Only
1696: Compare fails (ENI UK)
1700: Unique key contraint violation attempting to import the same xml message twice
1742: Reprocess messages is automatically setting some to ignore
1760: Balance Detail Screen - Totals don’t line up
1581: Error opening matching and balancing when no balances are configured.
1654: No range checking when entering the Hour Adjustment for a recipient
1691: TDT Screen
1202: Edig@s V3 HCN support
Edig@s V3 Hub Confirmation Notice (HCN) available in ENOM
1584: ACCPOS XML
The XML generated for EDIG@S V4 ACCPOS messages includes the date and time as UTC. The new attribute is called ‘start_dts_utc1’
1676: Error viewing latest messages
1681: Highlighted All Balance Summary
1694: Looks like case is important with oracle upgrade script 1.52 - 1.54.
1725: Oracle - viewing only latest messages doesn’t work
1680: Tooltip on Balance Detail screen
1624: Error importing TWT from xml.
1620: Error editing date when re-sending a message in enom.
1582: All columns on the Matching and Balancing maintenance form should be left justified.
977: Message alert rules
Added functionality for users to specify e-mail receipt notification rules for received messages. On the Notifications tab of the System options screen the user can configure to receive an e-mail when a new message is received from any recipient, or they can define specific recipient and message type combinations.
1155: ENOM+ multiple shipper support
ENOM+ can handle the case where 2 or more shippers use the same ENOM. Where the shippers send and receive messages with the same TSO, matching will take this into account and balances can be set up for each shipper independently. [Note: matching and balancing data will need to be deleted and re-generated using the bulk operation facility]
914: Bulk operations
New ‘Bulk Operations’ screen allows users to perform a number of functions for messages that apply to a range of Gas Days. The user can choose to process all the messages, or just the latest that apply. Functions include : - (Re)process matching & balancing data - delete matching&balancing data - export message xml - delete messagesAccess to the delete messages function is controlled at user level. There is a check box on the user maintenance screen to control a users access to this function.
1660: Language settings
Using ENOM Local settings a user can specify the display language or set ENOM to use the machines regional settings to determine the display language. English and German languages are supported.
961: NOGAT view average
The message screen displays both the total and average of the hourly values for each message row. This enhancement applies for the following messages: NOGO02, NOGO03, NOGO06, NOGO07, NOGO13, NOGO18, NOGI02, NOGI06, NOGI12
1645: Error printing Account Position Report (APR) Message
Error printing Account Position Report (APR) Message fixed
1505: ENOM+ rounding issues when calculating balances
1598: Where message matches notification rule, no email is sent and message viewer does not show information for message.
965: Files not registered properly on Vista
1625: Columns being obscured in NOGO02 messages.
1173: Location name mapping
Locations can be configured to have aliases for matching and balancing purposes
1201: Edig@s V3 CDT support
Edig@s V3 Customers Daily Transfer Notice (CDT) available in ENOM
1343: TIGF NOMRES
TDT v3 modified to accept messages from TIGF.
986: Edig@s V3 SMT support
Edig@s V3 Shippers Monthly Transit Forecast Message available in ENOM
667: All information disappears when re-feeding a NOGI06 xml file
The XML ouput generated by ENOM for a NOGI06 was incorrect. The XLM document node <hour_items_bool> is incorrect and has been changed to <hour_items>
932: Alerting emails not sent after ENOM errors occurred
FTP performance issues have been improved. Issue with local temporary directory not being cleared has been resolved.
1221: Add User error
User Maintenance screen updated: Added date calandar control for selecting Account Expiry Date. Added validation for required user details when adding a new user. Improved screen layout to make editing a user less cumbersome. Screen title updated with “password valid days” when user information is saved.
1191: XML Processing user feedback improved
User feedback has been improved for XML (and Legacy .OUT file) import into Enom. If there are any errors processing the messages, more detail is now provided in the diagnostic .LOG files.You can now also see the XML processing LOG in the Enom UI. There is a status-panel labelled 'XML' on the right hand side of the bottom of the Enom main screen. Double-click on that and the XML log will pop up.
675: ACCPOS message
v3 ACCPOS message has been added.