KB-2053 Aberrant behavior after deleting versions of content objects

Parmida Borhani — Fri, 10 Jan 2020 00:04:37 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/10/2020 12:04:37 AM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behavior is observed:

The suggestion panel does not show any information for that content object when hovering over an invocation in the expression editor.
Interface configurations and bindings in process models are lost, and it is not possible to reconfigure them.

Cause

The VERSION_ORIGINAL version of the content object was deleted. After deleting the original version, Appian gradually propagates the remapped content IDs throughout the system.

Action

Appian will gradually propagate the updated content IDs which will resolve the issue. If an immediate resolution is required, republish the affected content object by either re-importing it, or saving it in the /design interface.

When using the Suite API, instead use the deactivateVersion Suite API method to deactivate that content version instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: plug-ins, integration, custom plugins, plugins

KB-XXXX Aberrant behavior after deleting versions of content objects

Tom Ryan — Thu, 09 Jan 2020 23:14:18 GMT

Revision 6 posted to Appian Knowledge Base by Tom Ryan on 1/9/2020 11:14:18 PM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behavior is observed:

The suggestion panel does not show any information for that content object when hovering over an invocation in the expression editor.
Interface configurations and bindings in process models are lost, and it is not possible to reconfigure them.

Cause

The VERSION_ORIGINAL version of the content object was deleted. After deleting the original version, it takes Appian some time to propagate the remapped content ids throughout the system.

Action

Appian will gradually propagate the updated content ids which will resolve the issue. If an immediate resolution is required, republish the affected content object by either reimporting it, or saving it in the /design interface.
When using the Suite API, instead use the deactivateVersion Suite API method to deactivate that content version instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: integration, custom plugins, shared components, plugins

KB-XXXX Aberrant behavior after deleting versions of content objects

Tristan Newmann — Thu, 09 Jan 2020 04:18:32 GMT

Revision 5 posted to Appian Knowledge Base by Tristan Newmann on 1/9/2020 4:18:32 AM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behavior is observed:

The suggestion panel does not show any information for that content object when hovering over an invocation in the expression editor.
Interface configurations and bindings in process models are lost, and it is not possible to reconfigure them.

Cause

The VERSION_ORIGINAL version of the content object was deleted. After deleting the original version, it takes Appian some time to propagate the remapped content ids throughout the system.

Action

Republish the affected content object by either reimporting it, or saving it in the /design interface.
When using the Suite API, instead use the deactivateVersion Suite API method to deactivate that content version instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: integration, custom plugins, shared components, plugins

KB-XXXX Aberrant behavior after deleting versions of content objects

Tristan Newmann — Thu, 09 Jan 2020 04:17:07 GMT

Revision 4 posted to Appian Knowledge Base by Tristan Newmann on 1/9/2020 4:17:07 AM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behavior is observed:

The suggestion panel does not show any information for that content object when hovering over an invocation in the expression editor.
Interface configurations and bindings in process models are lost, and it is not possible to reconfigure them.

Cause

The VERSION_ORIGINAL version of the content object was deleted. After deleting the original version, it takes Appian some time to propagate the remapped content ids throughout the system.

Action

Republish the affected content object by either reimporting it, or saving it in the /design interface.
When using the Suite API, instead use the deactivateVersion Suite API method to deactivate that content version instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: integration, custom plugins, plugins

KB-XXXX Aberrant behavior after deleting versions of content objects

Tristan Newmann — Tue, 07 Jan 2020 05:07:22 GMT

Revision 3 posted to Appian Knowledge Base by Tristan Newmann on 1/7/2020 5:07:22 AM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behavior is observed:

The suggestion panel does not show any information for that content object when hovering over an invocation in the expression editor.
Interface configurations and bindings in process models are lost, and it is not possible to reconfigure them.

Cause

The VERSION_ORIGINAL version of the content object was deleted. It is not a valid operation to delete this version of a content object. Instead, it should be deactivated using the deactivateVersion Suite API method.

Action

Republish the affected content object by either reimporting it, or saving it in the /design interface.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: integration, custom plugins, plugins

KB-XXXX Deleting VERSION_ORIGINAL of a content object causes aberrant behaviour

Tristan Newmann — Tue, 07 Jan 2020 04:46:05 GMT

Revision 2 posted to Appian Knowledge Base by Tristan Newmann on 1/7/2020 4:46:05 AM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behaviour is observed:

The suggestion panel will not show any information for that content object when hovering over an invocation in the expression editor.
Interface configurations and bindings in process models will be lost, and it will not be possible to reconfigure them.

Cause

The VERSION_ORIGINAL version of the content object was deleted. It is not a valid operation to delete this version of a content object, instead, it should be deactivated using the deactivateVersion Suite API method.

Action

Republish the affected content object by either reimporting it, or saving it in the /design interface.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: custom plugins, plugins

KB-XXXX Deleting VERSION_ORIGINAL of a content object causes aberrant behaviour

Tristan Newmann — Tue, 07 Jan 2020 04:45:21 GMT

Revision 1 posted to Appian Knowledge Base by Tristan Newmann on 1/7/2020 4:45:21 AM

Symptoms

After deleting content object (Appian expression, interface and constant) versions using the Suite API methods deleteVersion or deleteVersions, the following behaviour is observed:

The suggestion panel will not show any information for that content when hovering over an invocation of the content in the expression editor.
Interface configurations and bindings in process models will be lost, and it will not be possible to reconfigure them.

Cause

Action

Republish the affected content object by either reimporting it, or saving it in the /design interface.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: custom plugins, plugins