Definitions:

• Item - An Item is something can be described and/or tracked such as an issue, request, or task.
• Module - A module is a description you need to attach to an Item. A module can be something like product, version, assigned user, status, priority, or due date.
• Value - A Value is an entry for a module. A value can be selected from a predefined list or entered dynamically by the end user.
• Note - Multiple notes can be attached to an Item and each of those notes can have modules attached to the note. This is good for situations in which the description of an Item may change over a time that it is being tracked and a note is used to further document that change.
• Hours and Resources - are similar to notes in that they attached to Items. Hours and resources provide a way to track the expense of completing or associated with a task.

Database Layout:

Multiple Databases
One database is used for configuration and the other for data. This allows you to easily manipulate your configuration and your database separately. If you want to create a new data store with the same configuration, simply create a new database for the data.

Multiple Value Tables
Values are stored in a separate table for each module. A module is descriptive data that can be attached to an Item. If you store each piece of data in a separate table the organization is clearer and more easily maintained.

Installation and Start Menu:

• ItemAction
• ItemAction Manager
• Select Database
• There will also be a shortcut to the help file and a shortcut to uninstall ItemAction.

User Database Configuration:

ItemAction will also look for database settings left from a previous version. If no databases can be found, the user will be prompted to designate the location of the databases.

Once valid database selections have been made the orginal load of ItemAction or ItemAction manager will continue and this screen will automatically be closed. The currently highlighted database configuration in the list will be the one that is used.

Management/Workgroup Configuration:

The Manager application can be used to customize the installation.

Passwords:

If ItemAction is first run from a system that has no Username, system authentication will not be available and the user will be forced to set a password.

Only an administrator can edit and clear a users password.

In the manager application the manager will be able to tell if a user has a password set, but there is no way to retrieve a password from the system. The only way to recover a password for a user is to clear the password or change the password.

Security/Selection Levels:

Three Security Levels are pre-defined and cannot be deleted or renamed. The three pre-defined Security Levels are:

• Guest
• Issuer
• Assigned

A users Security Clearance cant be set to the levels Issuer or Assigned since they are set dynamically as the user switches from one Item to another. If a users actual Security Clearance is higher than Issuer or Assigned they will retain the higher level of privileges.

Guest has its priority locked at 0. Guests do not need a user license to view information, but they can't make any changes or enter any information.

Issuer is a special purpose level. It is the security level of the user who creates, or issues the item.

Assigned is the user who the item has been assigned to.

Other security levels are user-defined, and you may change them to whatever you like.

Triggers:

Viewing items:

Filtering the Item List:

ItemAction Email:

Individual users can also receive confirmation email for all changes that they make themselves, by enabling the option in their options dialog.

ItemAction sends email using a MAPI enabled mail client.

Closing items: