step

The <step> element represents an action that a user must follow to accomplish a task. Each step in a task must contain a command <cmd> element which describes the particular action the user must do to accomplish the overall task. The step element can also contain information <info>, substeps <substeps>, tutorial information <tutorialinfo>, a step example <stepxmp>, choices <choices> or a stepresult <stepresult>, although these are optional.

Contains

(cmd then (info or substeps or tutorialinfo or stepxmp or choicetable or choices) (any number) then (stepresult) (optional) )

Contained by

steps, steps-unordered

Inheritance

topic/li, task/step

Attributes

Name	Description	Data Type	Default Value	Required?
importance	The attribute indicates whether the element it modifies is optional or required.	optional \| required	#IMPLIED	No
%select-atts;	A set of related attributes, described at select-atts. Note: For this element, the attribute importance has only the values "required" and "optional."
%id-atts; (id, conref)	A set of related attributes, described at %id-atts;	parameter entity	PE not applicable	Not applicable
translate	Indicates whether the content of the element should be translated or not.	yes \| no	#IMPLIED	No
xml:lang	Specifies the language of the element content. When no xml:lang value is supplied, the default value of English is assumed. For example, if there is a note element with the attribute xml:lang set to the value "es-es," then the label on the note, which is normally output as "Note" is now output in Spanish as "Nota." The allowed xml:lang values are based on ISO-3166 Country Codes and RFC 3066 Language Codes (see W3C: Language tagging in HTML and XML).	NMTOKEN	#IMPLIED	No
%global-atts; (xtrf, xtrc)	A set of related attributes, described at %global-atts;	parameter entity	PE not applicable	Not applicable
class, outputclass	Common attributes described in Other common DITA attributes

Example

<task id="sqlj">
<title>Creating an SQLJ file</title>
<taskbody>
<context>Once you have set up SQLJ, you need to create a new SQLJ file.
</context>
<steps>
<step><cmd>Select <menucascade><uicontrol>File</uicontrol><uicontrol>New</uicontrol>.</cmd>
<info>New files are created with default values based on a standard template.</info>
</step>
</steps>
</taskbody>
</task>