Cyclos 4.11 REST deprecation notes.

This page reports the deprecated elements in Cyclos REST web services.
As policy, breaking changes are marked as deprecated for at least 2 major Cyclos versions, then removed.

Model properties

To remove on	Model	Property	Notes
4.12	AdView	addresses	Use `userAddresses` instead
4.12	TicketsPermissions	accept	Use `approve` instead
4.12	UsersPermissions	contacts	Use `ContactsPermissions.enable` instead
4.13	BaseCustomFieldValue	linkedEntityValue	Use one of the specific fields: - `userValue`: If the entity type is `user` - `recordValue`: If the entity type is `record` - `transactionValue`: If the entity type is `transaction` - `transferValue`: If the entity type is `transfer` - `adValue`: If the entity type is `advertisement`
4.13	CustomFieldDetailed	allowedMimeTypes	Use `mimeTypes` instead
4.13	CustomFieldDetailed	otherMimeTypes	Use `mimeTypes` instead
4.13	Notification	location	Use `entityType` instead.
4.13	Operation	canRunDirectly	Use the other flags instead. This flag was decomposed in several others to allow better control at the moment of run a custom operation. For example, if your front-end asks for the confirmation password in a popup instead of in its own page and the only thing you need to run the operation is that (i.e there are no missing parameters, no file upload, etc) then you could show the popup to collect the password and then run the custom operation directly in the same page on which you are.
4.13	PaymentRequestPermissions	authorize	true
4.13	TransactionDataForSearch	canViewScheduled	Use `visibleKinds` instead.
4.13	TransactionTypeData	requiresDescription	Use `descriptionAvailability` instead
4.13	VoucherView	canCancel	This is redundant with `cancelAction`, is `false` if `cancelAction` is `null`, and `true` if `cancelAction` is not `null`.

Service operations

To remove on	URL	Method	Notes
4.12	/tickets/{ticket}/accept	POST	Use `POST /tickets/{ticket}/approve` instead
4.12	/{user}/contacts/{contact}	DELETE	Use `DELETE /contact-list/{id}` instead
4.12	/{user}/contacts/{contact}	POST	Use `POST /{user}/contact-list` instead
4.13	/contactInfos/{id}/image	POST	Use `POST /contact-infos/{id}/image`
4.13	/images/{id}/content	GET	Use `GET /images/{idOrKey}/content` instead. Generally clients should use the `Image.url` property, which is always correct.
4.13	/images/{kind}/{file}	GET	Use `GET /images/{idOrKey}/content` instead. Generally clients should use the `Image.url` property, which is always correct.