Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

This article describes the principal changes of Amazon Templates.

The Template download section can be found at this page


Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.



TOOL Amazon S3

Support defining parameters automatically through Metadata Link

When drag and dropping an S3 Metadata Link on S3 Tool, related parameters will now automatically use the values from the Metadata.

You can now leave the "Secret Key", "Access Key Id", "Bucket Name" and "Region" parameters empty, they will be filled by the Metadata Link.

You can still, of course, define manually the values in the parameters if needed, they will override the Metadata Link values.



REJECT Redshift

Rejects rules with warning severity level fixed

Reject rules which are defined with "warning" severity level in Metadata should not be removed from the flow and should be loaded in target table.

Previous version of the Template was unexpectedly removing rejected rows with "warning" severity level from the flow, which was wrong, and which has been fixed from this version.

Rows which does not fulfill a rule which has been specified with "warning" severity level will not be kept in the flow and loaded into target table.


Alternate Key check was not performed on correct columns

Alternate Keys checks were performed on all unique keys instead of Alternate Keys defined in Metadata.




Recycling of previous rejects fixed

When using the option to recycle the rejects of previous execution an extra step is executed to add those previous rejects in the integration flow.

This step had several issues which avoided it to work properly and which have been fixed in this version.

Moreover, possible duplicates while retrieving those rejects are now filtered using DISTINCT keyword.




Suggest a new Article!