You are currently reviewing an older revision of this page.
This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.
This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:
For any enhancements/defects, use one of the following as applicable:
Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.
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.
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:
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.
This article applies to all versions of Appian.
© 2019 Appian. All rights reserved.