Actions for Halo Service Solutions #
- Send Data to Halo Service Solutions. Sends a custom set of Lucidum data to Halo Service Solutions.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Halo Service Solutions on a regular schedule.
- You can send normalized, enriched Lucidum data to Halo Service Solutions to be indexed, searched, and analyzed.
Prerequisites #
To execute Halo Service Solutions actions, you must configure a Halo Service Solutions API connection beforehand. For details, see https://halo.haloservicedesk.com/apidoc/authentication/client.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
Halo Service Solutions Configuration #
To create a configuration for Halo Service Solutions actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. URL of your Halo Web Application instance.
-
Client ID. The client ID for a Halo account that has read and write access to the Halo API. For details, see https://halo.haloservicedesk.com/apidoc/authorisation and https://halo.haloservicedesk.com/apidoc/authentication.
- Client Secret. The client ID for a Halo account that has read and write access to the Halo API. For details, see https://halo.haloservicedesk.com/apidoc/authorisation and https://halo.haloservicedesk.com/apidoc/authentication.
-
Max # of Records per Payload. The maximum number of records to send to Halo Service Solutions in each action. The default value is “50”.
Create a New Action #
To create an action for Halo Service Solutions, contact Lucidum customer care.
