node-red-contrib-agilite/numbering/numbering.html

Node-RED nodes to integrate with Agilit-e cloud or Agilit-e on-prem

<script type='text/javascript'>
  RED.nodes.registerType('numbering',{
    category: 'agilite',
    inputs: 1,
    outputs:1,
    icon: 'numbering.png',
    color: '#ffa4a2',
    label: function () {
      return this.name || 'Numbering'
    },
    paletteLabel : 'numbering',
    defaults : {
      server: { value : '', required: true, type: 'agilite-login' },
      profileKey: { value : '' },
      name: { value:'' },
      field: { value: 'payload' },
      fieldType: { value: 'msg' },
      failFlow: { value: true }
    },
    oneditprepare: function () {
      if (!this.fieldType) this.fieldType = 'msg'
      
      $('#node-input-field').typedInput({
        default: 'msg',
        types: ['msg','flow','global'],
        typeField: $('#node-input-fieldType')
      })
    }
  })
</script>

<script type='text/x-red' data-template-name='numbering'>
  <div class="form-row">
    <label for="node-input-server"><i class="fa fa-server"></i> Server</label>
    <input type="text" id="node-input-server" placeholder="Server"></input>
  </div>
  <div class="form-row">
    <label for="node-input-profileKey"><i class="fa fa-key"></i> Profile Key {{}}</label>
    <input type="text" id="node-input-profileKey" />
  </div>
  <div class="form-row">
        <label for="node-input-field"><i class="fa fa-edit"></i> <span data-i18n="template.label.property">Output to</span></label>
        <input type="text" id="node-input-field" placeholder="payload" style="width:250px">
        <input type="hidden" id="node-input-fieldType">
  </div>
  <div class="form-row">
    <label for="node-input-failFlow"><i class="fa fa-exclamation-triangle"></i> <span data-i18n="template.label.property">Fail Flow on Error</span></label>
    <input type="checkbox" id="node-input-failFlow" style="width:initial" /> Yes
  </div>
  <div class="form-row">
    <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
    <input type="text" id="node-input-name" placeholder="Node Name" />
  </div>
</script>

<script type='text/x-red' data-help-name='numbering'>
  <p>A node to have Agilit-e generate a unique number based on the provided Profile Key.</p>
    <h3>Inputs</h3>
    <dl class="message-properties">
      <dt>Server (required)<span class="property-type">Configuration Node</span></dt>
      <dd>The server configuration to connect to the relevant Agilit-e API Server. This is achieved by providing the API Server URL (required) and an API Key (optional). <b>NOTE:</b> If providing an API Key, be sure to click on the "Authenticate" button, to have Node-RED authenticate the API Key before the Server configuration is used by Nodes.</dd>
      <dt>Profile Key (required)<span class="property-type">string</span></dt>
      <dd>The unique <b>key</b> of the Numbering Profile to be used to generate unique numbers.</dd>
      <dt>msg.payload<span class="property-type">object</span></dt>
      <dd>
        Optional data to be passed to Agilit-e for Handlebars evaluations in the relevant module's Profile. Example:
        <code>msg.payload = { prefix: "PRE-", suffix: "-SUF" }</code>
      </dd>
      <br />
      <p style="margin: 0 5px 0 5px"><b>NOTE:</b> Values can be provided manually in the Input Fields in this Node's UI Form, or programmatically using <a href="https://handlebarsjs.com/" target="_blank">Handlebars</a>, where the Input Field's Label includes <code>{{}}</code>. Labels with <code>{{}}</code> are <b>Handlebars-enabled</b> and evaluate prop values relative to the <code>msg</code> object (e.g. <code>{{profileKey}}</code> = <code>msg.profileKey</code>). A final note: The difference between using 2 curly braces vs 3, is that values evaluated using 2 curly braces are first encoded/escaped before evaluated, whereas values using 3 curly braces are not. It is usually safer to use 3 curly braces, but in most cases 2 will work fine.</p>
    </dl>
    <h3>Outputs</h3>
    <dl class="message-properties">
      <p style="margin: 0 5px 0 5px">By default, this Node will output the result to <code>msg.payload</code>. This can be changed in the Node UI Form's <b>Output To</b> Field</p>
    </dl>
    <h3>Additional Properties</h3>
    <dl class="message-properties">
      <p style="margin: 0 5px 0 5px">By default, if an error occurs, this Node will fail and stop the flow from continuing. This can be switched off in the Node UI Form's <b>Fail Flow on Error</b> Field. This allows one to manually manage the error by referencing the <code>msg.agilite.succcess</code> and <code>msg.agilite.errorMessage</code> prop values.</p>
      <br />
      <p style="margin: 0 5px 0 5px">The following properties can be set in the <code>msg.agilite</code> object:</p>
      <dt>logProfileKey <span class="property-type">string</span></dt>
      <dd>The unique <b>key</b> to the Batch Logging Profile used for custom logging.</dd>
      <dt>apiKey <span class="property-type">string</span></dt>
      <dd>The Agilit-e API Key used to authenticate the Agilit-e transaction. This is not required if you've set up a Configuration Node that already has an API Key which has been authenticated.</dd>
    </dl>
</script>