Bug Tracker

Step 1: Create Business Objects

In this Bug Tracker application, there are two main types of Business Object; Bug Reports and Comments. Business Objects can be added to an application from the Application tab.

Step 2: Build Forms

The Bug Report object has five forms associated with it; one general New Issue Form, three specific forms (Printer Problem, Computer Problem and Network Problem) and a form where the help department can set who is assigned to the job.

The Comment object has only one form. Most of the comment form is taken up with the Comment field, which will be used for the body of the message. Besides this, there are fields for setting the subject and authour of the comment. There is also a read-only field for quoting the previous comment, if the comment is a response.

Step 3: Build Workflow

In this Bug Tracker Application, there are four processes.

The main process is the one which deals with filing Bug Reports. When a bug is reported, it is filtered with Rule Based Decisions, to find out which type of problem it is. This problem is then sent on to the help department. The help department can decide who to assign the task to.
At each step of this process, the status of the Bug Report is updated and the user, who reported the bug, is informed of the status of the problem.

The second process deals with what happens, when the bug has been repaired. When the bug is repaired, the user, who has been assigned the bug, changes it's status to "resolved". Then the user, who reported the problem, is informed that the situation has been fixed.
In this process there are measures in place to ensure that unauthourised users cannot change the status of the Bug Report. Also, if a Bug Report has already been cancelled or resolved, this process will not run.

The last two process both relate to the comments system.
The first comment-related process occurs when a user wants to add a comment to a Bug Report. This process automatically fills out the subject field (with the Bug Report's summary) and the user's name.
The second comment-process occurs when a user wants to reply to a previous comment. This process automatically fills out the subject field and quotes the previous user's comment in the new Comment object.
There are also measures in place that prevent a user commenting on a Bug Report that has been resolved or cancelled.

Step 4: Create Views and Related Lists

The final step in creating this application is to build Views and Related Lists. Views allow the administrator to easily retrieve information about all Bug Reports. Related Lists are used to associate the Comments with the appropriate Bug Reports.

Between these steps, it is also useful to test the process with test objects and, where necessary, to make adjustments to forms and processes.

Video of the Application Being Built

This video shows the Bug Tracker being built. This video has been sped up. In real-time, the entire process took about two hours.