|
The Login-Screen.
SWAMPs default authentication mechanism stores
its users and permissions in a database.
The authentication mechanism can easily be customized
and extended to use another base for user data,
e.g. the SUSE-internal SWAMP installation uses a LDAP based authentication.
|
|
Overview for all Workflows in SWAMP.
This page shows a List of currently running processes.
It can be configured to filter the workflowlist in several ways.
Each Workflow is diplayed with its state and its waiting Tasks.
The displayed columns are also completely configureable
by workflow-type and by user preferences. This example shows a list
of SUSE cds that are to be created.
|
|
The WebSWAMP GUI is easy to extend to fit many use-cases.
The screenshot shows a SUSE internal extension that makes it
easy to track many CD creating workflows that are combined to
a "product".
|
|
Each workflow brings its own documentation and a
context sensitive link to it is shown in the upper right corner
of the WebSWAMP GUI. The documentation can also be
extended by the users by editing it inside the browser.
|
|
The WebSWAMP Startpage.
This Screenshot shows the customized SUSE-internal version
with quicklinks to important workflows.
|
|
The WebSWAMP Task-page.
Each kind of User-Task has its own screen to be done.
Tasks that can be done in the Webapp are:
- editing any fields of the workflows data
- make a choice
- give an "OK" so that the workflow is triggered
to go on.
|
|
The Templates page.
All available Workflow templates (available to the logged in user)
are shown on this screen and can be started from here.
|
|
The Workflow page.
All relevant data that is connected to a specific workflow instance
can be found on this page. This contains:
- The Workflow history (who has done what/when)
- Reached Milestones
- active Tasks
- the workflows attached data
- admin functions to change the workflows state
|
