sections in the article
inriver is moving towards more incremental, smaller releases to be able to accommodate our customers in a better and faster way. With smaller, more frequent releases, inriver will be able to increase the quality and transparency of the releases and be able to identify and mitigate any erroneous behavior that may be caused by the release much faster. Please note that larger features and/or changes that are deemed to have a strong impact on customers and partners will of course be communicated in advance.
Please see below for the deployed features and improvements:
- The mandatory permission ManageModel has been added to POST/PUT/DELETE endpoints for /model endpoints.
-
The following endpoints have now been added to the model REST API:
- GET v1.0.0/model/linktype
- GET v1.0.0/model/linktype/{likeTypeId}
- PUT v1.0.0/model/linktype
- POST v1.0.0/model/linktype
- DELETE v1.0.0/model/linktype
- DELETE v1.0.0/model/linktype/{likeTypeId}
- As a user in the REST API, working with Query Work Area, it will now be possible to see the specific Query Work Area via endpoint '/api/v1.0.0/workareafolderquery/{id}'. This will make it easier to get the details from the specific Work Area ID.
-
Remoting nuget 8.8.1 has been made available at https://www.nuget.org/packages/inRiver.Remoting.iPMC:
- Internal data processing improvements
-
The following methods have been deprecated in the Remoting API:
- ImportEntityFile
- GetImportFileResult
- GetImportFileBatches
- GetBatchStatuses
Please see below for the deployed bug fixes:
- We have applied a solution to ensure that when working with Channel Nodes, via the REST API, that connects to two or more parent nodes, it will now be possible to GET ChannelNodeTree and see the node tree without error and with the correct node ID.
Comments
0 comments
Please sign in to leave a comment.