Note
Due to a technical error, this post is being announced after the changes were issued.
Overview
We have added a Context property to Alloy items and it will now be visible as part of all calls that get or list items.
Users will not be able to edit or delete system items, those with Core and Module context property.
This is to avoid any issues where items that Alloy expects to be present, are unexpectedly removed.
Who will this Affect?
This change will affect users who access items via the API or manage integrations.
Details
Example of GET /api/item/{id} for working days Core item
{
"item": {
"itemId": "5c800cc32d14711a9cc642f4",
"designCode": "designs_workingDays",
"collection": "Live",
...
"context": "Core",
"attributes": [...]
}
}There has been no change in terms of item creation and users cannot pass an item context on items create or edit. All user-created items will automatically have context set to Customer.
For example, creating holidays item via POST /api/item
{
"designCode": "designs_holidays",
"collection": "Live",
"attributes": [
{
"attributeCode": "attributes_holidaysName",
"value": "May holiday"
},
{
"attributeCode": "attributes_holidaysStartDate",
"value": "2021-05-03"
}
],
"locked": false
}Will return response that includes "context": "Customer"
{
"item": {
"itemId": "607d5420959e583ad874fc58",
"designCode": "designs_holidays",
"collection": "Live",
...
"locked": false,
"context": "Customer",
"attributes": [...],
"signature": "607d5421959e583ad874fc5d"
}
}System items delete and edit is forbidden
When trying to delete or edit system items, the API will now respond with a 403Forbidden response, e.g. for working days standard item 5c800cc32d14711a9cc642f4 as above swagger responses are as follows.
