Feature Removal Deprecation: FNZ Studio 2025
This article summarizes the deprecation and removal of features with FNZ Studio 2025.x (see Products page for the latest released version).
When upgrading to FNZ Studio 2025.x, this means:
- Removed features – Issues related to the removal of features must be addressed before upgrading to your FNZ Studio 2025.x version.
- Deprecated features – Issues related to the deprecation of features do not require any action before upgrading to FNZ Studio 2025.x. Deprecated features will continue to work as normal in FNZ Studio 2025.x, as we plan to remove them in minimum two years since the date of the release that deprecates the item (e.g., not before 2027 for features deprecated in FNZ Studio 2025.x. This time frame gives you time to address the necessary changes by following the recommended actions. See the Deprecation section below for more details.
Related Documentation Resources
- Deprecation and removal principles: Feature Deprecation and Removal in the 'System Administration: Upgrade Principles' article.
- Feature removal and deprecation in supported Platform versions can be found in legacy documentation
Removal of Features
The following tables list features removed in FNZ Studio 2025.x.x versions and the recommended actions to replace them. Issues related to feature removal require action before upgrading to the current FNZ Studio 2025.x.x version.
Removed Configuration Properties
| Removed Feature | More Information |
|---|---|
|
Configuration property |
These features were deprecated in Appway 11. |
nm.admintools.toplevelentries. |
This feature is not functional and the corresponding code is also removed. |
nm.pdfrenderer.dyndoc.legacy.renderer
|
This property, which was used to re-enable the legacy PDF Output Table renderer, was deprecated in Appway 11. |
nm.install.time; nm.system.uuid |
This property was deprecated in Appway 11. |
nm.cluster.eviction.datahandles.maxsize; nm.cluster.nearcache.valuestores.maxsize |
This property was deprecated in Appway 11. |
Removed Script Functions
| Removed Feature | More Information |
|---|---|
SCRIPTFUNCTIONURL
|
This Script Function was deprecated in versions previous to Appway 7. |
CustomProcessLogEntry
|
This Script Function was deprecated in versions previous to Appway 7 and is no longer functional. |
GetProcessStatistics
|
This Script Function was deprecated in versions previous to Appway 7 and is no longer functional. |
|
|
This Script Function was deprecated in Appway 11. |
|
|
This Script Function was deprecated in Appway 11. |
|
|
These Script Functions were deprecated in Appway 2022.1. |
|
|
This Script Function was deprecated in Appway 11. |
|
|
This Script Function was deprecated in Appway 10. |
|
|
This Script Function was deprecated in Appway 10. |
|
|
These Script Functions were deprecated in Appway 11. |
Removed Extension
| Removed Feature | More Information |
|---|---|
| COBExtension |
This COBExtension was deprecated in Appway 9. Please, contact Support if you need assistance. |
Other Removed Features
| Removed Feature | More Information |
|---|---|
| Investment Selection Tool (IST) | The Investment Selection Tool (IST) has been removed, since its functionality has been replaced with the table capabilities available in App Tasks. No migration is available. |
Deprecation of Features
The following tables list features deprecated in FNZ Studio 2025.x.x versions and the recommended actions to replace them. Issues related to the deprecation of features do not require immediate action before upgrading to the current FNZ Studio 2025.x.x version. However, we suggest that you start considering the recommended actions described for each deprecated item.
Deprecated Script Functions
| Deprecated Item | Recommended Action | Why We Are Deprecating |
|---|---|---|
CREATEPROTOTYPE
|
There is no direct replacement. To get a "null-initialized" object you can create a new Data Class instance and set all its properties to null | This Script Function was used in deprecated extensions or in combination with old Script Functions. |
EXECUTIONCONTEXTATTRIBUTE
|
No usages have been found, therefore there is no replacement abvailable. | This Script Function should not be used in Solutions. |
HTTPGET
|
Use The signature and behavior of the functions have not changed. The |
Http-related functions were reorganized into the Http: namespace for easier access. |
HTTPPOST
|
Use Http:Post instead. The signature and behavior of the functions have not changed. The Migration:MigrateFunctions (see below) can be used to replace usages of the old function with the new function. |
Http-related functions were reorganized into the Http: namespace for easier access. |
HTTPREQUEST() and related Primitive Type HttpRequest |
Usages are replaced as follows:
|
All the listed usages of this Script Function are replaced with new Script Functions in the |
HTTPRESPONSE() and related Primitive Type HttpResponse |
Usages are replaced as follows:
|
All the listed usages of this Script Function are replaced with new Script Functions in the HttpResponse namespace since they returned non-serializable Primitive Types. |
SCREENCONTEXT() and related Primitive Type ScreenContext |
We recommend using the new Script Function Screen:IsAdminMode() to replace calls to SCREENCONTEXT().isAdminMode(). |
This Scrip Function returns a non-serializable Primitive Type, and is seldom used. |
EXECUTIONCONTEXT() and related Primitive Type ExecutionContext |
There is no specific recommendation. | This Scrip Function returns a non-serializable Primitive Type, and is seldom used. |
Deprecated Extensions
| Deprecated Item | Recommended Action | Why We Are Deprecating |
|---|---|---|
| ExternalAuthenticator Extension | There is no specific recommendation. |
The extension uses Primitive Type |
Appendix: Migration Tool for Automatic Migration to New Functions
To keep your Solution up to date and make sure it uses the recommended functions and methods, we strongly advise performing an automatic migration of functions and method calls. This is done through the Automigrator Tool described below:
- Execute
Migration:MigrateFunctions, and pass the Package ID as an argument, as the function executes migration on a per-Package basis. Example:Migration:MigrateFunctions('ClientOnboarding')migrates all occurrences of deprecated functions in the Client Onboarding Package. In detail, the migration function performs the following actions:- The migration function finds all Business Objects using deprecated functions within the given Package.
Example – The Client Onboarding Package contains the Script Function Business Object "Test", which uses the deprecated
USERROLES()function:Function ClientOnboarding:Test(String $value) : Nothing Begin USERROLES(); End - The migration function replaces all occurrences of deprecated functions with the new namespaced functions; an uncommitted version of each Business Object with migrated code is created.
Example – The Script Function Business Object "Test" has been modified by the migration function to replace the deprecated function:
Function ClientOnboarding:Test(String $value) : Nothing Begin User:CurrentUserListRoleIds(); End - The migration function returns a list of Business Object IDs that have been migrated.
Example:
String[ClientOnboarding:Test]
- The migration function finds all Business Objects using deprecated functions within the given Package.
Example – The Client Onboarding Package contains the Script Function Business Object "Test", which uses the deprecated
- Based on the list of migrated Business Objects, review the changes to the Business Objects and commit them.