Non-interactive tasks automatically start and complete without user intervention once they have been started.
This table provides a summary description of each of the Non-Interactive tasks:
| Task | Description | Task Type |
| Run Report Book | This task runs a predefined report book for Anaplan XML Reports. | Reporting |
| Generate Anaplan XL Reporting Report | This task generates an Anaplan XL report that can be published to an Azure File Storage, an FTPS location, or Explorer. | Reporting |
| Send Email | This task emails a message. | Notification |
| Send Message | It sends a message to a Slack or Microsoft Teams channel. | Notification |
| Application Integration | These tasks are used to integrate directly with external ETL tools such as Azure Synapse Analytics or Azure Data Factory. This enables Anaplan workflow to execute a process, or pipeline as part of the workflow, that runs an ETL process to import data into the staging tables. Application Integration is available for Azure Data Factory as well as Azure Synapse Analytics. | Application |
| Automated Import | In an automated import, the data import runs without user interaction. These tasks enable the creator of a workflow to reference file storage locations such as Azure Blob Storage or FTPS Servers to execute the import of either CSV or XLSX files. | Application |
| Data Transfer | It enable data transfers from a staging table to the data model, with the option to apply mappings during the transfer. | Application |
| Model Export | These tasks enable exporting data from Anaplan. | Application |
| Planning Export | These tasks are used in specific scenarios to export Anaplan data to a third-party application. | Application |
| Calculation | It executes a stored procedure on the database server. | Application |
| Refresh SSAS Model | It refreshes the published SSAS model. | Application |
| Start | All workflows must begin with a Start task. There can be multiple Start tasks in a workflow. When the workflow is started, all Start tasks will be started and successors will be started. | Control |
| Decision | These tasks change the flow of the tasks depending on a logical decision. The process to be run is based on the results of the expression. | Control |
| Note | These are notes in the workflow to document the workflow. These tasks aren't executed when the workflow starts. | Control |
| Log | It allows the user to log a message to the process log. | Control |
| Delay | It pauses the execution of the workflow for a brief period. | Control |
| Subprocess | Use this task to create a new mini workflow to keep the workflow diagram a manageable size. It creates a new workflow that returns to the calling process when the subprocess is completed. | Control |
| Foreach | It's a special type of subprocess task that can iterate through a set of members. With this task, you can create a workflow process for several business units quickly and easily by defining the workflow once and selecting the members, such as business units, to be burst (or cascaded) through. | Control |
| Lock | It blocks another workflow process from running the same subprocess. For example, if there's a task or stored procedure that needs to be completed before another workflow calls it, that task can be encapsulated into a lock subprocess. The task must be completed before another workflow process can call it. | Control |
| Run Workflow | It triggers another workflow process to run within a workflow process. | Control |
| Abort | It stops the current workflow process immediately. | Control |
