Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08

From 41.1 to 40.1 From 105.1 to 104.1

From version 104.1

edited by Erik Bakker
on 2023/04/13 14:30

Change comment: There is no comment for this version

To version 41.1

edited by Erik Bakker
on 2022/11/07 16:35

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--195 - Easter Party
++187 - Integration Sponsor

Content

@@ -2,98 +2,142 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
++**Hi there, eMagiz developers!** With this release we will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version.
--== **Release properties** ==**
++== **Store - Next phase** ==
--With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
++This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.
--As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
++[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
--{{video attachment="release-blog-easter-party--release-properties.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
--{{info}}The following considerations need to be taken into account when using this functionality:
--* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
--* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
--* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
--* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
--* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
--* There is a maximum of twenty-six ‘property’ releases. (twenty-six letters of the alphabet)
--* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
++== **New eMagiz Mendix Connector** ==
--== **API improvements** ==
++With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
--//__Improved auto-generated error handling__//
--When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
++{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
--//__Switch default message format__//
--We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
++== **Flow version restore** ~* ==
--//__Re-using elements in gateway message__//
--This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
++On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect.
--//__Improved naming of API operations when adding integrations to Create__//
--Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
++[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
--== **3rd generation improvements** ==
++{{warning}}Note, that the following restrictions apply when restoring to a previous version:
++  * Changes made on definition and transformation level are **not** restored
++  * You will **not** be able to restore to any flow version that was created before October 17th, 2022
++  * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
++  * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
--//__Update of the static alerting engine__//
--In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
++== **Feedback items ** ==
--//__Add "Data pipeline" functionality__//
--This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Fix related to the debugger__//
--This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
++//__Redirect to the Manage Dashboard from your model home page__//
++Directly navigating to the Manage phase (of any environment) will automatically redirect you to the error message Dashboard, as that is the landing page of the Manage phase.
--{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
++//__Readable entry of a SpEL expression in a flow component__//
++As of now, the input field for your SpEL expression in certain flow components will dynamically expand when you enter a large SpEL expression. This will improve the readability of your solution and will make it easier to enter and validate your SpEL expressions.
--//__Improved migration process__//
--This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
++[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
--//__Deployment plan change__//
--In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
++//__Keep Create and the Create Phase release in sync__//
++Previously the Create and the Create Phase release might have become out of sync. As a result, comparing a release to the Create Phase release could yield confusing results. With this release, we have made several improvements to prevent this from happening.
--{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
++//__Mask password values in the unused properties overview__//
++All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview.
--== **Feedback items ** ==
++//__Press Enter to Search for properties__//
++With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview.
--//__License Tracker improvements__//
--With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
++//__Styling update on tag selection on integration level__//
++With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly.
--//__Ability to view the message definition for a topic__//
--Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
++//__Enter to close automated flow testing pop-up__//
++Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button.
--//__Restricted access for uploading custom certificates to endpoints__//
--To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
++//__Improved naming of downloaded Event Streaming keystore__//
++When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client.
--== **Bug fixes ** ==
++//__Pop out on the Traces tab within Flow Testing__//
++In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow.
--//__Improved deletion behavior for enumerations__//
--To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
++//__Sorting User Management__//
++As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview.
--//__Prevent "async" api operations__//
--With this release, we have removed the ability to select the "async" option when the default message format is API Management.
++//__Improved warning on passthrough API operation__//
++Most users forget to configure a backend API operation or switch to the transformation option when configuring an API operation in Capture and Design before moving to Create. This is then blocked, leaving users confused about what to do next. Therefore we introduce an additional warning in the Design phase that lets you know that your configuration of an API operation is not yet finished. This way, you can correct it **before** trying to move it to Create.
--//__Importing a response definition broke the request definition__//
--Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
++//__Improved update functionality of Swagger file when changing data model__//
++Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly.
--//__Removing a flow does not update the API "all-entry" anymore__//
--When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
++{{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}}
--//__Stop deployment plan when a property is missing__//
--Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
++//__"Disapprove and go to environment"__//
++Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
--//__Cap stack trace of error messages and log entries__//
--To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
++//__Improve readability of API Gateway operations in Create and Deploy__//
++When you have a lengthy name for your API Gateway operation, it becomes tough to discern the various API Gateway operations in your landscape. To alleviate this problem, we have added a tooltip functionality that will show the full display name when hovering over the API Gateway operation.
++//__Add Topic Storage information to License Tracker__//
++On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz.
++
++[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
++
++//__Add Compatibility check when importing store items__//
++We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening.
++
++//__Show dependencies between support objects__//
++As of now, when you click on a support object, all related support objects will also be highlighted in the same overview. This makes it easier to see the relationship between support objects and components and among support objects.
++
++//__Improve rendering of validation definition when using multiple namespaces__//
++With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end.
++
++//__Improved help texts on next-generation runtime functionality across the portal__//
++With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime.
++
++== **Bug Fixes** ==
++
++//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
++With this release, we have made several improvements to what feedback is given to the user when moving a flow from Create to Deploy for the first (upon creating your first definitive version). This will ensure that no confusing pop-ups will be shown that are incorrect and only confuse the user further.
++
++//__Show information in the Exception of error messages overview__//
++With this release, we have resolved the bug plaguing this page. As a result, you will again see information on this page when there is information to show.
++
++//__Improve styling of cron trigger configuration pop-up__//
++The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again.
++
++//__Prevent flow editing locks in specific situations__//
++There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release.
++
++//__Generate property value empties the runtime selection__//
++With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
++
++//__Make sure nothing of a system message is editable from your exit__//
++Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices.
++
++//__Prevent users without view rights from seeing a weird screen in those phases__//
++With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently.
++
++//__Name of starting point of the flow test is incorrect__//
++With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct.
++
++//__Audit Trail on User Management could break__//
++When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue.
++
++//__Progress bar in the license tracker is shown twice__//
++With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
++
++//__Compare flows with support objects in the new flow designer__//
++We have fixed a bug related to support objects that prevented you from comparing two flows when one was built in the latest, and the difference was constructed in the old flow designer.
++
  == **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:
--* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
--* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
--* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
++* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
++* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
  == **Key takeaways** ==

Changes for page 210 - Deployment Delights

Summary

Details

Navigation