KB-1587 Tempo and /designer contents do not render properly

Jordan Horwat — Mon, 23 Jul 2018 12:44:42 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 12:44:42 PM

Symptoms

Tempo is not rendering properly:

When trying to access /designer, this error can appear:

Cause

This can happen when the Default Community has been deleted.

Action

Check if the Default Community exists:

Navigate to Runtime Data (<APPIAN_URL>/suite/designer).
Click on Documents.
Check if the Default Community is present. The following two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center.

If it is not present, here is how to recreate the Default Community:

In an environment where the Default Community exists running the same version and hotfix as the malfunctioning environment, open Appian Designer.
Create an application containing the Default Community, System Knowledge Center, and Temporary Documents Knowledge Center.
Export this application from the working environment and import it into the malfunctioning environment.

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and earlier.

Tags: user interface, knowledge centers, application design

KB-1587 Tempo and /designer contents do not render properly

Nick Vigilante — Tue, 29 May 2018 14:03:01 GMT

Revision 10 posted to Appian Knowledge Base by Nick Vigilante on 5/29/2018 2:03:01 PM

Symptoms

Tempo is not rendering properly:

When trying to access /designer, this error can appear:

Cause

This can happen when the Default Community has been deleted.

Action

Check if the Default Community exists:

Navigate to Runtime Data (<APPIAN_URL>/suite/designer).
Click on Documents.
Check if the Default Community is present. The following two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center.

If it is not present, here is how to recreate the Default Community:

In an environment where the Default Community exists running the same version and hotfix as the malfunctioning environment, open Appian Designer.
Create an application containing the Default Community, System Knowledge Center, and Temporary Documents Knowledge Center.
Export this application from the working environment and import it into the malfunctioning environment.

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and earlier.

Tags: user interface

KB-1587 Tempo and /designer contents do not render properly

Nick Vigilante — Tue, 29 May 2018 10:03:01 GMT

Revision 9 posted to Appian Knowledge Base by Nick Vigilante on 5/29/2018 10:03:01 AM

Symptoms

Tempo is not rendering properly:

When trying to access /designer, this error can appear:

Cause

This can happen when the Default Community has been deleted.

Action

Check if the Default Community exists:

Navigate to Runtime Data (<APPIAN_URL>/suite/designer).
Click on Documents.
Check if the Default Community is present. The following two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center.

If it is not present, here is how to recreate the Default Community:

In an environment where the Default Community exists running the same version and hotfix as the malfunctioning environment, open Appian Designer.
Create an application containing the Default Community, System Knowledge Center, and Temporary Documents Knowledge Center.
Export this application from the working environment and import it into the malfunctioning environment.

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and earlier.

Tags: user interface

DRAFT KB-XXXX How to retrieve the Default Community

Tom Ryan — Tue, 29 May 2018 04:01:50 GMT

Revision 8 posted to Appian Knowledge Base by Tom Ryan on 5/29/2018 4:01:50 AM

Symptoms

Tempo is not rendering properly:

When trying to access /designer, this error can appear:

Cause

This can happen when the Default Community has been deleted.

Action

Check if the Default Community exists:

Navigate to Runtime Data (<APPIAN_URL>/suite/designer).
Click on Documents.
Check if the Default Community is present. The following two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center.

If it is not present, here is how to recreate the Default Community:

In an environment where the Default Community exists running the same version and hotfix as the malfunctioning environment, open Appian Designer.
Create an application containing the Default Community, System Knowledge Center, and Temporary Documents Knowledge Center.
Export this application from the working environment and import it into the malfunctioning environment.

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and earlier.

DRAFT KB-XXXX How to retrieve the Default Community

Diaba Konate — Tue, 22 May 2018 07:59:41 GMT

Revision 7 posted to Appian Knowledge Base by Diaba Konate on 5/22/2018 7:59:41 AM

Symptoms

Tempo is not rendering properly:

When trying to access /designer, this error can appear:

Cause

This can happen when the Default Community has been deleted.

Action

Check if the Default Community exists:

Navigate to Runtime Data (<APPIAN_URL>/suite/designer).
Click on Documents.
Check if the Default Community is present. This two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center.

If it is not present, here is how to recreate the Default Community:

In an environment where the Default Community exists running the same version and hotfix as the malfunctioning environment, open Appian Designer.
Create an application containing the Default Community, System Knowledge Center, and Temporary Documents Knowledge Center.
Export this application from the working environment and import it into the malfunctioning environment.

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and earlier.

DRAFT KB-XXXX How to retrieve the Default Community

Diaba Konate — Mon, 21 May 2018 11:38:03 GMT

Revision 6 posted to Appian Knowledge Base by Diaba Konate on 5/21/2018 11:38:03 AM

Symptoms

Tempo is not rendering properly:

When trying to access /designer, this error can appear:

Cause

This can happen when the Default Community has been deleted.

Action

Check if the Default Community exists:

Navigate to Runtime Data (<APPIAN_URL>/suite/designer).
Click on Documents.
Check if the Default Community is present. This two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center.

If it is not present, here is how to recreate the Default Community:

In an environment where the Default Community exists running the same version and hotfix as the malfunctioning environment, open Appian Designer.
Create an application containing the Default Community, System Knowledge Center, and Temporary Documents Knowledge Center.
Export this application from the working environment and import it into the malfunctioning environment.

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and earlier.

DRAFT KB-XXXX How to retrieve the Default Community

Diaba Konate — Fri, 18 May 2018 10:14:12 GMT

Revision 5 posted to Appian Knowledge Base by Diaba Konate on 5/18/2018 10:14:12 AM

Symptoms

Tempo page is not rendering properly:

When trying to access to legacy designer, this error can appear:

Cause

This can happen when the Default Community have been deleted.

Action

Check if the Default Community exists:

Go to Runtime Data
Click on Documents
Check if the Default Community is present. This two subfolders should also be present: System Knowledge Center and Temporary Documents Knowledge Center

If it is not present, here is how to retrieve the Default Community:

Export it from another environment in an application
Import it to the impacted environment

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and later.

DRAFT KB-XXXX How to retrieve the Default Community

Diaba Konate — Wed, 16 May 2018 09:38:02 GMT

Revision 4 posted to Appian Knowledge Base by Diaba Konate on 5/16/2018 9:38:02 AM

Symptoms

Tempo page is not rendering properly:

When trying to access to legacy designer, this error can appear:

Cause

This can happen when the Default Community have been deleted.

Action

Check if the Default Community exists:

Go to Runtime Data
Click on Documents
Check if the Default Community is present. This two sub folder should also be present System Knowledge Center and Temporary Documents Knownledge Center

If it is not present, here is how to retrieve the Default Community:

Export it from another environment in an application
Import it to the impacted environment

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and later.

DRAFT KB-XXXX How to retrieve the Default Community

Diaba Konate — Mon, 14 May 2018 12:33:49 GMT

Revision 3 posted to Appian Knowledge Base by Diaba Konate on 5/14/2018 12:33:49 PM

Symptoms

Tempo page is not rendering properly:

When trying to access to legacy designer, this error can appear:

Cause

This can happen if the Default Community have been deleted.

Action

Check if the default community exists by:

These steps solve this issue:

Export the Default Community from another environment in an application
Import it to the impacted environment

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and later.

DRAFT KB-XXXX How to retrieve the Default Community

Diaba Konate — Mon, 14 May 2018 04:35:04 GMT

Revision 2 posted to Appian Knowledge Base by Diaba Konate on 5/14/2018 4:35:04 AM

Symptoms

Tempo page is not rendering properly:

When trying to access to legacy designer, this error can appear:

Cause

This can happen if the Default Community have been deleted.

Action

These steps solve this issue:

Export the Default Community from another environment in an application
Import it to the impacted environment

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and later.

DRAFT INT-XXXX How to retrieve the Default Community

Diaba Konate — Fri, 11 May 2018 17:14:50 GMT

Revision 1 posted to Appian Knowledge Base by Diaba Konate on 5/11/2018 5:14:50 PM

Symptoms

Tempo page is not rendering properly:

When trying to access to legacy designer, this error can appear:

Cause

This can happen if the Default Community have been deleted.

Action

These steps solve this issue:

Export the Default Community from another environment in an application
Import it to the impacted environment

This community has a reserved UUID which means that importing it will restore it.

Affected Versions

This article applies to Appian 17.4 and later.