There are multiple ways to use the Special Function Table. One option lets you collect user information when you don’t want to create Issuetrak user records. For example, in a retail operation tracking customer complaints, you may only hear from a customer one time. You need to capture information to resolve their problem, but you may never interact with them again. Another option lets you capture part numbers or product SKUs that need to be referenced across multiple issues. Storing this information in the Special Function Table lets you build a history of how many times that SKU or part is tied to an issue.
When deciding to use the Special Function Table there are a few things you need to take into account. First, Special Function Table records are not associated with your site’s visibility constraints. Anyone that can view the submit page can search for and view all of the Special Function Table records in your site. Second, the 50 text fields can only store 150 characters each. Additionally, only users with the permission “Can add, edit and delete Special Function Table records” can create or edit Special Function Records from the submit screen. If the user can also edit the issue, they cantake the data entered into the five visible fields by someone else and create a record if necessary.
The Special Function Table works really well for recording contact information for people or things that don’t need to interact with your Issuetrak system. It allows you to create information outside of your site’s structure, without the overhead of creating a new user or new asset. Special Function Table records also allow you to track an issue history for each record, so you can see what issues that record was selected on. Special Function Table records can be a useful part of your Issuetrak system.
Once you have an idea of what you want to use this for, go ahead and enable the Special Function Table. After the feature is enabled, configure it by navigating to Administration > Special Function Table.
Start on the Table Settings page and set the Table Name; this name will appear on the issue screens and will also change the label in the Administration menu. For example, if you want to use the Special Function Table for Contact Records, then the Table Name could be “Customer/Contact Info.” Then choose either the one or two column layout for the five fields that appear on the issue record.
You can enable the option to “Use Table as Contact Record,” which will allow you to select one of the first five fields to capture an email address. If that field is filled in on an issue, then email notifications will be sent to that email address based the settings determined under View/Maintain Distribution List.
After you’ve completed the Table Settings, you can define the field labels for the 50 different fields on the Label Definitions page.
The Label Definitions screen allows you to name the fields. Keep in mind that you can use as many or as few of the 50 fields as needed. Only the first five fields will be displayed on the issue record. You can see the rest of the fields by selecting “details” when viewing an issue.