...
Extension Designer ships with several nodes specific to Parasoft functionality.
| Scroll Table Layout | ||
|---|---|---|
|
| Component | 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.
| ||||||
|---|---|---|---|---|---|---|---|
Parameters | 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 | 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:
| ||||||
| Profile Search | 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. | ||||||
| PC REST API | This general purpose node makes requests the Policy Center REST API.
Open the following URL in a browser to view the Policy Center REST API documentation and learn about the available endpoints: http://<HOST>:<PORT>/apidoc | ||||||
DTP REST API
| This general purpose node makes request to the DTP REST API. See REST API for information about endpoints in DTP.
There may be instances in which a DTP REST API node shows a persistent "requesting" message.
Check the $DTP_SERVICES_HOME/logs/<service UUID>.log file or the $DTP_SERVICES_HOME/logs/main.log file 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 | This node gathers the DTP server information set in the configuration page (see DTP Enterprise Pack Configuration).
| ||||||
| DTP Store Metrics | 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 | This node gets DTP user information.
| ||||||
| Database | 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 | This node is used to subscribe to MQTT events from the event broker.
| ||||||
| Event Out | This node publishes a event.
| ||||||
This node can sent emails using the SMTP mail server defined in the Configuration tab. See DTP Enterprise Pack Configuration.
| |||||||
| i18n | This node stores localization information. |
...
The node is pre-loaded with useful libraries:
| Scroll Table Layout | ||
|---|---|---|
|
| lodash | Add the following line to your function node to initialize lodash and make its functionality is available.
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.
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.
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.
Node Markings
| Scroll Table Layout | ||
|---|---|---|
|
| Input node |
| Nodes process data from left to right. A white square on the left hand side indicates that the node can receive inputs from a message object. The node's documentation will describe the expected input “msg” format. |
|---|---|---|
| Output node |
| A white square on the right hand side indicates that the node can output payload data. If there is more than one icon on the right hand side, it means that the node can output multiple sets of data. |
| Nodes with inputs and outputs |
| If a node has squares on both the left and right, it means it accepts inputs from a message object and can output payload data. For details on the expected inputs and outputs, see each node's on-line documentation (select the node, then review the details in the Info tab). |
| Node with missing configuration |
| A red triangle indicates that all required fields are not properly configured. Double-click the node to find out what field(s) require additional configuration (they will be marked with a red box, like the URL field below), then update the node accordingly. |
| Unsaved node |
| This blue circle indicates that the node is not yet saved in the server. If there is any node with a blue circle icon, the Deploy button will become active. |
...