> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/scheduled-task.md). # Scheduled Task ## Description The *scheduledtask* part represents a single step/task within a workflow. **Used With:** This part is used in the Workflow framework. ## Use The *scheduledtask* part is a single step/task within a workflow, and the logicnet that contains it represents the workflow itself. When the system executes the workflow, the framework steps through the logicnet of the workflow and executes the scheduled tasks within it. When the system executes a scheduled task, it presents to the user associated forms for user input or performs specific processing if the task is a system task. Depending on the outcome of the task, the system steps the workflow forward. ## Parameters | Field Name | Description | Type/Options | Optional/Mandatory | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------------ | | Task label | This is the label of the task node in the model. | Text | Optional | | Task Type | This tells the system if the task type is a user or system task. | User \| System | Mandatory | | Object-id | This is the ID of the data-object associated with the workflow of which the task is a part. The data-object is the persistent data container. | Text | Mandatory | | Object-type | This is the value the system presents to the user and writes to the context when no previous value exists. | Text | Optional | | Options | These are the possible outputs of the task. The workflow is stepped dependent on the selected output of the task. In case the task is a UI task, the options will be presented as buttons that the user can click to navigate to the next task. | | | | Value | This is the value of the selected option. | Text | Mandatory | | Caption | If the task is a UI task, the system shows the this on the navigation buttons. | Text | Mandatory | | Applies to | This has been deprecated. | | Optional | | Other | This has been deprecated. | | Optional | | Next status | This is the next status of the task. | pending \| in progress \| completed \| cancelled | Mandatory | | Next action | This has been deprecated. | Text | Optional | | Save | This indicates whether the system must save the data as updated in the dataobject\_data. | yes \| no | Mandatory | | Validation | This indicates whether validation of the input form needs to be performed. It only applies to UI tasks. | yes \| no | Mandatory | | Condition | This has been deprecated. | | | | Next object status | This has been deprecated. | | | | Next object substatus | This has been deprecated. | | | | Display | This tells the system whether the option should be displayed. | yes \| no | Mandatory | | Actions | These are optional action buttons that you can define. In contrast to the options buttons, which are used to step the workflow, action buttons trigger an action while the task is still open. Each action button can be associated with a logicnet the system will call when the user clicks the button. | | | | Caption | This is the button caption. | Text | Optional | | Applies to | This has been deprecated. | | Optional | | Call Logicnet | This is the name of the logicnet that is associated with the button. | Text | Mandatory | | Display | This indicates whether the logicnet has UI elements to show or not. If you select *yes* the system launches the logicnet in a popup. | yes \| no | Mandatory | | Parameters | These are the input parameters to pass to the launched logicnet. | Text | Optional | | Task Logicnet | This is the logicnet that is associated with the task. The system calls this logicnet when the task is being executed. | Text | Mandatory | | Load Logicnet | This is the logicnet the system will call to load the data for the task. | Text | | | Save Logicnet | This is the logicnet the system calls to save the data of the task to persistent storage. | Text | | | Pre-processor Logicnet | This is a logicnet the system can call before executing the main task net. | Text | Optional | | Post-process logicnet | This is a logicnet the system can call after the main task net has been executed. | Text | Optional | | Parameters | These are the input parameters of the task. | Text | Optional | | Subject | This is the subject of the task. | Text | Optional | | Planned start-stamp | This is the time the system should start the task. | Timestamp | Optional | | Display | This specifies whether the task has UI elements to show or not. | yes \| no | Mandatory | | Result | This has been deprecated. | | | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/scheduled-task.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.