Versions Compared

Old Version 2

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version Current

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 2024.1

...

Table of Content Zone
locationtop

Component Node

The Component node is used to create reusable front end web components. This node, as well as the Parameters node, is called by the Endpoint node and must be configured to create front end components. You can import pre-programmed sample Component nodes from the library. See Creating Custom DTP Widgets Using Extension Designer for details.

Parameter Node

The Parameters node is used to create reusable front end web components. This node, as well as the Component node, is called by the Endpoint node and must be configured to create front end components. You can import pre-programmed sample Parameters nodes from the library. See Creating Custom DTP Widgets Using Extension Designer for details.

 

Endpoint Node

The Endpoint node exposes a service endpoint that encapsulates all the functionality necessary to create a full-stack web component. The Endpoint node references the Component and Parameters nodes, which must be configured for this node to function.

You can implement multiple instances of the same flow when in your services, but if your flows contain Endpoint nodes, then the UUID for each node must be different. Otherwise, only the first instance of the flow will be read. You can manually change the UUID or delete it and re-save the node with an empty UUID field. Saving the empty field will generate a new UUID unique to that instance.

You can configure the Endpoint node to expose the following types:

  • General: The General endpoint does not have a UI component. It can be used for general request/response scenarios (for example, triggering a flow via a cURL command).
  • Parameter Values: The Parameter endpoint type is used to control the contents of dropdown menus in the widgets you are creating. See Configuring Parameter Nodes.
  • Report: The Report endpoint type points to a Component node configured to display a drill-down report and its associated Parameters node.
  • Widget: The Widget endpoint type points to a Component node configured to display a widget and its associated Parameters node.

Profile Search Node

The Profile Search node gathers model profiles to be used in the flow.

You can perform finer searches by specifying additional search parameters in the Additional attributes section.

If a report schema has additional attributes assigned to it, then individual report profiles can be found by adding key/value pairs to the additional search parameters which match those additional attributes.

The key/value pairs created in this area can also mustache values ({{property}}) from the msg object that is passed to the node.

DTP REST API Node 
Anchor
dtp-rest-api-node
dtp-rest-api-node

This general-purpose node makes request to the DTP REST API. See Using DTP REST APIs for information about endpoints in DTP.

There may be instances in which a DTP REST API node shows a persistent "requesting" message.

Check the <SERVICE_UUID>.log or main.log file in the $DTPthe <DTP_SERVICES_HOMEHOME>/logs/ directory for error messages. In most instances, this issue is related to the service attempting to send a very large payload to the DTP REST API. Reduce or split the payload and make multiple connections to post the data.

DTP Server Info Node

This node gathers the DTP server information set in the configuration page (see DTP Enterprise Pack Configuration).

DTP Store Metrics Node

This node allows you to define a new metric type and send the new metric results to DTP in order to store custom metrics.

Get User Node

This node gets DTP user information.

Database Node

This node allows you to interact with the Enterprise Pack database. You can use the node to persist data across flow invocations and service restarts.

Event In Node

This node is used to subscribe to MQTT events from the event broker.

Event Out Node

This node publishes an event.

Mail Node

This node can send emails using the SMTP mail server defined in the SMTP Settings.

i18n Node

This node stores localization information.

Function Node

The function node is not a Parasoft-specific node, but it is an important part of nearly every flow. You can write your own logic for your flow by adding JavaScript to the node. The function node is in the function palette. 

The node is pre-loaded with useful libraries:

Scroll Table Layout
widths30%,70%

lodash

Add the following line to your function node to initialize lodash and make its functionality is available.

var _ = context.global.lodash;

See https://lodash.com/docs to learn more about this utility library.

moment

This utility library is used to manipulate date and time in your flows. Add the following line to your function node to initialize moment and make its functionality is available.

var moment = context.glboal.moment;

See https://momentjs.com/docs/moment to learn more about this utility library.

os

This module from node.js detects operating system-specific information. Add the following line to your function node to initialize os and make its functionality is available.

var os = context.global.os;

See https://nodejs.org/api/os.html to learn more about this utility library.

Click on the following link to learn more about the function node: https://nodered.org/docs/writing-functions.

...