You are currently reviewing an older revision of this page.
After upgrading Appian, some suers have experienced the following issue after starting up their Appian instance and accessing Tempo:
This article explains the cause of the issue.
If this is a product defect, use the following language:
This issue has been reported to the Appian product team. The reference number for this issue is AN-XXXXX.
Ensure the JIRA ticket number is bold.
If the ticket has been fixed, use the following language:
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
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.
This section contains the steps to resolve the issue. If no action is required for this, indicate so in this section. If there is a bug with no workaround, say "No action is available at this time while the Appian product team investigates this issue."
If there is a bug with a workaround, the action should include that workaround.
This section is optional. Workarounds typically are ways for a customer to correct their issue at some technical debt (not a complete solution or requires extra work at the cost of not upgrading).
This section will list any specific configurations that this article applies to. Some examples are as follows:
This article applies to all versions of Appian.
This article applies to Appian 16.2 and later.
This article applies to Appian 17.1 and earlier.
This article applies to Appian 17.1 and 17.2.
This article applies to Appian 16.1, 16.2, and 16.3.
You can also include additional configurations, such as "using JBoss EAP as an application server", "using Internet Explorer 11 as a web browser", or "using SQL Server as a data source".
Last Reviewed: Month YYYY