|
22 | 22 | "description": "Pacific/Honolulu", |
23 | 23 | "id": 316 |
24 | 24 | }, |
25 | | - "project_calendar": 1, |
26 | 25 | "disable_parallel_booking": false, |
27 | 26 | "is_archive": false, |
28 | 27 | "created_on": "2018-08-20T09:25:34.925474Z", |
@@ -61,7 +60,7 @@ Name | Description |
61 | 60 | **image** <br>`string` | String value representing URL of image file of project. |
62 | 61 | **tags** <br>`array of strings` | Tags are the list of strings (labels) attached to this project object which could be used for the purpose of filtering, identification or other information. |
63 | 62 | **timezone** <br>`integer` | Defines and categorize projects based on their location. This field is only available when scheduling plus module is on. |
64 | | -**project_calender** <br>`integer` | ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.This field is only available when scheduling plus module is on. |
| 63 | +**project_calendar** <br>`integer` | ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.This field is only available when scheduling plus module is on. |
65 | 64 | **is_archive** <br>`boolean` | Boolean value representing whether this project is archived or not. |
66 | 65 | **created_on** <br>`string` | Timestamp at which this project object was created. |
67 | 66 | **created_by** <br> `object` | Object representing user who created this project object. |
@@ -102,7 +101,7 @@ Name | Description |
102 | 101 | **end_date**<br><span class="mandatoryFlag">⚑</span> <span class="removableFlag mln-2">⚑</span> | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. |
103 | 102 | **tags**<br><span class="removableFlag mln-2">⚑</span> | An optional array of strings which could be attached to this project object as labels. This can be useful for the purpose of filtering, identification or other information. |
104 | 103 | **timezone** <br><span class="mandatoryFlag">⚑</span> <span class="removableFlag mln-2">⚑</span> | One timezone object can be defined for a project.<br><br>_**Note**: <span class="warning">This field is only available when scheduling plus module is on</span>._ |
105 | | -**project_calender** <br>| ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.<br><br>_**Note**: <span class="warning">This field is only available when scheduling plus module is on</span>._ |
| 104 | +**project_calendar** <br>| ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.<br><br>_**Note**: <span class="warning">This field is only available when scheduling plus module is on</span>._ |
106 | 105 | **disable_parallel_booking** <br>`optional` | Boolean value defining if project can or cannot have multiple bookings at a time. Default value for disable parallel booking is false. |
107 | 106 | **udf_\*** <br><span class="mandatoryFlag">⚑</span> <span class="removableFlag mln-2">⚑</span> | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Projects. Different types of projects may have a different set of user-defined fields. The value for user defined field can be passed as shown in example request. In given example `udf_confirmed`</span> is a user defined field. <a href="#user-defined-fields" class="api-ref">Learn more</a><br><br>_**Note**: User with Administrator rights can make fields marked with <span class="mandatoryFlag iconInline">⚑</span> mandatory and remove fields marked with <span class="removableFlag iconInline">⚑</span>, from <a href ="#get-a-specific-project-type" class="api-ref">specific project type</a> using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while creating project, the operation will fail with response code **400**_. |
108 | 107 |
|
@@ -166,7 +165,6 @@ curl -v \ |
166 | 165 | "description": "Pacific/Honolulu", |
167 | 166 | "id": 316 |
168 | 167 | }, |
169 | | - "project_calendar": 1, |
170 | 168 | "disable_parallel_booking": false, |
171 | 169 | "is_archive": false, |
172 | 170 | "created_on": "2018-08-20T09:25:34.925474Z", |
@@ -246,8 +244,8 @@ curl -v "https://app.eresourcescheduler.cloud/rest/v1/projects/1" \ |
246 | 244 | "id": 316 |
247 | 245 | }, |
248 | 246 | "project_calendar": { |
249 | | - "name": "blank", |
250 | | - "id": 2 |
| 247 | + "name": "Default", |
| 248 | + "id": 1 |
251 | 249 | }, |
252 | 250 | "disable_parallel_booking": false, |
253 | 251 | "is_archive": false, |
@@ -425,7 +423,7 @@ curl -v -X PUT \ |
425 | 423 | **email**<br><span class="mandatoryFlag">⚑</span> <span class="removableFlag mln-2">⚑</span> | String value representing email address associated with project object. Email address must be properly formatted with a maximum length of 254 characters. |
426 | 424 | **tags**<br><span class="removableFlag mln-2">⚑</span> | An optional array of strings which could be attached to this project object as labels. This can be useful for the purpose of filtering, identification or other information. It can be up to 50 characters. |
427 | 425 | **timezone** <br><span class="mandatoryFlag">⚑</span> <span class="removableFlag mln-2">⚑</span> | One timezone object can be defined for a project.<br><br>_**Note**: <span class="warning">This field is only available when scheduling plus module is on</span>._ |
428 | | -**project_calender** <br>| ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.<br><br>_**Note**: <span class="warning">This field is only available when scheduling plus module is on</span>._ |
| 426 | +**project_calendar** <br>| ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.<br><br>_**Note**: <span class="warning">This field is only available when scheduling plus module is on</span>._ |
429 | 427 | **disable_parallel_booking** <br>`optional` | Boolean value defining if project can or cannot have multiple bookings at a time. Default value for disable parallel booking is false. |
430 | 428 | **udf_\*** <br><span class="mandatoryFlag">⚑</span> <span class="removableFlag mln-2">⚑</span> | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Project. Different types of projects may have a different set of user-defined fields. The value for user defined field can be passed as shown in example request. In first example `udf_progress` is a user defined field. <a href ="#user-defined-fields" class="api-ref">Learn more</a><br><br>_**Note**: User with Administrator rights can make fields marked with <span class="mandatoryFlag iconInline">⚑</span> mandatory and remove fields marked with <span class="removableFlag iconInline">⚑</span>, from <a href ="#get-a-specific-project-type" class="api-ref">specific project type</a> using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while updating project, the operation will fail with response code **400**_. |
431 | 429 |
|
|
0 commit comments