Rejected

Indicates that the form completed the workflow, but that is was not accepted by at least one authorizing Role or Person, or did not pass all processes, or encountered an Exception.

Other Rejected node practices:

• There must always be one Rejected node defined per workflow.
• Like Accepted nodes, workflows can also contain multiple rejected nodes so that users are able to tailor the messages that are generated by these nodes.
• The Rejected node can receive more than one connector; the Rejected node is attached to the end of all Failure and No connectors in the workflow.
• Connections cannot originate from the Rejected node.

Property	Description	Sample Value	Mandatory or Optional	Notes
Description	Brief description of the node.	Form rejected.	Optional
Icon	The *.GIF image that represents the Rejected icon.	rejected.gif	Mandatory	Defaults to rejected.gif.
Name	Name assigned to the icon. The name is displayed directly underneath the icon in the workspace. The name assigned should be relevant to the node purpose.	Rejected1	Mandatory	Defaults to Rejected1.
Message	The message that is displayed to the employee.	"Your request has been accepted.”