This Release Bulletin provides a brief description of any enhancements or new features as well as bug fixes that are included in version 2025.5.
Rollout schedule
-
Version 2025.5 rolls out to the ‘preview’ ring on May 16-17, 2025, and to the ‘production’ ring on June 21-22, 2025.
-
System variables are supported in the email subject and body through the $__SYS() syntax. Other variables can also be utilized through the
$__STORE() and $__MAP() syntax.
What's New
Email Notifications
Jobs can now be configured to send email notifications on success or failure.
-
Email settings can be configured in the System Utilities section of the Connect UI – these settings are ‘global’ and they apply to all jobs in the system.
-
System variables are supported in the email subject and body through the $__SYS() syntax. Other variables can also be utilized through the $__STORE() and $__MAP() syntax.
-
The ‘From’ email address is of the form - “EcoSys Connect <ring>EcoSysConnect@smartplantcloud.net” where <ring> is Production, Test or Development.
-
Emails are sent only for the main job (not sub-jobs)
-
Email settings can be overridden at an individual job level, otherwise they inherit global email settings
-
A new column indicates whether email notifications have been overridden at the job level.
Email Processor
This processor can be embedded into jobs and utilized independently of the email notifications feature.
-
Configuration is similar to that of email notifications.
-
It sends 1 email irrespective of the number of entities it processes.
-
If used within an Iterator, it will send an email every time the Iterator runs.
-
Spring Expression Language (SpEL) syntax can be used as a criteria to decide whether an email should be sent or not.
Custom Messages in the Logger Processor
The Logger processor is typically used to print the entity in the data pipeline (in JSON format). Custom messages provide a mechanism to control what gets printed instead.
Example
If the custom log message configured is as follows:
Debug: The Job Parameter Project=$ PARAM(Project) has a WBS=$ MAP(wbs)
Then, for each entity passing through the pipeline, the messages printed may be of the form –
Debug: The Job Parameter Project=ABC has a WBS=ABC-1 Debug: The Job Parameter Project=ABC has a WBS=ABC-1-1 Note that variables can be used within the log message.
OData: Manage Navigation Links
Navigation links are URLs that can be used to set/retrieve an entity or a collection of entities related to the current entity via a navigation property.
-
Links can be created within OData Processors and Writers using the ‘Configure Links’ button – links can be created to object references or to inline .
Connect supports the creating navigation links with batch operations. Check the ‘Batch Update’ option under ‘Configure Links’ to enable this.
OData: Custom Input Parameters
Typically, the metadata returned by an OData service completely defines the schema of the entities involved. But if the metadata is incomplete, or does not define the required schema at all, input parameters can be custom-defined to fill that gap.
-
Click on the “Customize Input Fields” button (usually in the Advanced section of the Connect component) to start the process.
-
Fields can be defined either as an object/container that can carry other fields or as a ‘primitive’ (non-object)
-
Primitive fields have strong data types
-
Here’s an example of a container field called ‘Interfaces’ with a string attribute called ‘ISPFDocumentMaster’ being added to the existing metadata
EcoSys Version Required
This release requires the following EcoSys versions:
>= 9.2.02.131
>= 9.3.03.103
These versions are the hot fixes.
Variables
No new variables have been introduced in this release.