- cause
The <cause> element describes a potential source of the problem that is addressed by the troubleshooting topic.
- condition
The <condition> element describes a state that the troubleshooting topic is intended to remedy. This information helps the user decide whether a troubleshooting topic might contain an applicable remedy for a problem.
- diagnostics
The <diagnostics> element contains information that helps readers determine the cause of a problem.
- diagnostics-general
The <diagnostics-general> element includes non-procedural information that can help determine the causes of a symptom. Results of the diagnoses might link to possible solutions.
- diagnostics-steps
The <diagnostics-steps> element includes step-by-step information that can help readers determine the causes of a symptom. Results of the diagnostic steps might link to potential solutions.
- remedy
The <remedy> element contains steps that are a potential solution for a problem. In addition, it also might contain information about the person or team who can perform the task.
- responsibleParty
The <responsibleParty> element identifies the individual or team whose task it is to perform a remedy procedure. It also can provide important information about the qualifications that the person or team must have.
- troublebody
The <troublebody> element contains the main content of the troubleshooting topic. The troubleshooting body can contain information about the condition, how to diagnose the cause, and one or more possible solutions.
- troubleshooting
The <troubleshooting> element is the top-level element for a troubleshooting topic. Troubleshooting topics provide information that enables readers to identify a condition, diagnose a cause, and potentially fix the problem.
- troubleSolution
Each <troubleSolution> element contains information about the cause of a problem and a potential remedy.