Neurons Bots Stages

Used to present and filter information from devices that meet the specified criteria. The output and context from this query stage can be passed through subsequent stages in the bot.
For example, show devices with less than 10% free disk space.

Action stages leverage Automation Fabric to perform actions. Use of variables is available for some actions. Learn more about Stage variables.

• Filter Results: You can filter query results based on customizable properties. Once you connect a built-in Query Stage to a Filter, the Property drop-down lists all available properties that can be selected. To view details of the properties, go to the query Stage Settings panel and select Stage Information.
• You can also use the Preview Query functionality to assess all targeted devices, and use the results table to view the format and range of values that can be filtered.
• You have the ability to join multiple queries together in sequence. If this is done, all results are combined and available to filter on, or use in Action Stages. You can change the comparison behavior of the connected filter so that it either applies either AND or the OR logic to determine the results.
• Join: Use this stage to re-merge a bot that has split down separate branches. In the Stage settings, select the join behavior; Any state, All succeeded, At least one succeeded.
• Set Variable: Use this stage to provide a consistent reference point that can be configured with default values and updated by stages based on results. This is useful when you want to use a single variable to reference a field which might be updated from queries across different branches. The variables that you can set are defined in Define variables.

• Delay: Use this stage to set the workflow on hold for a predetermined amount of time. It delays the execution of the upcoming stage based on the time configured in the delay stage. In the stage settings, select the delay duration time in minutes, hours, and days. The maximum possible delay you can set is for seven days, and the minimum delay is one minute. This stage is helpful for waiting for a user to reply to a message or for a process to finish.

Stages for early access are available here. Beta stages are offered to enable Ivanti to gather feedback and data around upcoming features.

Custom stages allow you to execute a custom script. You can choose from the following scripting templates:

• osquery: an open source SQL based language that can be used to query and retrieve information from devices and supports Windows and macOS devices.
• PowerShell Query: can be used to query Windows and macOS devices. It can run as system or logged-on user.
• Bash Action: can be used to perform actions on macOS devices.
• Command Action: executes Windows command prompt commands on the target endpoint. It can run as system or the logged-in user.
• Powershell Action: can be used to perform actions on Windows devices.

Learn more about Custom Stages

List function stages allow you to perform actions on stage results that are a list. You can, for example, filter, sort, count, or sum the list.
If the result of a List function stage is again a list, you can add another List function to further refine the result.

In the work area, you can recognize a stage that (is expected to) return a list result by the List tag.

To apply a List function stage in your workflow:

1. Add a stage that has a list result.

2. Add the desired List function.

3. Using , connect the stages from step 2 and 3.
   This will populate the value(s) for Select List on the List function stage.

4. Select the List on which you want to perform the List function.

5. Depending on the List function, complete the remaining configuration of the stage.

6. Complete the rest of your bot workflow and save your changes.

Interaction stages allow a bot to interact with and collect input from end users using Microsoft Teams. You can choose from the following interaction stages:

• MS Teams Interaction: Allows a bot to interact and collect input from an end user through Microsoft Teams. The message comprises a title, a message, and a choice of interaction: buttons or free text input.
• MS Teams Message: Allows a bot to send one-way messages to end users using Microsoft Teams. The message comprises a title and a message.
• MS Teams Rating: Allows a bot to interact and collect ratings from an end user through Microsoft Teams. The message comprises a title, a question, and a rating.
• MS Teams Sentiment: Allows a bot to interact and collect input from an end user through Microsoft Teams. The message comprises a title, a message, and a choice of interaction: buttons or free text input.

To learn more, refer to MS Teams Stages.

User stages are custom scripted stages. They are saved and made available in this User section for multiple reuse in bot creation.

Learn more about User Stages.

Bot Name: Name of the current bot.

Initiation User: Name of the user who initiated the bot. This will either be a user, or a Neurons service.

Initiation User ID: User ID of the initiating user. This will either be a user ID, or a Neurons service.

Timestamp (ISO): Current timestamp in ISO format.

Device Name: Gets the device name for current device within the current stage. Device names returned are separated by commas.

All Device Data: Gets all data for current device within the current stage. This will be a JSON object.

Given Name: Name of the logged on end user.

Display Name: Full name of the end user.

Email: Email for the end user.