241 - Wild West
Hi there, eMagiz developers! In this release, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new runtime image containing a much-needed improvement regarding deployment executions when working with state generation and code mappings, along with various improvements in our underlying code.
Property Comparison
As of this release, you can compare properties between two releases via the compare properties functionality in Deploy -> Releases. This allows you to quickly compare which property values have been changed, altered, or deleted. On top of that, it provides information on which user executed this change so you can confirm with that person whether that is expected. Note that this functionality only works on activated releases, so it should be utilized from an audit perspective and cannot be used to validate property changes in preparation before activating the release.
New Runtime Image
As announced on our status page, we will release a new runtime image as part of this release. The main changes within the runtime image are
- Updated our Java runtime version from Java 17.0.10 to Java 17.0.13. This is primarily a security update involving cipher suite changes, as outlined in the remarks below.
- Updated Spring boot from version 3.2.2 to 3.4.1.
- We have marked the OAuth2 grant type ‘password’ as deprecated, which will be removed with the introduction of OAuth 2.1. It can still be used, but a warning will be given when configured. To prevent the need to migrate to another OAuth grant type in the future, we encourage you to switch to one of the other grant types.
- The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed.
Please find out more here.
Hackathon Efforts
Minor Changes
Improved copy behavior for Q&A questions
To simplify the act of copying a link to a question, we have slightly altered the current functionality so that you can copy the link to your clipboard with a single click. We have also ensured that the UI is consistent across the platform.
Removal of remark field when creating a new integration
We have removed a free text field called "Remarks" when creating a new integration, as that field was rarely used and was not visible across the platform after you had pressed "Save."
Display name character limitations better shown
In eMagiz we have set limits on the allowed length of various input fields. One example is the display name given to components within the Flow Designer. We now inform the user of how many characters (out of the 64 characters maximum) can be defined by the user when the user exceeds the limit of 64 characters.
Improved information when deleting message defintions from Create -> Resources
We now inform the user which specific transformation, including relevant metadata, prevents you from deleting a message definition under Create -> Resources.
Bug Fixes
Emptying the name of a system in Capture is not allowed anymore
We have ensured that you can no longer empty the system name of an existing system in Capture and subsequently store the system.
Improved resilience when creating and editing message definitions
Various changes have been introduced on the message definition level that improves the platform's resilience in cases where users become so enthusiastic that they click many times to execute the same action. With this, we prevent a user from causing duplicates or errors when executing the same action repeatedly.
Custom examples for request messages are shown in Swagger
With this release, we also ensure that when you define a custom example message in your Swagger UI, it will be displayed for both request and response messages.
Improved input validation on multiple runtime option
You will see a nice validation error when activating the "multiple runtimes" option without filling in a value in the "multiple runtimes" input field.
Correct naming of browser page for Create -> Components
We have correctly named the browser page when navigating Create -> Components.
User confirmation improvements when deleting wiretaps
We have improved the necessary user confirmation when deleting wiretaps within the Flow Designer. This way, you only need to confirm the deletion once instead of twice.
Property description updates
You can now update the property description even when an existing property description is already present. Do note that the property description is related to the property placeholder and is, therefore, the same across environments.
Naming improvement auto-created components API Gateway
When adding a new API Gateway passthrough operation to your Create phase, we now have a new default name given to the "REST Template" support object that aligns with other components in the flow.
Queue Browser - Switch environment
When switching between environments A (i.e., Test) and B (i.e., Acceptance), the queue browser overview is refreshed correctly, so we show the correct information, avoiding confusion.
Minor Changes
Disallow use of hyphens in technical names across the platform
For new systems, message types, machines, tenants, and models, hyphens are no longer allowed in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
Deployment Plan improvements - Execution
We have improved the stability of the deployment plan execution for all models running on the current-generation architecture.
Bug Fixes
Loading bar addition when adding a system
We have added a loading bar when a user adds a system. This indicates to the user that the action is being handled, and as a result, there is no need to click again.
Create -> Add Integrations improvements
With this release, we bring two improvements to the removal functionality under Create -> Add Integrations.
- Users can untransfer a flow even when there is a property attached to the flow.
- When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
Environment Template improvement
We fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
Fancy Forum Answers
As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
Key Takeaways
Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
- If you have questions surrounding our Program Increment Planning, please get in touch with productmanagement@emagiz.com
- If you have feedback or ideas for us, talk to the Platypus
- Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these.
- Clear your browser cache (Ctrl + Shift + Del)
- Check out the release notes here
- Start thinking about how the license tracker can aid your development
- Start thinking about major, minor, and patch
- Keep making great integrations
Let's stay in touch and till next time!