Weekly Upgrade Announcement 8/29/22
Posted: September 2nd, 2022, 3:01 pm
Platform Upgrade Schedule
On Tuesday September 6th, the IDE/DV/QA environments for Platform1, Platform2, Platform3, and Platform4 will be upgraded to DesignTime Revision 2381 and RunTime Revision 1046. Platform1, Platform2, and Platform4 will begin their upgrade at 3:00PM CST with an expected completion time of 3:30PM CST. Platform3 will begin its upgrade at 12:00PM CST with an expected completion time of 12:30PM CST.
On Thursday September 8th, the PD environment for Platform1, Platform2, Platform3, and Platform4 will be upgraded to RunTime Revision 1046. Platform1, Platform2, and Platform4 will begin their upgrade at 3:00PM CST with an expected completion time of 3:30PM CST. Platform3 will begin its upgrade at 12:00PM with an expected completion time of 12:30PM CST.
DesignTime
Revision 2379: Database Maintenance Fixes
Revision 1036: Alarm Email Improvements
On Tuesday September 6th, the IDE/DV/QA environments for Platform1, Platform2, Platform3, and Platform4 will be upgraded to DesignTime Revision 2381 and RunTime Revision 1046. Platform1, Platform2, and Platform4 will begin their upgrade at 3:00PM CST with an expected completion time of 3:30PM CST. Platform3 will begin its upgrade at 12:00PM CST with an expected completion time of 12:30PM CST.
On Thursday September 8th, the PD environment for Platform1, Platform2, Platform3, and Platform4 will be upgraded to RunTime Revision 1046. Platform1, Platform2, and Platform4 will begin their upgrade at 3:00PM CST with an expected completion time of 3:30PM CST. Platform3 will begin its upgrade at 12:00PM with an expected completion time of 12:30PM CST.
DesignTime
Revision 2379: Database Maintenance Fixes
- The below issues have been resolved:
- When a user has a space on any side of a value when using the bulk add feature the column fails to get created properly. Excess whitespace is now trimmed out before created the table.
- When a user adds a new column of length MAX the column gets created with a length of 1. The MAX column length is now interpreted correctly.
- When a user adds new columns the columns fail to get added. The logic now properly loads the column to add it to the table.
- Table promotion is only adding the first new column to existing tables. Now all columns get added on promotion
- The IDE pages are only showing the Connector App as the Language App even when an application has a different Language App set. The current language app is now loaded per application.
- Check the forum post for more info.
Revision 1036: Alarm Email Improvements
- The alarm emails now include the application and tenant that the alarm is going off for to help inform the user of where the disconnect is happening.
- When a user logs out of a page and tries to use a button on another page that is secured the page will now forward to the login page.
- On page postback the select control with the following display types fail to properly reload the control if the control had values selected, then a postback happened, and then all values were deselected and another postback happens. The PreSelectValue attribute has been removed on postback since the values should stay the same.
- Some control properties with HTML Encode off are throwing the following error: "An item of type 'Element' cannot be constructed within a node of type 'Attribute'. The property values are now changed to model data before inserting it into the page HTML.
- The MVC_View_Html table now has the LanguageId column updated to the proper column type and length.
- Certain properties like the Parameters property of the Widget are failing to load them properly because of HtmlEncode. Code has been added to unescape properties that can get saved as XML.
- If a page has an open window and the page is set to be translated, then the opened page/window throws an error. Code has been added to inform the opened window to be translated.
- If the widget control is hidden on page load, then it will not be rendered when the control is unhidden. Logic has been added to include the widget controls in the render in these circumstances.
- In MVC applications if there is no default button set for a textbox control no buttons will get clicked.
In the text area type of the textbox control if there is no default button set then hitting enter or shift + enter will result in a new line. If there is a default button set then hitting enter will call the default button and hitting shift + enter will result in a new line.