KB-1700 Document security does not update after moving a document

Rebecca Jonas — Fri, 14 Jun 2019 21:07:06 GMT

Current Revision posted to Appian Knowledge Base by Rebecca Jonas on 6/14/2019 9:07:06 PM

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.

Symptoms

After moving a document to a new folder via Appian Designer or using the Move Document smart service, the document remains inaccessible to users who have "Viewer" privileges or higher to the target folder but no access to the source folder. These users are able to see new documents uploaded to the target folder as expected.

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This issue has been addressed in Appian 19.1.

Action

Upgrade to the latest version of Appian.

Workaround

If the issue is encountered when moving documents using Appian Designer, consider using a process model with the workaround below.

Include an Inherit Security from Parent for Document smart service node, provided by the Content Security Utilities Shared Component, after the Move Document node in the impacted process models. The smart service will force the content security to refresh after it has been moved.

Affected Versions

This article applies to Appian 18.4 and earlier.

Last Reviewed: June 2019

Tags: known issues, appian objects, process models, documents, Security, application design, fixed issues, plugins

KB-1700 Document security does not update after moving a document

Parmida Borhani — Thu, 13 Sep 2018 04:08:59 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 9/13/2018 4:08:59 AM

Symptoms

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This is a known issue in which document security does not update correctly after moving a document. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-79520.

Workaround

If the issue is encountered when moving documents using Appian Designer, consider using a process model with the workaround below.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

KB-1700 Document security does not update after moving a document

Parmida Borhani — Thu, 13 Sep 2018 00:08:59 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 9/13/2018 12:08:59 AM

Symptoms

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Workaround

If the issue is encountered when moving documents using Appian Designer, consider using a process model with the workaround below.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Parmida Borhani — Thu, 13 Sep 2018 00:08:22 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 9/13/2018 12:08:22 AM

Symptoms

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Workaround

If the issue is encountered when moving documents using Appian Designer, consider using a process model with the workaround below.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Jussi Lundstedt — Wed, 12 Sep 2018 17:40:04 GMT

Revision 10 posted to Appian Knowledge Base by Jussi Lundstedt on 9/12/2018 5:40:04 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Workaround

If the issue is encountered when moving documents using Appian Designer, consider using a process model with the workaround below.

You can include an Inherit Security from Parent for Document smart service node, provided by the Content Security Utilities Shared Component, after the Move Document node in the impacted process models. The smart service will force the content security to refresh after it has been moved.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

KB-XXXX Document security does not update after moving a Document

Jussi Lundstedt — Wed, 12 Sep 2018 16:06:47 GMT

Revision 1 posted to Appian Knowledge Base by Jussi Lundstedt on 9/12/2018 4:06:47 PM

Symptom

After moving a document to a new folder using the Move Document Smart Service, the document remains inaccessible to users who have "Viewer" privileges or higher to the target folder but no access to the source folder. These users are able to see new documents uploaded to the target folder as expected.

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This is a known issue with the document security not updating correctly after moving a document. It has been reported to the Appian Product Team as AN-79520.

Workaround

You can include an Inherit Security from Parent for Document Smart Service node provided by the Content Security Utilities Shared Component after the Move Document node in impacted process models. The Smart Service will force the content security to refresh after it has been moved.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Jordan Horwat — Wed, 12 Sep 2018 15:09:22 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 9/12/2018 3:09:22 PM

Symptom

After moving a document to a new folder using the Move Document smart service, the document remains inaccessible to users who have "Viewer" privileges or higher to the target folder but no access to the source folder. These users are able to see new documents uploaded to the target folder as expected.

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Jordan Horwat — Wed, 12 Sep 2018 15:08:43 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 9/12/2018 3:08:43 PM

Symptom

After moving a document to a new folder using the Move Document smart serve, the document remains inaccessible to users who have "Viewer" privileges or higher to the target folder but no access to the source folder. These users are able to see new documents uploaded to the target folder as expected.

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Action

You can include an Inherit Security from Parent for Document smart serve node, provided by the Content Security Utilities Shared Component, after the Move Document node in the impacted process models. The smart service will force the content security to refresh after it has been moved.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Jordan Horwat — Wed, 12 Sep 2018 15:06:51 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 9/12/2018 3:06:51 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Action

You can include an Inherit Security from Parent for Document Smart Service node, provided by the Content Security Utilities Shared Component, after the Move Document node in the impacted process models. The smart service will force the content security to refresh after it has been moved.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Jordan Horwat — Wed, 12 Sep 2018 15:05:59 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 9/12/2018 3:05:59 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This is a known issue in which document security does not update correctly after moving a document. It has been reported to the Appian Product Team. The reference number for this issue is AN-79520.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

DRAFT KB-XXXX Document security does not update after moving a document

Jordan Horwat — Wed, 12 Sep 2018 15:04:44 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 9/12/2018 3:04:44 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

KB-XXXX Document security does not update after moving a Document

Jussi Lundstedt — Wed, 12 Sep 2018 12:13:17 GMT

Revision 4 posted to Appian Knowledge Base by Jussi Lundstedt on 9/12/2018 12:13:17 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This is a known issue with the document security not updating correctly after moving a document. It has been reported to the Appian Product Team as AN-79520.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

KB-XXXX Document security does not update after moving a Document

Jussi Lundstedt — Wed, 12 Sep 2018 12:12:08 GMT

Revision 3 posted to Appian Knowledge Base by Jussi Lundstedt on 9/12/2018 12:12:08 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This is a known issue with the document security not updating correctly after moving a document. It has been reported to the Appian Product Team as AN-79520.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins

KB-XXXX Document security does not update after moving a Document

Jussi Lundstedt — Wed, 12 Sep 2018 12:10:45 GMT

Revision 2 posted to Appian Knowledge Base by Jussi Lundstedt on 9/12/2018 12:10:45 PM

Symptom

When viewing the security of the document itself, the security matches the target folder's security as intended.

Cause

This is a known issue with the document security not updating correctly after moving a document. It has been reported to the Appian Product Team as AN-79520.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: known issues, appian objects, process models, documents, Security, application design, open issues, plugins