The Incident nodes expose the following functionality:
- Create an Incident via the
NL Incident Createnode. Most NL nodes will do this automatically, but this provides a way to explicitly create an Incident for the active message.
- Add a Note to a new or existing Incident via the
NL Incident Add Notenode.
- Set the Incident name via the
NL Incident Set Namenode.
- Set the Incident status to
Closed by Flowvia the
NL Incident Set Statusnode.
- Get the Incident’s timelines URL via the
NL Incident Get Timeline URLnode.
- Set the Incident’s Category via the
NL Incident Set Categorynode.
Adds a note to the Incident's timeline as defined by the configuration settings. When a message arrives, the Incident's timeline is updated with a new note. The note is generated using a user-specified set of rules.
Creates an Incident for the incoming message. This is to create a tracking point for incidents in the flow. The message continues through the node unaltered. If the Incident already exists, nothing is done.
Sets the name of the Incident as defined by the configuration settings. When a message arrives, the node will rename the Incident based on a user-specified set of rules.
Utility node to change the status of the Incident, i.e. the current message in the flow, to either opened (
Open) or closed (
Closed by Flow). An Incident is automatically created by any Nevelex Labs node included in the flows when a message is received by the node. If this node is the first Nevelex Labs node in the flow, it will create a new Incident with the desired status. For more information on status changes see Incident Statuses and Transitions.
Node to retrieve the Incident timeline URL and add the URL into the
msg.__sfMeta__meta data object. Upon receiving a message on the input, this node adds the
urlfield into the
msg.__sfMeta__pathway of the message.
It is not recommended to use this node before a node which aggregates Incidents, since the URL may change.
This node sets the category for the Incident containing the current message.
Categorynames are case-sensitive. If the supplied
Categorydoes not match an existing category, a new category is automatically created. If the
Categoryis not supplied, no category is assigned to the active Incident.
The NL incident nodes used in the following screen shot are configured to:
- Create an Incident
- Add a note saying “Hello”.
- Set the incidents name to the current date and time.
- Close the incident
The flow used in this example is shown below.
The Incident’s timeline is shown below.