Can't reject filed records

Description

Steps to reproduce

  1. Login to Share

  2. Upload a file into a collaboration site

  3. Declare the file as a record

  4. Navigate into the RM site

  5. Go to unfiled records

  6. Move the record to a folder, without completing it

Expected: Reject record action is available

Actual: Reject record action is not available

Environment

None

Activity

Show:
All Replies
October 30, 2020, 11:06 PM

[This issue has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The reporter of this issue was jknowles]

Claudia Agache
May 22, 2019, 6:33 AM
Edited

Checked that:

  • Reject action is not available for a category, record folder, not in-place record, complete record, frozen record, cut-off record

  • Reject action is not available for rm user with no Reject Records capability even if user has filing permissions

  • Reject action is not available for rm user with Reject Records capability and read-only permissions

  • Rejected record doesn't keep record's metadata

  • Reject option is working also for a record declared and filed directly to a record folder

All Replies
May 14, 2019, 9:52 AM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was buildandpackaging] Ross Gale mentioned this issue in a merge request of records-management/records-management:
'Resolve "Feature/ rejectfiledrecords"'

All Replies
May 7, 2019, 4:29 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was rgale] Here are the list of conditions we have when rejecting a record:

<entry key="capabilityCondition.filling" value="true"/>
<entry key="capabilityCondition.frozen" value="false"/>
<entry key="capabilityCondition.cutoff" value="false"/>
<entry key="capabilityCondition.closed" value="false"/>
<entry key="capabilityCondition.declared" value="false"/>
<entry key="capabilityCondition.recordFiled" value="false"/>
<entry key="capabilityCondition.isRecordOriginatingLocationSet" value="true" />

I think there was concern about the scope of testing this bug would require but looking at the other options in the conditions list i think limit what we would need to test considerably

Done

Assignee

Unassigned

Reporter

All Replies

Bug Priority

Category 3