Page History

...

ViewFoundSet/ViewRecord is now more inline with the normal foundset api when it comes to editing/failed records (including the new validation framework)

The builder is improved to detect better methods links to elements that are not really correct (pointing from 1 form to the other), so it can be that you suddenly have errors like:

Property "onActionMethodID" from element "btnBuildNow" in form "jobConfiguration" is linked to an entity that does not exist.

Tomcat is updated from 8.5.50 to 8.5.57 (internal in developer and the one in application_sever)

...

a small fix in the RestWS if a "application/x-www-form-urlencoded" was send to the server then the content was not a JavaScript array
It is now, but anybody that worked around this (contentparam.get(0) instead of contentparam[0]) needs to undo this workaround.

If you still use the application server directly instead of WAR then the web.xml file from application_server/server/ROOT/WEB-INF/ must be adjusted to not get an exception on startup:

 <filter>
      <filter-name>SeparateSessionFilter</filter-name>
      <filter-class>org.sablo.filter.SeparateSessionFilter</filter-class>
      <init-param>
      <!-- Separate sablo request from non-sablo (web client), only invalidate session when both are invalidated -->
         <param-name>paths</param-name>
         <param-value>/rfb/:/websocket/:/solutions/:/spec/:/resources/</param-value>
      </init-param>
   </filter>

    <filter-mapping>
        <filter-name>SeparateSessionFilter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>

Remove those lines (are on different locations in the web.xml file). This is also true for the 2020.2.1 LTS and 20206.1 releases.