System Identified Issues

Logiak helps you to ensure the quality of what you produce in various ways.

One of these ways is that it continually checks for patterns which indicate you have probably made a mistake.

If it finds one, it attaches an orange flag at the point at which the error is occurring. This is what we mean by a "System Issue" - an Issue identified by the Logiak system.

Example: System Issues in a Process

When you add the question to a Process, it will immediately be flagged with a System Issue flag, which might seem harsh, but it is fair.

The warning in this case is that the question is included in the Process, but as yet its value is not made use of (of course not, you have only just added it).

Unused User Interaction

Despite this being obvious when you first add a question, it is far more difficult to keep track, later on, when the Process is large and things get created, linked, updated, moved, etc.

To have Logiak automatically picking up issues such as this can be invaluable for ensuring quality.

Let us explain this particular System Issue  -

The main uses for a value obtained from the user are:

Store in an Object in the database
Use in the definition of a Condition
Use in the updating of a variable
Presented to the user as part of a later interaction

If a value is asked from a user and not used in any of these ways (i.e. not used at all), then a system issue is appropriately raised since, it what circumstances could it be appropriate to ask the user something and then totally ignore the response?

Suppressing a System Issue

But if you decide there is a good reason and the System Issue is, in fact, no issue for you, you can select the Question and check the "Suppress" checkbox next to the Issue alert.

The Issue alert then goes to a subdued grey, and the orange flag no longer appears against the question (unless there is also another applicable system issue of course).

No items found.

System Identified Issues

Logiak helps you to ensure the quality of what you produce in various ways.

One of these ways is that it continually checks for patterns which indicate you have probably made a mistake.

If it finds one, it attaches an orange flag at the point at which the error is occurring. This is what we mean by a "System Issue" - an Issue identified by the Logiak system.

Example: System Issues in a Process

When you add the question to a Process, it will immediately be flagged with a System Issue flag, which might seem harsh, but it is fair.

The warning in this case is that the question is included in the Process, but as yet its value is not made use of (of course not, you have only just added it).

Unused User Interaction

Despite this being obvious when you first add a question, it is far more difficult to keep track, later on, when the Process is large and things get created, linked, updated, moved, etc.

To have Logiak automatically picking up issues such as this can be invaluable for ensuring quality.

Let us explain this particular System Issue  -

The main uses for a value obtained from the user are:

Store in an Object in the database
Use in the definition of a Condition
Use in the updating of a variable
Presented to the user as part of a later interaction

If a value is asked from a user and not used in any of these ways (i.e. not used at all), then a system issue is appropriately raised since, it what circumstances could it be appropriate to ask the user something and then totally ignore the response?

Suppressing a System Issue

But if you decide there is a good reason and the System Issue is, in fact, no issue for you, you can select the Question and check the "Suppress" checkbox next to the Issue alert.

The Issue alert then goes to a subdued grey, and the orange flag no longer appears against the question (unless there is also another applicable system issue of course).

Next Step:
No items found.