<NODISPLAY>

No-display cards do not appear on the phone. Instead, they immediately execute the ACCEPT or PREV action. They are useful for initializing variables.

Statement	Description
`<NODISPLAY`	Beginning of the No-Display header.
`name=card_name`	A name for the card. Tasks can specify this name as a destination.
`>`
`actions`	In general, the phone automatically executes the `ACCEPT` actions when the user navigates forward to the card and the `PREV` actions when the user navigates back to the card. For the exact behavior with specific task types, see the table below. The phone executes only the `ACCEPT` and `PREV` actions defined for the no-display card; it ignores all other actions.
`</NODISPLAY>`	The no-display header.

The following table lists the task types that can invoke a no-display card and the actions the phone executes in the no-display card.

Invoking task type	No-display action executed by phone
`GO`	`ACCEPT`
`GOSUB`	`ACCEPT`
`RETURN`	`PREV`
`PREV`	`PREV`
`CANCEL`	`PREV`
`RETURN` or `CANCEL` with `DEST` specifying the No-Display card	`ACCEPT`
`RETURN` with the `NEXT` option of the calling card specifying the no-display card	`ACCEPT`
`RETURN` with the `CANCEL` option of the calling card specifying the no-display card	`ACCEPT`