No workflow execution is possible without a properly configured audit trail database and a deployed model. Also, the users have to be defined and assigned to the roles we defined in the model before we can start our support case management process.
Users must be created in the Administration Perspective. They are not part of the model.
We are going to create individual users and assign them to the created roles. While roles and organizations belong to the modeling environment, users belong to the runtime environment and are created, modified and assigned to their respective roles in Stardust Administration Perspective.
To create a user in this tutorial, you must first log on to the Stardust Portal.
The start URL for the Support-Case Stardust Portal is:
http://hostname:port/Support-Case
and will lead you to the Stardust Portal login screen, whereby
hostname is the
name of the host running your application server (in this case localhost)
andport is the HTTP
port of your application server (in this case 8080)So if the Tomcat settings are configured just as they were shown earlier in this tutorial, the browser URL to enter is http://localhost:8080/Support-Case.
Log on with the default administrator's user ID and password: motu/motu (master of the universe). You can use Shift-F8 to rapid type these credentials:
Figure: Login Screen
In the Portal navigation, select the Administration icon
to switch to the Administration perspective.
In the Administration perspective Administrative Views section, choose Participant Manager to open the Participant Manager view.
Figure: Open the Participant Manager View
Click the Create User button to create a new user. Please refer to chapter Creating and Editing User Accounts of the Stardust Portal documentation for detailed information on creating users.
Figure: Click Create User icon
In the appearing dialog fill in the details about the new user:


Now add another user in the same way and assign it to role Engineer. Both users should be displayed in the Participant tree.

Figure: Users displayed in the Participant Tree.
! Tip: When the ACME organization was diagramed earlier, the Callcenter Agent and Engineer roles were shown to Work For ACME Headquarters. Stardust uses that relationship to define delegation rules among participants (supervisors and subordinates). For worklist visibility no explicit assignment to ACME Headquarters is needed in the case of Frank Cityman (or the other engineer user.)
Logout off the Stardust Portal.
ACME can now execute their support case management process. We will log in the Portal this time as Frank Cityman, and perform the activity Enter Data.
Figure: Logging on as another user
The logged on user can now perform activities belonging to the support case management process.

Figure: Starting a Process (Support Case Management Example)
Note that you can adjust the number of columns to display multiple
cardinality data structures in the auto-generated manual activity panel. The
default value is 3. Refer to chapter
Configuring Portal Settings in the
Stardust Portal guide for details.
The first activity of the process has been performed.
The next activity in the series, Analyze To Solve has been assigned to a different performer. A work item for this activity will be placed in the worklist of the user assigned to the role Engineer. For the next activity the user assigned to the role Engineer has to log in to the Stardust Portal.
In contrast to a user performing an initial process activity, a user performing the second or later activity does not click the start process prompt. He just picks up a work item visible in his worklist by clicking on the work item symbol. Notice, there are no startable processes for the Engineer in ACME model, because the manual trigger was only assigned to the Callcenter role, not Engineer. Of course, other process definitions (in addition to Support Case Management) could be added in the future and those could be defined with manual triggers for the Engineer.


C: sends the item to the Deliver Patch
user activity (CLOSED path).R: sends the item to the application activity
Notify Customer (REJECTED path), which prints a
notification on your console.

O: means that the state is still open and repeats the activity
Analyze To Solve.
Congratulations ! You have completed the Stardust Developers Support Case Tutorial.