Bug 1018854 - Broken instructions for quickstars/switchyard/demos/helpdesk
Summary: Broken instructions for quickstars/switchyard/demos/helpdesk
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Examples
Version: 6.0.0,6.0.0 GA
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: David Ward
QA Contact: Martin Vecera
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 14:24 UTC by Martin Vecera
Modified: 2013-10-17 16:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-16 14:09:13 UTC
Type: Bug


Attachments (Terms of Use)

Description Martin Vecera 2013-10-14 14:24:14 UTC
quickstarts/switchyard/demos/helpdesk/Readme.md reads
...
6. Going back to your web browser window:
    As krisv (a developer), click the Submit button to get the list of tasks.
    As krisv, review the tasks you want to perform and click the Submit button again.
    As david (a user), click the Submit button to get the list of tasks. He will only have tasks if more details were required.
    If there were user tasks, check the tasks you want to complete and click the Submit button again.
    Continue toggling back and forth as the users until all tasks are completed.
    You can view the application server output in its console window to see the progression of the progress.
...

This is not valid, the ticket is immediately passed to the other user after the first click on Submit. So the users needs to switch in actions: krisv - david - krisv - david...

Comment 1 Keith Babo 2013-10-16 14:09:13 UTC
I have just verified that the original instructions are accurate with a fresh deployment of this quickstart on ER4.  The real point of the quickstart is that there is a human workflow that only concludes when the approver (krisv) approves/rejects the ticket.  Until that happens, the ticket bounces back and forth between krisv and david.


Note You need to log in before you can comment on or make changes to this bug.