KB-2289 Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non-supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Maggie Deppe-Walker — Wed, 31 Jan 2024 06:23:44 GMT

Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 1/31/2024 6:23:44 AM

Symptoms

Given a data store backed by an Oracle database, and a CDT with a text field containing an invalid character (ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏĞÑÒÓÔÕÖ×ØÙÚÛÜİŞßàáâãäåæçèéêëìíîïğñòóôõö÷øùúûüışÿ), the following error is thrown when verifying the data store, downloading the DDL script or creating a CDT from a table/view:

The following error is seen in the app server log:

 Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n.jar library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/. This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Cloud

Apply the latest hotfix to your Appian Cloud installation.

Self-managed

Deploy orai18n.jar under <APPIAN_HOME>/tomcat/apache-tomcat/lib/ and restart the application server. This library can be obtained from Oracle here.

Affected Versions

This article applies to all self-managed versions of Appian and Appian Cloud 22.1 and later.

Last Reviewed: December 2024

Tags: known issues, encoding, database, design, fixed issues, oracle

KB-2289 Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non-supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Maggie Deppe-Walker — Wed, 31 Jan 2024 06:23:44 GMT

Revision 12 posted to Appian Knowledge Base by Maggie Deppe-Walker on 1/31/2024 6:23:44 AM

Symptoms

The following error is seen in the app server log:

 Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n.jar library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/. This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Cloud

Apply the latest hotfix to your Appian Cloud installation.

Self-managed

Deploy orai18n.jar under <APPIAN_HOME>/tomcat/apache-tomcat/lib/ and restart the application server. This library can be obtained from Oracle here.

Affected Versions

This article applies to all self-managed versions of Appian and Appian Cloud 22.1 and later.

Last Reviewed: December 2024

Tags: known issues, encoding, database, design, fixed issues, oracle

SP-7772 [DRAFT] Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non-supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Elly Meng — Wed, 22 Feb 2023 23:05:45 GMT

Revision 11 posted to Appian Knowledge Base by Elly Meng on 2/22/2023 11:05:45 PM

Symptoms

The following error is seen in the app server log:

 Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n.jar library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/. This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Cloud

Apply the latest hotfix to your Appian Cloud installation.

Self-managed

Deploy orai18n.jar under <APPIAN_HOME>/tomcat/apache-tomcat/lib/ and restart the application server. This library can be obtained from Oracle here.

Affected Versions

This article applies to all self-managed versions of Appian and Appian Cloud 22.1 and later.

Last Reviewed: February 2023

Tags: known issues, encoding, database, design, fixed issues, oracle

SP-7772 [DRAFT] Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non-supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 09 Feb 2023 11:56:11 GMT

Revision 10 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 2/9/2023 11:56:11 AM

Symptoms

When verifying the Data Store, downloading the DDL script from the Data Store Designer or creating a CDT/Data Type Object from a data source, using an Oracle database as a data source with a data type with a text field containing "ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏĞÑÒÓÔÕÖ×ØÙÚÛÜİŞßàáâãäåæçèéêëìíîïğñòóôõö÷øùúûüışÿ".

Error message pops up about not being able to retrieve metadata of some Data Store field:

The application server log also complains about missing orai18n.jar:

 Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Deploy the missing orai18n.jar under <APPIAN_HOME>/tomcat/apache-tomcat/lib/ and restart the application server. It can be obtained from the Oracle companion packages: https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to Appian Cloud 22.4.0.10, 22.1.620.0 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Mon, 04 Jul 2022 08:47:54 GMT

Revision 9 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 7/4/2022 8:47:54 AM

Symptoms

Error message pops up about not being able to retrieve metadata of some Data Store field:

The application server log also complains about missing orai18n.jar:

 Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to Appian Cloud 22.4.0.10, 22.1.620.0 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Mon, 04 Jul 2022 08:46:30 GMT

Revision 8 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 7/4/2022 8:46:30 AM

Symptoms

Error message pops up about not being able to retrieve metadata of some Data Store field:

The application server log also complains about missing orai18n.jar:

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to Appian Cloud 22.4.0.10, 22.1.620.0 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Mon, 04 Jul 2022 08:39:38 GMT

Revision 7 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 7/4/2022 8:39:38 AM

Symptoms

When verifying the Data Store, downloading the DDL script from the Data Store Designer or creating a CDT/Data Type Object from a data source, using an Oracle database as data source with a data type with text field containing "ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏĞÑÒÓÔÕÖ×ØÙÚÛÜİŞßàáâãäåæçèéêëìíîïğñòóôõö÷øùúûüışÿ".

Error message pops up about not being able to retrieve metadata of some Data Store field:

Application server log also complains about missing orai18n.jar:

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian 22.2.300.0 and 22.1.620.0 for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to Appian Cloud 22.4.0.10, 22.1.620.0 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 30 Jun 2022 10:45:34 GMT

Revision 6 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 6/30/2022 10:45:34 AM

Symptoms

Error message pops up about not being able to retrieve metadata of some Data Store field:

Application server log also complains about missing orai18n.jar:

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian X.X for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian Cloud 22.1 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 30 Jun 2022 10:39:52 GMT

Revision 5 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 6/30/2022 10:39:52 AM

Symptoms

Error message pops up about not being able to retrieve metadata of some Data Store field:

Application server log also complains about missing orai18n.jar:

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian X.X for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Deploy the missing orai18n.jar under <APPIAN_HOME>/tomcat/apache-tomcat/lib/ and restart the application server. It can be obtained from the Oracle companion packages: https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian Cloud 22.1 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 30 Jun 2022 10:39:39 GMT

Revision 4 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 6/30/2022 10:39:39 AM

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Symptoms

Error message pops up about not being able to retrieve metadata of some Data Store field:

Application server log also complains about missing orai18n.jar:

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

The orai18n library is missing under <APPIAN_HOME>/tomcat/apache-tomcat/lib/

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian X.X for Cloud customers.

Action

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian Cloud 22.1 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 30 Jun 2022 10:33:06 GMT

Revision 3 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 6/30/2022 10:33:06 AM

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Symptoms

When
1) verifying the data store,
2) downloading the ddl script from the data store designer and
3) Creating a CDT/Data Type Object from a data source.

Unsing an Oracle database as data source with a data type with text field containing "ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏĞÑÒÓÔÕÖ×ØÙÚÛÜİŞßàáâãäåæçèéêëìíîïğñòóôõö÷øùúûüışÿ" and use a!queryEntity to read and ensure it was written properly.

Error message pops up about not being able to retrieve metadata. Tomcat-stdOut.log complains about missing orai18n.jar.

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-208514.
This issue has been hotfixed via AN-208781 in Appian X.X.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian Cloud installation.
If it's a self-managed environment, deploy the missing library following the steps from the next section.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian Cloud 22.1 and earlier versions.

Last Reviewed: June 2022

Tags: known issues, encoding, database, design, fixed issues, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 30 Jun 2022 10:25:53 GMT

Revision 2 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 6/30/2022 10:25:53 AM

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Symptoms

When
1) verifying the data store,
2) downloading the ddl script from the data store designer and
3) Creating a CDT/Data Type Object from a data source.

Error message pops up about not being able to retrieve metadata. Tomcat-stdOut.log complains about missing orai18n.jar.

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.https://issues.appian.com/browse/AN-208781
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian versions X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian versions X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian Cloud 22.1 and earlier versions.

Last Reviewed: June 2022

Tags: encoding, database, design, oracle

INT-XXXX Can't publish Data Store or download DDL scripts - Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath) on customers with Oracle Database.

Miguel Ángel Antolín Bermúdez — Thu, 30 Jun 2022 10:09:42 GMT

Revision 1 posted to Appian Knowledge Base by Miguel Ángel Antolín Bermúdez on 6/30/2022 10:09:42 AM

INT-0002 [TEMPLATE] Symptoms-Cause-Action-Workaround

This article serves as a template that you can copy/paste into a new article for use later on.

The title of the article must be under 256 characters (less depending on the types of characters used in the title as this is a limitation of Telligent). It must describe as concisely as possible the issue faced. If there is a short enough error message, it should be included in the title for readability. Those using the Knowledge Base should get a good idea of what the article is about just by reading the title.

This description is for informational purposes only. There should be no text above the "Symptoms" header when using this template. The only exception to this is if the article you are writing is an issue that has been resolved, include the following green box above the Symptoms section:

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

To include this box, add the following in the source code of your article:

<table style='background-color: #bcedaf;'>
<tbody>
<tr>
<td>This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.</td>
</tr>
</tbody>
</table>

Symptoms

Against the data store pointing to the database, write to DSE with a data type with text field containing "ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏĞÑÒÓÔÕÖ×ØÙÚÛÜİŞßàáâãäåæçèéêëìíîïğñòóôõö÷øùúûüışÿ" and use a!queryEntity to read and ensure it was written properly. This should work before and after this ticket's fixes go in.

1. Create new data type object. Give it an id (Number (Integer)) and a text field. Save.

2. Create data store -> select oracle data source.

3. Add the newly created data type object as an entity.

4. Hit verify. See that it says no matching tables found.

5. Hit "Download DDL Script". It should succeed to download the script.

6. Hit "SAVE & PUBLISH".

Expected behavior: This should succeed and the new data type object is persisted in the database with the associated user's schema.

Actual behavior: Error message pops up about not being able to retrieve metadata. Tomcat-stdOut.log complains about missing orai18n.jar.

Caused by: java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

The same error is being returned when selecting this data source when attempting to create a CDT from a table/view.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.https://issues.appian.com/browse/AN-208781
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian versions X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian versions X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.
This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian 7.11 and later.
This article applies to Appian 16.2 and earlier.
This article applies to Appian 7.11 and 16.1.
This article applies to Appian 16.1, 16.2, and 16.3.
This article applies to self-managed Appian 19.3 and earlier.
This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.

Last Reviewed: Month YYYY

Tags: encoding, database, design, oracle