The bot will directly perform actions in Ivanti (HEAT or Neurons) to create, update, and query information about tickets.
The Moveworks service interacts with your Ivanti instance so that the bot can:
To perform the actions listed above, Moveworks needs a service account in our Ivanti instance.
A dedicated service account in Ivanti allows the Moveworks service to read, create and update tickets, as well as read user information.
If you have an Ivanti sub-prod instance (test/dev/sandbox etc.), create a service account in this instance as well.
This account is used for testing. Please grant access to an instance that is the closest to what is deployed in your prod instance for the Moveworks Team.
Navigate to Settings → Users and Permissions and create a new user for Moveworks.

Next, navigate to Settings → Users and Permissions → Roles and Permissions
Create a new role called Moveworks and edit the permissions.

Add the necessary permissions for the Moveworks bot.

Login into the instance as admin and click on Configure Applications

Now click on Security Controls → API Keys located in the left navigation bar.

Add a key group for Moveworks.

Add a new API key.

In the subsequent page, add the following:
Moveworks<name of service account created in previous section><name of role created in previous section>
Copy the API key and share with your Moveworks team.

When relevant, the Moveworks bot can serve Service Requests to end users to help resolve their question or request. The URLs for these Service Requests must be exported out of Ivanti Neurons and shared with the Moveworks team.
Login as an administrator.
Navigate to More.. → Request Offering

The list of all available forms (Published & Unpublished) will be shown.
Click on the Name of the form to view details.
In the Define request offering tab click the Direct Link to this offering button.

Copy the Direct link.
Repeat steps 4 through 6 for all forms.