Set project properties
rillsoft_project_updateIdempotent
Updates main project properties like name, dates, calendar, color, category, status, customer, priority, and scheduling settings. Adjusts project period and input options, not display timescale.
Instructions
Sets properties of the main project: key data (name, start, finish, fixing), calendar and color, the master-data references category, status, customer, priority and plan variant, plus scheduling mode, input step widths and the two metric switches. This changes the period of the project, not the time scale of the display (use rillsoft_timescale_apply for that). Subprojects go through rillsoft_subproject_update. One undo step.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | name of the project | |
| color | No | bar color as #RRGGBB or 'automatic' | |
| fixed | No | fix the project start | |
| start | No | project start, formatted DD.MM.YYYY hh:mm | |
| finish | No | project finish, formatted DD.MM.YYYY hh:mm | |
| priority | No | priority of the project in percent (0 to 100), as in the dialog. In a portfolio refused: the tool addresses the portfolio, the field belongs to each project | |
| statusId | No | id of the project status from rillsoft_resource_pool_catalog_list (types: project_status); 0 = none. In a portfolio refused: the tool addresses the portfolio, the field belongs to each project | |
| calendarId | No | id of the calendar from rillsoft_resource_pool_catalog_list (types: calendar); the main project always carries a concrete id | |
| categoryId | No | id of the project category from rillsoft_resource_pool_catalog_list (types: project_category); 0 = none. In a portfolio refused: the tool addresses the portfolio, the field belongs to each project | |
| customerId | No | id of the customer from rillsoft_resource_pool_catalog_list (types: project_customer); 0 = none. In a portfolio refused: the tool addresses the portfolio, the field belongs to each project | |
| primaryColor | No | pass the color on to child elements that carry none of their own | |
| effortEditable | No | effort may be entered on the task | |
| schedulingMode | No | capacity_driven computes with the calendars and absences of the assigned resources, deadline_driven computes without them. In a portfolio refused: the tool addresses the portfolio, the mode belongs to each project | |
| validationMode | No | what to do where existing elements would fall outside the new period: strict (the default) refuses and names the culprits, extend widens the period to cover what exists, force applies it anyway; effective only together with start or finish | strict |
| planningVariant | No | number of the plan variant (baseline) of the project; 0 = dynamic. Refused in a portfolio: there is no baseline there, not even per project | |
| timeStepMinutes | No | input time grid in minutes: 1, 5, 10, 15, 30 or 60, at most the grid of the calendar | |
| durationStepUnit | No | unit used to enter a duration | |
| quantityStepUnit | No | unit used to enter a quantity | |
| dynamicRedistribution | No | redistribute effort dynamically; permitted only with schedulingMode capacity_driven. In a portfolio refused: the tool addresses the portfolio, the switch belongs to each project | |
| outputQuantityEditable | No | output quantity may be entered on the task |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wbs | Yes | WBS code | |
| name | Yes | name | |
| uuid | Yes | UUID of the element | |
| start | Yes | start, DD.MM.YYYY hh:mm | |
| finish | Yes | finish, DD.MM.YYYY hh:mm | |
| number | Yes | number of the element; unique even for split tasks |