> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/development/flow-portal-2/portlets/common-configuration/visual-planning-input-data.md).

# Visual planning input data

In visual planning, user actions like drag and drop and double click will start workflows as configured in Interaction. The workflows require some fixed input parameters. 

An input table will be sent to the workflow. The table name will default to InputTable. The workflow start step needs to be configured with the actual variable names for data to be available within the workflow.

Below are lists of which input is required for each action and portlet.

<table><thead><tr><th width="268">Workflow name</th><th>Gantt</th><th>Kanban</th><th>Map</th><th>Scheduler</th></tr></thead><tbody><tr><td>Create Task workflow</td><td> </td><td> </td><td>x</td><td>x</td></tr><tr><td>Double Click Workflow</td><td>x</td><td>x</td><td>x</td><td>x</td></tr><tr><td>Drag and Drop workflow</td><td>x</td><td>x</td><td>x</td><td>x</td></tr><tr><td>Drop from table</td><td>x</td><td> </td><td> </td><td>x</td></tr><tr><td>Resize</td><td> </td><td> </td><td> </td><td>x</td></tr></tbody></table>

{% tabs %}
{% tab title="Gantt" %}

## Gantt

#### Double Click

* OperationType: "DoubleClick"&#x20;
* TaskId

OR

* operation type: "DoubleClick"
* TaskId

#### Drag and Drop

* OperationType: "Drop"&#x20;
* TaskId&#x20;
* StartDate&#x20;
* EndDate

#### Drop from Table

* OperationType: "DropFromTable"&#x20;
* TaskId&#x20;
* StartDate&#x20;
* EndDate
  {% endtab %}

{% tab title="Kanban" %}

## Kanban

#### Double Click

* OperationType: "DoubleClick"&#x20;
* TaskId

or

* operationType: "DoubleClick"&#x20;
* taskId

#### Drag and Drop

* OperationType: "DragAndDrop"&#x20;
* TaskId&#x20;
* SourceStatus&#x20;
* TargetStatus&#x20;
* SourceSwimlane&#x20;
* TargetSwimlane&#x20;
* CurrentItemOrderId&#x20;
* PrevItemOrderId&#x20;
* NextItemOrderId
  {% endtab %}

{% tab title="Map" %}

## Map

**Create Marker**

* OperationType: "CreateNewMarker"&#x20;
* NewLatitude&#x20;
* NewLongitude

**Double Click**

* OperationType: "DoubleClick"&#x20;
* Id&#x20;
* NewLatitude&#x20;
* NewLongitude

**Drag and Drop**

* OperationType: "DragAndDrop"&#x20;
* Id&#x20;
* NewLatitude&#x20;
* NewLongitude
  {% endtab %}

{% tab title="Scheduler" %}

## Scheduler

**Create Task**

* OperationType: "Create"&#x20;
* StartDate&#x20;
* EndDate&#x20;
* TargetResourceId&#x20;
* SourceResourceId

**Double Click**

* OperationType: "DoubleClickTask"&#x20;
* TaskId&#x20;
* SourceResourceId&#x20;
* TargetResourceId&#x20;
* StartDate&#x20;
* EndDate

**Drag and Drop**

* OperationType: "DropTask"&#x20;
* TaskId&#x20;
* SourceResourceId&#x20;
* TargetResourceId&#x20;
* StartDate&#x20;
* EndDate

**Drop from Table**

* OperationType: "DropFromTable"&#x20;
* SourceResourceId&#x20;
* TargetResourceId&#x20;
* StartDate&#x20;
* EndDate

**Resize**

* OperationType: "ResizeTask"&#x20;
* TaskId&#x20;
* SourceResourceId&#x20;
* TargetResourceId&#x20;
* StartDate&#x20;
* EndDate
  {% endtab %}
  {% endtabs %}


---

# 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://help.novacuraflow.com/development/flow-portal-2/portlets/common-configuration/visual-planning-input-data.md?ask=<question>&goal=<user_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.