CLONE -submit process with items which are already part of another workflow

Description

Pre-conditions:
1. Any web project should be created.
2. User with any role except Content Reviewer for selected web project is logged in Alfresco.
3. At least one item is created and submited;
4. User on Web project's main page;

Steps
1. Select a check-box near submitted file;
2. Press "Submit Selected" link;
3. Fill "Label" and "Description" fields;
4. Press "OK" button;

Expected result
"OK" button is disabled, Workflow: with "No suitable workflows could be found for the modified items below" message; Modified Items: with "The following items cannot be submitted as they are already part of a workflow" message for being submitted file;

Actual result
"OK" button is enabled;

andreyMa

Note: good work in Alfresco 3.2.1 EE b 495

Environment

Alfresco 3.3 EE b 58 - Stack 3 (environment: Windows 2008 SP1 x64, MSSQL 2008 SP1 x64, Tomcat 6.0.18 as a service, JDK 6u20 x64, Kerberos + Alfresco Client: Windows 7, IE 8)

Testcase ID

WCM-431

Activity

Show:
All Replies
September 1, 2010, 2:26 AM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was srigby] Pulled back to Cheetah for BRB review

All Replies
October 18, 2010, 8:08 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was srigby] For retest in head-enterprise build 359 or later

All Replies
October 20, 2010, 2:17 AM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was alfrescoqa] Successfully validated using Alfresco Enterprise 3.4.0 (build 359), Windows Server 2008 x64, Mysql 5.1.50, Tomcat 6.0.26 Windows XP, FF3.6.

Derek Hulley
August 31, 2016, 10:18 PM

The component originally used was not a supported, recognisable system component with an associated component owner. Either the component never existed (it was fictional) or it has reached end-of-life.
The issues will be closed. Reopen and assign to an existing system component if necessary. Use labels appropriately.

All Replies
October 31, 2020, 12:11 PM

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

Fixed

Assignee

All Replies

Reporter

All Replies

Labels

None

Security Severity

None

Patch Attached

None

Sprint Number

None

Documentation required

None

Documentation Impact

None

Resource

External

Regression

Regression

Escalation level

None

Triage

None

Release Train

None

Delivery Team

None

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Critical