Rules Management and Automation With Common Knowledge

Problem Report

Before submitting your problem report, please take time to check the latest FAQ to see if your problem or similar is listed.

Please be as detailed and precise as possible when you are describing your problem. It is critical that you detail the steps that must be taken to reproduce the problem. If our engineers can easily reproduce the problem then they can rapidly provide a solution. If you have any additional supporting information you can provide that will assist us in reproducing the problem, the please include it with your problem report.

After completion of a problem report, you will be given a problem identifier. Any future correspondence associated with the problem should refer to this identifier.

Note: Fields marked with an asterisk (*) are mandatory.

* Name

* Company

* Email

*OS:
What Operating System are you using?

Please enter details if "Other"

OS Patches:
What OS patches/Service packs do you have installed?

RAM:
How much memory do you have installed?

Drivespace:
How much hard drive space do you have?

Please list each drive associated with your problem

*Component:
What component of common knowledge were you using when the problem occurred?

Studio
Rules Engine
Documentation
Other
Please enter details if "Other"

*Language:
What programming language were you using?

Please enter details if "Other"

*Studio Version:
What version of Studio do you have?

Extenders:
What extenders do you have installed?

Table
Grid
Workflow
Rete
Tree
Script
ActiveScript
Library
Other

Please enter details if "Other"

*Severity:
How severe do you consider the problem?

Non-Critical
(Mildly annoying but can put up with it)
Moderate
(Can work around but really annoys me and wastes my time)
Serious
(Stops me performing something I really want to do)
Very Serious
(Has severely limited the operation of my application)
Critical
(Has completely stopped me from achieving my objectives)

*Repeatable:
Is the problem repeatable?

No, it has only occurred once
Not really, it only occurs once in a while
Yes, it happens every time

*Summary:
Please provide a one-line summary of the problem.
This will become the TITLE for any problem records in the Support Q&A.

*Description:
Please provide a detailed description of the problem:

To Reproduce:
List the steps required to reproduce the problem.
If this is not possible then please provide a detailed description of the context in which the problem occurred:

Additional:
Please provide further information that may be relevant to the problem, or that you think may help our engineers to reproduce and/or correct the problem: