As clients can now assign who should be charged for individual line items for supplies and cost in our app, we have extended response in API to include those values in the response for task object.
New key bill_to has been introduced with costs and supplies arrays.
In case where values in bill_to are different, tasks bill_to will have the value multiple.
Or in case this value is same across the cost and supplies, the same vallue will be populated for main bill_to in task.
When creating a task, it is now possible to send assign_default_workers parameter.
If the param is sent as true, we prioritize default workers set at the template level. If template level default workers do not exist, we will use the department level. Both are set per property.
Default assignees will be adjacent to assignments that were manually set. So if you send custom assignments, and also send assign_default_workers=true we will honor both.
We have published a new endpoint for subdepartments and their corresponding Ids. The subdepartment_id will be used when creating a task.
[
{'id': 101, 'name': 'Human Resources'},
{'id': 242, 'name': 'Marketing Analytics'},
{'id': 317, 'name': 'Customer Support'},
{'id': 455, 'name': 'Product Development'},
{'id': 528, 'name': 'Financial Planning'}
]Added the following fields as values that can be used to create or update a task:
| Name | Type | Added to |
|---|---|---|
task.subdepartment_id | integer | Create Task, Update Task |
task.rate_paid | float | Create Task , Update Task |
task.rate_type | enum (hourly, piece) | Create Task , Update Task |
task.requested_by | enum | Create Task , Update Task |
Added the following fields to the task response:
Added the following fields to the task response and task list response:
Added the following fields that can be used when retrieving tasks in bulk:
Added API resources to manage property contacts
Added the following details to the Task Webhook payload: