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:
- For inriver users, it is now possible to disable link rules from running, which is very useful when still in the planning or enrichment phase of a new Channel and the current published channels should be affected as little as possible. Another scenario could be that you have found a large number of orphaned Channel Nodes (entities that are not in a Channel), and you want a non-destructive way to prevent the Link Rules from running.
- As an user working in Control Center you will now have the ability to delete all keys in a CVL.
- NOTE: Due to the potential impact on the customer environment, administering this functionality is recommended exclusively for individuals with extensive knowledge of the customer environment's data model.
- As a user working in Control Center, you will now be able to see all enabled extensions that are running.
-
As a user working in Control Center, you will now have a shortcut menu to the different parts of an environment, so that you can easily navigate
- As a user working in Control Center that has access to several environments, a "Switch Environment" dropdown has now been added in the user menu for quicker access to different environments. This feature is hidden for customers with only one environment
- As a user working in Control Center with extension management, a description field in the extension view has been added
-
Improvements have been made to REST API Swagger to show possible response codes for the following endpoints:
- ExtensionController
- ChannelController
- EntityController
- LinkController
- MediaController
- ModelController
- QueryController
- SyndicateController
- SystemController
- WorkAreaController
- WorkflowController
-
Enhancements have been made to the REST API adding endpoints for ConnectorState:
-
Get all ConnectorStates
- GET v1.0.0/extensions/connectorstates
-
Get all ConnectorStates for Connector -
- GET v1.0.0/extensions/connectorstates/{connectorId}
-
Add a ConnectorState
- POST v1.0.0/extensions/connectorstates
-
Update a ConnectorState
- PUT v1.0.0/extensions/connectorstates/{id}
-
Delete all ConnectorStates
- DELETE v1.0.0/extensions/connectorstates
-
Delete a ConnectorState
- DELETE v1.0.0/extensions/connectorstates/{id}
-
Delete all ConnectorStates for Connector
- DELETE v1.0.0/extensions/connectorstates/connector/{connectorId}
-
Get all ConnectorStates
- Enhancements have been made so it is now possible to create entityTypes/CVL in Control Center and in the REST API GET-method remains the same casing as the key's value in Control center.
Please see below for the deployed bug fixes:
- It has now been corrected so that users are not allowed to Add/ Update CVL through REST API when using invalid data types other than String and LocaleString.
- It has now been corrected so that when creating or updating a CVL, this is then returned when retrieving the CVL with a GET request.
- It has now been corrected so that when a user in Control Center is Adding/Updating/Delete CVL keys, the changes will be reflected to the Portal accordingly.
- It has now been corrected so that, as a user in the REST API modifying the User Details, the FirstName and LastName will now be required.
- It has now been corrected so that Extension Statistics can be seen in the Extension tab in the Control Center.
- It has now been corrected so that the setting PORTAL_ENVIRONMENT_COLOR_INDICATOR line will be removed when the setting is deleted and caches are cleared.
- It has now been corrected so that deleting language that don't exist in the REST API will result in a bad request (400).
Please note that in order for the changes in Control center to be in effect, a hard reload of the browser might be needed (Ctrl and press F5).
For weekly deployment plans follow this link:
https://community.inriver.com/hc/en-us/articles/12147582177308-Weekly-deployment-plan
Comments
5 comments
Wow, these are some fantastic QoL changes! 👍
Awesome updates!
But I don´t see the changes in Control Center, do we need to enable/do anything for make the changes visible?
Yes, already emptied cache, tried different browsers, computers and so on.... ;)
Mattias Agerberg Please try a hard reload of the page and it should be visible, sorry for the inconvenience!
Nice work!
Really good and wanted improvements!
Helena Gerebro - Thanks!
Did a hard reload, didn't work the first time or the second, the thrid time it worked like a charm.
So if anyone else has the same issue, do hard reload several times until shown :)
Please sign in to leave a comment.