Known Issues in Quantum Fabric V9
Analytics
- Download of a report in the excel format fails due to a colon (: ) in the name of the report.
For more information about this feature, click here.
Engagement
- It is not possible to add a title for Rich Push Template even though the option to save Rich Push Template with title is provided.
Identity
- OAuth Provider type is not displayed under Data Panel > Project Services.
- In the Manage App Store Users window, the App Store link navigates to the wrong link.
- It is not possible to import more than 100 different groups via CSV import of users.
Quantum Fabric SDK
- An invalid SSO error occurs and the login fails even after providing the correct user ID and password.
Console
- Issue with GET verb mapping and its variant mappings for SDO Object Services
In case of SDO Object Services, in the GET verb mapping the user can also configure extra variant mappings like
getByPk
,getbatch
, etc.In MobileFabric V7.x or Fabric V8.x:
- Any changes made in the GET verb mapping override the changes made in the individual variant verbs like
getByPk
andgetbatch
. - While generating the service definition during publish, the mappings made in the variant verbs are ignored and are instead stamped with the mapping of the GET Verb.
When you upgrade from MobileFabric V7.x or Fabric V8.x to Quantum Fabric V9:
- Any changes made in the GET verb mapping do not override the changes made in the individual variant verbs like
getByPk
andgetbatch
. - While generating the service definition during publish to runtime, the mappings made in the variant verbs are respected and are stamped.
Check the following post the V9-GA upgrade:
- Verify the individual GET Variant mappings on the Visual Editor / XML definition and validate them.
- Any changes made in the GET verb mapping override the changes made in the individual variant verbs like
Installer
- Issue
Advanced push notifications are blocked for the combination of a JBoss app server and an Oracle database.
Workaround
Add the
ojdbc8.jar
file to thekpns/war/libs
directory, and then restart the server.
- Issue
On certain system display resolutions, the Windows Installer UI may get distorted and you may face difficulties in proceeding with the installation.
Workaround
You must lower the scaling factor and/or resolution of your system and restart the installer.
- Issue
Upgrade from 8.2.1.3 GA to V9.x gets reverted.
Workaround
Before the upgrade, execute the following SQL statement from admin database
For MySQL
------------ delete from <admindb>.schema_version where script = 'V62.1__konyadmin-mysql-8.2.0.0.sql';
For SQLServer
--------------- delete from <admindb>.schema_version where script = 'V62.1__konyadmin-sqlserver-8.2.0.0.sql';
For Oracle ---------- delete from <admindb>.schema_version where script = 'V62.1__konyadmin-oracle-8.2.0.0.sql';
-
Issue: While upgrading from MobileFabric 7.3 to Quantum Fabric V9 and then upgrading to a version after V9, the upgrade fails due to the following error:"java.sql.SQLSyntaxErrorException: Table 'prefixidglobaldbsuffix.schema_version' doesn't exist".
Workaround
To avoid this issue, perform the following step:
- Delete the idglobaldb schema before upgrading to the version later than V9.
-
Issue: When you setup Quantum Fabric (On-Premises) on WebSphere Liberty Profile using the Command Line Installer (CLI) the publish of the Storage application fails. The failure occurs when you enter the database type input in upper or mixed casing. The storage database type is a case-sensitive field which accepts only lowercase inputs. For example: oracle, mysql, mssql and mariadb.
Workaround
Change the database name in the following sets of schemas and tables:
-
Schema: ADMINDB
Table: SERVER_CONFIGURATION
Field / value: storage_database_type = oracle / mysql / mssql / mariadb
-
Schema: ACCOUNTS
Table: FEATURES
Field / value: {"storagedatabasetype":"oracle / mysql / mssql / mariadb","serverdatabasetype":"oracle / mysql / mssql / mariadb"}
-
-
Issue: The publishing of a Storage application fails on an environment that uses the SQLServer with Windows authentication.
Workaround
In the
server_configuration
table of the Integration database(admindb) insert the keyKONY_SERVER_IS_WINDOWS_AUTHENTICATION_ENABLED
with value set to true. Restart the application server.
- Issue: On a Quantum Fabric environment installed on Apache Tomcat the attempt to publish a web application fails with a 403 error.
This error occurs due to the increased strictness of the ordering of tags within the
tomcat-users.xml
file that comes with the Installer bundled Tomcat v9.0.33.Workaround
Update the
tomcat-users.xml
file located at <TOMCAT_HOME>/conf/ and ensure all the <role> tags precede the all the <user> tags.Example configuration:
-
Issue: While upgrading Identity from MobileFabric 7.0/7.1 to Quantum Fabric V9.x with the selected database as MSSQL, the upgrade fails due to the following errors that occur due to the Flyway tool version upgraded from 3.x to 4.x:
- Failed to DROP INDEX "<auth_schema>"."schema_version_ir_idx"
- Failed to DROP INDEX "<auth_schema>"."schema_version_vr_idx"
Workaround
To avoid this issue, perform the following steps:
Remove the version_rank column from the schema_version table in the authglobaldb by following queries before the upgrade.
DROP INDEX schema_version_ir_idx ON dbo.schema_version GO DROP INDEX schema_version_vr_idx ON dbo.schema_version GO ALTER TABLE dbo.schema_version DROP CONSTRAINT schema_version_pk GO ALTER TABLE dbo.schema_version DROP COLUMN version_rank GO ALTER TABLE dbo.schema_version ADD CONSTRAINT schema_version_pk PRIMARY KEY CLUSTERED (installed_rank) GO ALTER TABLE dbo.schema_version ALTER COLUMN version nvarchar(50) NULL GO