Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 98.1
edited by Erik Bakker
on 2023/04/13 08:47
Change comment: There is no comment for this version
To version 53.1
edited by Erik Bakker
on 2022/11/21 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +188 - Close Encounters
Content
... ... @@ -2,85 +2,74 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**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.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **Release properties** ==**
7 +== **3rd generation runtime bolstering** ==
8 8  
9 -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-generation.WebHome||target= "blank"]]
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
10 10  
11 -== **API improvements** ==
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
12 12  
13 -//__Improved auto-generated error handling__//
14 -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.
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
15 15  
16 -//__Switch default message format__//
17 -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.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
18 18  
19 -//__Re-using elements in gateway message__//
20 -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.
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
21 21  
22 -//__Improved naming of API operations when adding integrations to Create__//
23 -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.
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
24 24  
25 -== **3rd generation improvements** ==
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
26 26  
27 -//__Update of the static alerting engine__//
28 -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.
29 +== **Exportable Release Audit** ~* ==
29 29  
30 -//__Add "Data pipeline" functionality__//
31 -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.
31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
32 32  
33 -//__Fix related to the debugger__//
34 -This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
35 35  
36 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Works **only** for releases that are promoted and made active on **Production**
37 + * You will **only** see changes made during the **current** calendar year
38 + * On the first of April all objects of the **last** calendar year will be **removed**.
39 + ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
37 37  
38 -//__Improved migration process__//
39 -This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
40 -
41 -//__Deployment plan change__//
42 -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.
43 -
44 -{{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}}
45 -
46 46  == **Feedback items ** ==
47 47  
48 -//__License Tracker improvements__//
49 -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.
43 +We have also solved other feedback items besides the flow designer's critical updates.
50 50  
51 -//__Ability to view the message definition for a topic__//
52 -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.
45 +//__Improved naming convention on Store related pages__//
46 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
53 53  
54 -//__Restricted access for uploading custom certificates to endpoints__//
55 -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.
48 +//__Press "Enter" to search on multiple pages__//
49 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
56 56  
57 -== **Bug fixes ** ==
51 +* Deploy → Deployment Plan
52 +* Deploy → Properties → History
53 +* Deploy → User Management → Roles
54 +* Manage → Error Messages → Error Messages
55 +* Manage → Error Messages → Flows with Error Messages
56 +* Manage → Error Messages → Exceptions of Error Messages
57 +* Manage → Log Entries
58 +* Manage → Alerts
59 +* Manage → Triggers
60 +* Manage → Tags – Cant find (only Gen2)
61 +* Manage → Notifications
62 +* Manage → Notification Settings
63 +* Manage → Data Usage → History
64 +* Manage → Code mappings → All tabs
58 58  
59 -//__Improved deletion behavior for enumerations__//
60 -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.
61 -
62 -//__Prevent "async" api operations__//
63 -With this release, we have removed the ability to select the "async" option when the default message format is API Management.
64 -
65 -//__Importing a response definition broke the request definition__//
66 -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.
67 -
68 -//__Removing a flow does not update the API "all-entry" anymore__//
69 -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.
70 -
71 -//__Stop deployment plan when a property is missing__//
72 -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.
73 -
74 -//__Cap stack trace of error messages and log entries__//
75 -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.
76 -
77 77  == **Fancy Forum Answers** ==
78 78  
79 79  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:
80 80  
81 -* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
82 -* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
83 -* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
70 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
71 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
72 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
84 84  
85 85  == **Key takeaways** ==
86 86