node-red-camunda8
Version:
Camunda 8 nodes for Node-RED
78 lines (69 loc) • 2.74 kB
HTML
<script type="text/javascript">
RED.nodes.registerType('resolve-incident', {
category: 'camunda',
color: '#F3B567',
defaults: {
name: { value: '' },
camunda: { required: true, type: 'camunda' },
},
inputs: 1,
outputs: 1,
icon: 'resolve-incident.svg',
label: function () {
return this.name || 'resolve incident';
},
paletteLabel: 'resolve incident',
});
</script>
<script type="text/x-red" data-template-name="resolve-incident">
<div class="form-row">
<label for="node-input-name"><i class="icon-tag"></i> Name</label>
<input type="text" id="node-input-name" placeholder="Name">
</div>
<div class="form-row">
<label for="node-input-camunda"><i class="fa fa-server"></i> Camunda Broker</label>
<input type="text" id="node-input-camunda" placeholder="Camunda Broker" />
</div>
</script>
<script type="text/x-red" data-help-name="resolve-incident">
<p>Resolves process incidents programmatically. This enables automated incident resolution and reduces manual intervention in production environments.</p>
<h3>Inputs</h3>
<dl class="message-properties">
<dt>payload.incidentKey <span class="property-type">string</span></dt>
<dd>The key of the incident to resolve.</dd>
</dl>
<h3>Outputs</h3>
<ol class="node-ports">
<li>Standard output
<dl class="message-properties">
<dt>payload <span class="property-type">object</span></dt>
<dd>Original payload with added incident resolution confirmation.</dd>
</dl>
</li>
</ol>
<h3>Details</h3>
<p>This node provides the ability to resolve incidents automatically. This is useful for:</p>
<ul>
<li>Automated incident resolution workflows</li>
<li>Reducing manual administrative overhead</li>
<li>Improving process reliability</li>
<li>DevOps automation scenarios</li>
</ul>
<h3>Usage Example</h3>
<p>To resolve an incident, send a message with the following payload:</p>
<pre>
{
"incidentKey": "12345678901234567"
}
</pre>
<p>The incident will be resolved and confirmation will be added to the payload.</p>
<h3>Details</h3>
<p>Incidents in Camunda 8 occur when:</p>
<ul>
<li>Job execution fails repeatedly</li>
<li>Input/output mapping errors occur</li>
<li>External system timeouts happen</li>
<li>Data validation failures occur</li>
</ul>
<p>This node enables automated recovery by resolving incidents programmatically, often after correcting the underlying issue.</p>
</script>