The following are the new features for September 2023:
Validate button in the Calculator step:
The Calculator step now has a Validate button feature! This is used to validate the JavaScript code in the step. The validation errors will be listed and displayed on the step itself as shown in the example below after clicking on the Validate button.
If the code is valid, a message will be displayed as shown in the image below.
AMS 360 WSAPI Lookup Mapper Step:
An AMS 360 Lookup step is now available!
Click on the ‘plus’ button highlighted in the image below to add a new connection or alternatively select an existing connection from the dropdown list. Entities can be selected by clicking on the Entity dropdown list. The Mappings section allows you to map fields from the lookup object to the current record. An action will occur when a record is not found in the On Not Found section by selecting an option.
The Enable Caching checkbox will enable caching of results so that the results are fetched only once for a specific ID. The Retry field can be enabled by clicking on the Enable checkbox; a Delay field and the Times field (number of retries) that can be made will appear. Input the required values and save the step. In the example shown in the image below, it would retry five times and the delay is 30 seconds in between those five retries.
AMS 360 WSAPI Destination Step:
Records can be sent to AMS 360 using the AMS 360 WSAPI Destination step! Click on the ‘plus’ button highlighted in the image below to add a new connection or alternatively select an existing connection from the dropdown list. Entities can be selected by clicking on the Entity dropdown list. The Retry field can be enabled by clicking on the Enable checkbox; a Delay field and the Times field (number of retries) that can be made will appear. Input the required values and save the step.
NetSuiteQL Connection:
A NetSuiteQL connection is now available! A NetSuite Account ID is required to create a connection. The Connection Type is automatically set to Token Based Authentication where all the fields are required. Input the credentials and then click the Save button to save the connection.
Click on the link below to view the NetSuiteQL API reference document:
NetSuite SuiteQL Source Step:
Data can now be retrieved from NetSuite SuiteQL using the NetSuite SuiteQL Source Step. Click on the ‘plus’ button highlighted in the image below to add a new connection or alternatively select an existing connection from the dropdown list. Type the SQL command in the Command section. The Paged checkbox will enable paging on the route. The Paging Offset section allows you to include the offset element. Type in the required number or click the button on the side to increase or decrease as required. The Page Size field and the Limit field can be modified.
Applied Epic Connection:
A connection to Applied Epic is now available. The page below illustrates the credentials that are required to create a connection. Input an Account, Database Name, and Authentication Key. Once the credentials are inputted, you can click on save and test the connection by clicking on the Test button.
Applied Epic SDK SOAP Source Step:
Data can be retrieved from Applied Epic using the Applied Epic SDK SOAP Source step . Click on the ‘plus’ button highlighted in the image below to add a new connection or alternatively select an existing connection from the dropdown list. The Route field and Operation field have a default configuration and can be modified. The Operation Body section is where the API, XML or JSON can be configured.
Click on the link below to view the Applied Epic API reference document:
NB: To view the full documentation, a WSDL is required.
JWKS Endpoint Type Field in the REST API Builder/Gateway:
An JWKS Endpoint Type Field is now available in the REST API Builder/Gateway. Select the Type (either Endpoint or Document) of JWKS resource by clicking on the drop-down list. The Endpoint Type has been selected in the example below. Type in the Endpoint URL and save the security scheme.
Enforce Input Schema on Buffers in the REST API/Gateway:
The Enforce Input Schema on Buffers feature on the Buffer in the REST API/Gateway is a checkbox feature that can be ticked to enforce the validation of a set structure. It will perform a validation before it sends data to the buffer. If it finds that the schema does not match the provided structure, it will reject the request and give an error message. This feature is only available for the POST, PUT and PATCH methods.
