This chapter describes how quality assurance is performed in the Stardust Portal.
To run the example process, start your server and deploy the model. For details on how to deploy a model, please refer to chapter Deploying a Workflow Model of the Support Case Example. Proceed with the following sections:
First we create two users, a performer of the activity and a performer of the quality assurance.
motu/motu). You can use the Shift-F8 short key.For details on how to create users and assign them to roles, refer chapter Creating and Editing User Accounts of the Stardust Portal documentation.

Figure: Create the users.


Go back to the worklist view and start another process instance of
QAUseFormula. Now enter an invalid entry for the account
number, e.g. 123456, which has more than 4 digits and complete the
activity.

Figure: Enter an invalid account number.
Again start another process instance of QAUseFormula. Now enter an empty entry for the account name and complete the activity.

Figure: Enter an invalid account name.
Logout and login as user Frank Cityman having the quality assurance operator role. Switch to the Workflow Execution Perspective.
In the My Assignments section, there are three items in the worklist. Click on the 3 item(s) entry to open the worklist view.

Figure: Open the Worklist View.
In the worklist view, you see two activity instances marked with the
icon
for being in quality
assurance, in our case awaiting to be reviewed. These are the activity instances, where an invalid name and an
invalid number was entered. The quality assurance formula added in the
activity property page has checked these values and returned true as
quality assurance is needed.

Figure: Activities marked for quality assurance.
We activate the activity instance, where we entered an invalid account number.

Figure: Activate the first Quality Assurance Activity.
The activity execution view opens. No we correct the number and pass the activity:
1234.
Yes to confirm that corrections were made.


ERR_101 for invalid account number.


Refer to chapter Executing Quality Assurance Activities in the End User Handbook for details on the option to pass or fail quality assurance activities.
In the worklist view, you can now see that the activity is passed and the activity following, Next Activity, is in the worklist.

Figure: Worklist with the passed activity.
We activate the next activity instance awaiting quality assurance, where we entered an empty account name.

Figure: Activate the first Quality Assurance Activity.
The activity execution view opens. No we will not correct the name and fail the activity quality assurance. The activity should be delegated back to the original performer.



ERR_102 for invalid account name.


In the worklist view, you can now see that the activity instance, which has been failed for quality assurance is removed from the worklist of the QA Operator role..

Figure: Updated Worklist after failing quality assurance.




Now perform the activity again with correct entries.


Now open the Process Details view of the last process to have a look at the actions performed on the activity instance, for which we entered an invalid account name.
For details on the table and how quality assurance states are displayed there, refer to chapter Viewing the Tree of Activities in a specific Process of the End User Handbook.
In this table, we can review the workflow cycle: