Step 2--Is workflow involved?

If you did not resolve the bug by reducing the possible sources of the issue to a form and a small number of fields, the issue is probably workflow related. Workflow is the source of the majority of code bugs.

Workflow debugging is complex because a workflow object responds to a two-stage trigger of cause and effect.

• The first trigger stage (the Execute On condition) is an application event. Filters use request transitions such as Modify or Submit while active links use an interface event like Open Window.
• The second trigger stage is the evaluation of a qualification. If the qualification evaluates to TRUE, then the actions specified in the If branch are executed. If the qualification evaluates to FALSE, then the actions specified in the Else branch are executed.

Is the problem with server-side workflow?

Does something happen on the server every time you create a new request? If so, the bug probably involves the server side (filters and escalations).

Is the problem with client-side workflow?

Does something happen on the server every time you select a button on a form? If so, the bug probably involves the client side (active links).

Which objects respond to the event?

After you have decided to focus on either filters, escalations, or active links, determine which objects respond to the event--the filters or active links that have an Execute On condition that matches the cause. This reduces the number of objects to examine.