Overview
The node integrates with an ABMS (presumably a backend management system) web service, allowing users to perform various operations such as creating, deleting, describing, querying, retrieving, and updating elements within the system. The "Sync" operation is listed but not implemented in the provided code.
This node is useful for automating interactions with the ABMS API, enabling workflows that manage data entities programmatically. For example, it can be used to create new records, query existing data, or update elements based on external triggers or schedules.
Since the "Sync" operation is not implemented, this summary focuses on the general capabilities of the node and the "Sync" operation's placeholder status.
Properties
| Name | Meaning |
|---|---|
| Session Name | A required string representing the session identifier obtained through a prior login operation. It is used to authenticate subsequent requests. |
Note: The "Session Name" property is hidden when the operation is "login" because it is not needed for logging in.
Output
The node outputs a JSON array containing the response from the ABMS web service for the requested operation. The structure of the JSON depends on the specific operation performed and the ABMS API response format.
No binary data output is indicated in the source code.
Dependencies
- Requires an API credential with host URL, username, and access key to authenticate requests.
- Uses HTTP requests to communicate with the ABMS web service endpoint
/webservice.php. - Uses the
crypto-jslibrary to generate MD5 hashes during the login operation for secure authentication.
Troubleshooting
- Unimplemented Operations: The "Sync", "Extend Session", and "Logout" operations are not implemented and will throw errors if used. Users should avoid selecting these operations until support is added.
- Login Failures: If the login operation fails, the node throws an error with the message and code returned by the ABMS API. Common causes include incorrect credentials or network issues.
- Session Name Requirement: Most operations require a valid "Session Name" obtained from a successful login. Using an invalid or expired session name will likely cause API errors.
- HTTP Request Errors: Network connectivity problems or incorrect API host configuration may result in request failures.
Links and References
- No external links or documentation references are provided in the source code. Users should consult the ABMS API documentation for detailed information about supported operations and expected request/response formats.