Managing Lists

The Lists page allows you to maintain lists of available values for user interface fields that require selection from specified values, or "issues." Permissions required to access this page: Access Admin Tab and Manage Lists.

To open the Lists page, choose Admin > Configure > Lists.

What's Changed? In previous versions, lists were called "lookup lists."

This interface displays a separate bar for each type of information that you can maintain. Click a bar to hide or display the issues that have already been defined for that field. You can also click the pushpin at the right end of a bar if you want to "lock" the bar so the information remains displayed while you click other bars. Click the pushpin again to remove the lock on the bar.

For each list, you can configure the following:

The list name.
How the issues will be displayed in the drop-down list: by code, by description or with a combination of the two.
How the issues will be sorted when displayed in the drop-down list. You can sort the issues by description or by code, as strings or as numbers in either case. For each type of sorting, you can also specify the order of sorting (ascending or descending).
The issues in the list.

The description and code/name for each issue in the list will be displayed for the current entity. A check box will appear next to the issue that is set as the default item, if any, and the issue will appear in blue text. In addition, the retired date will appear next to an issue once it is deleted. Please note that only issues that were used in the system can be retired. Items that were not used in the system will be deleted.

To add a new issue, click the Add icon, , to open the Issue utility for that list type.
- For tree details, you can select an existing issue and then click the Add icon to add a child issue.
To edit an existing issue or to associate additional part numbers with an existing issue, select the issue and click the Edit icon, .
Select one or more items in the list of associated parts and click the Delete icon, , to delete the existing issue(s) or to remove the association between a part number and an existing issue for the current entity. You will be prompted to confirm that you wish to delete the item and then it will be deleted or retired. If the item was never used in the current entity, it will be deleted from the current entity. If the current entity is the last or only entity in which the item exists, and the item was never used in the entity, it will be deleted from XFRACAS. If the item was used in the current entity, then it will be retired for the entity. If an item is retired, it will no longer be available to assign to an XFRACAS record for the current entity. However, it will continue to be associated with any existing records. In addition, if the item is associated with any other entities, it will still be available for those entities.

More Issues opens the Edit Issue List utility, which allows you to access all issues of the current issue type from other entities and select them for use in the current entity (i.e., use the same issues across multiple entities).

Lists

You can use the Lists page to manage standard lists and any lists that were added to the current entity via the Details page. Therefore, the lists that appear in your system may vary. Note also that some of the issues are required in XFRACAS. If you attempt to delete them, you will receive an error from XFRACAS and will not be able to delete them. Selected information about some of the standard lists is given next.

The Attachment – Record Association Type list defines the relationships that can be assigned when attaching an XFRACAS record to another XFRACAS record via the Attachment Information utility. You cannot delete these issues.
The FA ATP Test Result list defines the Acceptance Test Procedure (ATP) test results that can be assigned to a failure analysis report.
The Incident Category Chargeable list defines the chargeable (reliability-wise) incident categories that can be assigned to an incident report. These categories, along with the Incident Category Non-Chargeable categories, will appear in the Incident Category drop-down list and will help determine if the failure is treated as a failure or as a suspension for reliability calculations. Note the interaction between the incident category and the failure type:
- If the incident category is non-chargeable, the incident is non-chargeable.
- If the incident category is chargeable, then:
- - If at least one repaired/replaced part in the Incident Repair Information area has a chargeable failure type, the incident is chargeable.
  - If all repaired/replaced parts in the Incident Repair Information area have non-chargeable failure types, the incident is non-chargeable.

Examples of chargeable incident categories might include component failure (i.e., the part simply stops working), design issue or production error (i.e., the part was not built correctly or assembled correctly by the manufacturer). Examples of non-chargeable incident categories might include installation issue, operator error, software configuration problem or end of useful life.

The Incident Failure Type Chargeable list defines the failure types that represent chargeable part failures that can be assigned to an incident report. These failure types, along with the Incident Failure Type Non-Chargeable failure types, will appear in the Failure Type drop-down list in the Replace Part utility and Repair Part utility. Note the interaction between incident category and incident failure type listed above. Primary failure is considered a chargeable failure type. Primary suspension, collateral failure and collateral suspension are considered non-chargeable failure types.
The Incident Parts Disposition list defines the part disposition classifications that can be assigned to describe the disposition of a replaced or failed part via the Replace/Repair Parts utility.
The Incident System Status list defines the system statuses that can be assigned to a serialized system on the Incident page.
The Output Record Count list defines the number of records that can be selected in the Report Builder's Records per Page field, which determines the number of records that are displayed on each page of the report results.

Issue Utility

The changes made in the Issue utility will apply to all records that have already been associated with that issue. If you do not want the changes to apply to existing records, you can retire the existing issue and create a new issue with the new information, which allows you to add a new issue or a new issue with associated parts to the list or to associate additional part number(s) with an existing issue for the current entity or for other entities that you have access to.

The appearance of this utility will vary depending on whether the issue is associated with parts. For issues not associated with parts, you can specify the following:

The issue Description is the text that will be displayed in the list in the user interface. You cannot edit the description if the issue is used in an entity you do not have access to.
The issue Code indicates the issue’s priority in relation to the other issues in the list.
If you select the Default check box, the issue will be set as the default item and will be displayed by default in the list in the user interface. Please note that the issue will then be removed from all other entities. The Default check box will be unavailable if the issue is used in an entity you do not have access to.
If you enter an E-mail Address, an e-mail will be sent to that address when the issue is selected. This option is available only for drop-down field issues.
The Entities that you want the issue to be associated with.
Additional fields may be available depending on the field type that you are working with:
- For "Attachment - Record Association Type" issues, you can select an issue from the Reciprocal drop-down list to create a link between the two issues. When attaching an XFRACAS record to another XFRACAS record, if the selected relationship type has a reciprocal, then any reciprocal attachment created by the user will automatically be of that reciprocal type. For example, let's say a user is working with incident E1-1 and wants to attach incident E1-17 as a superseding incident. If the "superseding" issue is set up to have the "superseded" issue as its reciprocal and the user specifies a Reciprocal Section, then incident E1-17 will be attached to E1-1 as a superseding incident and E1-1 will be attached to E1-17 as a superseded incident.
- For issues associated with fields using drop-down lists, you can enter an E-mail Address for the issue. When the issue is selected, the e-mail address will receive an e-mail with a link, stating that the recipient should review the page.
- For tree issues, Parent allows you to change the parent of an issue, including the ability to make a child issue into a top-level issue or vice versa. This option is available only when you are editing an existing issue; the initial position of an issue is determined by whether you whether you had an existing issue selected when adding it (in which case the new issue is added as a child issue) or not (in which case it is added as a top level issue).

Save saves the issue properties and closes the window. If you are editing a retired issue, this button will change to Un-Retire. Note that when you return to the Lists page, the issues for the list you have just saved will refresh, but the rest of the utility will not refresh.