The oldest version, which can be upgraded to Intrexx 19.03, is Intrexx 7.
2. Upgrade to Intrexx 19.03
With Intrexx 19.03, you receive a completely revised version of the low-code
platform, Intrexx. We have taken extensive measures to make your portals
even safer, such as a mandatory switch to HTTPS, password encryption with
the PBKDF2 process and much more. We have simplified the architecture of web
connectors in relation to security and future updates (load balancing,
TLS offloading, flexibility).
The complete overhaul of the business logic with Intrexx 19.03 offers a whole
range of new benefits when designing applications.
Many changes had to be made to the existing APIs and interfaces to implement
all of these changes. We make every effort to stay as backwards compatible
as possible but we cannot always guarantee that everything can be migrated
as there was not an API for these in the past.
Therefore, we recommend that you plan your upgrade carefully and to perform
it in a separate test environment first. Plan in a timeframe for any potential
adjustments. Your Intrexx Partner is happy to support you here.
Please create a backup of your portal server and database before upgrading.
Deactivate any virus scanners for the duration of the upgrade process.
Please note that a portal export alone is not a sufficient backup.
Please perform the upgrade on a test system to begin with and not
within a live environment right away.
Support for the implementation of new authentication methods
The ability to fully use browser APIs (e.g. krypt APIs)
Changed data protection policies (privacy by default, privacy by design)
Messages from modern browsers about missing encryption are prevented
Before upgrading an Intrexx Portal Server on Windows with Integrated
Authentication and upstream Internet Information Server, please make
sure to check whether you have an HTTPS certificate.
The following components need to be installed:
When using Microsoft SQL Server, an error will seldomly occur when displaying tables.
A reason for this may be that the table is sorted by a long text field that the
Microsoft SQL Server cannot perform. The error can be fixed by changing the
sorting of the table and then saving the application afterwards.
(no longer compatible with the option to edit entries in
free layout tables).
This method returned access to any FuncPart within the browser window.
All FuncParts within the browser window can be identified with this.
allows you to identify all FuncParts within a container.
Additionally, FuncParts from the free table can be filtered out.
However, this is not necessary in most cases as this concerns scripts
that are performed in the context of a page. As soon as any HTML element
from an application page is referenced, the FuncPart can be retrieved via
Closing tooltips by clicking on the Cancel button can cause problems if
a target page is defined for the button and the tooltip should only be
closed. The solution is either to remove the target page or to transfer
all parameters for the target page.
The expert flag for the checkbox preselection has been removed and replaced by the
Support for webservices in the browser (display elements, assign fields when saving, web request)
has been removed. It is better to implement these via the web service action
in the Processes module called by Userworkflowevent, for example.
The expert attribute "customdefault" no longer triggers a dependency when a page
is loaded. Until Intrexx Version 19.03, "customdefault" was populated via
value is already provided by the server. If the removed triggers results in
the connected event listeners not being triggered, the dependency can
be triggered in the onload event of the page.
Will be completed removed in a future version. Until then, users are advised to use
instead. If is absolutely necessary to use a popup, users can define a custom
renderer via ix.loader.api (callback function) and then load the new content
in a popup via window.open.
End of life for all browsers that do not fully support ECMA Script 5.
Slider: The vertical slider has been removed without replacement.
This affects: upActionControl, upTextActionControl and upImageActionControl.
The IX API provides the following alternatives: ix.ajax, ix.loader and upSimpleAjax.
have been standardized and simplified.
The following methods are available:
public async checkValidity(): Promise<ValidationInfo>
public async reportValidity(): void
The following methods have been removed or are deprecated:
After the upgrade, existing portal pages will be converted into the new format.
However, the conversion cannot take into account whether a portlet took up
multiple columns. These settings need to be applied in the grid after the
Portlets in application pages:
As the portlet framework works completely asynchronously, any request values
must be transferred to the integrated pages via the portlet container.
This cannot be performed automatically during the upgrade. Therefore, if filters
of integrated portlets access request values, you should focus your attention
on this point.
Load pages from within portlets
If buttons with the
"Open in current window"
setting open pages from within a portlet,
then the page will be opened in the portlet. If the page contains a lot of elements, all page elements
may not be displayed in some cases. The
"Open target in main window"
setting is much more suitable in this case as the loaded page will be displayed in its entirety.
Velocity in view tables to access the
respective table data record:
Scripts that use $drRecord do not
work anymore because $drRecord is no longer resolved at this point.
Instead, the Velocity part should be transferred to a
"data-" attribute, for example, and
ActionControl in a view table with the following script call:
"PlainPasswordLoginModule" has been removed. It can be replaced like-for-like
editcontrols/datetime/UpDateTimeMainEditControl: "toLocalDateString()" removed,
'upDateControl.toLocalFormat()' can be used instead
Intrexx challenge-response authentication is no longer supported.
This means changes need to be made in the deployment and for web service
We recommend only providing web services with TLS encryption
Web service requests from clients - especially Intrexx clients - that use challenge-response
authentication need to be reconfigured to log in with username, domain and password
When switching to TLS, it may be necessary to provide the consuming clients
or portals with the SSL certificate of the Intrexx server
The class "de.uplanet.lucy.server.auxiliaries.RemoteAuthProxy", which was used
by only a few customers, has been removed. If there are customers who still
need this class, it can be reactivated upon request.
The callable "DSPassword" has been removed
The method "DsucUser#changePassword(JdbcConnection, int, byte)" has been removed after 4 years of deprecation
Session management via the URL parameter "rq_SId" is no longer supported
For reasons of security, there are only HTTP-only cookies with (in the case of HTTPS)
with a set secure flag