inriver is moving towards more incremental, smaller releases to accommodate our customers better and faster. With smaller, more frequent releases, inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release much faster.
NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.
Please see below for the deployed features and improvements:
General
-
It has been implemented that EntityTypes and FieldTypes used when deserializing the incoming Entity to server extensions are now being cached for 10 minutes. This caching mechanism improves performance but also means that any changes made to the model will not be reflected instantly on the incoming Entity.
Print 2.0
-
It has been implemented that Print 2.0 now includes a Print Force Reload feature. If users encounter integration issues and are uncertain whether all data has been loaded, this feature enables the "Force Data Reload" button on each print, which users can access. Please note that this should be used only as a workaround for customers experiencing issues.
-
It has been implemented that Print 2.0 now includes an Organizer Force Reload feature. If users experience difficulties with the organizer functionality, this feature enables the "Force Data Reload" button on each version, which users can access. Again, this should be used solely as a workaround for customers encountering issues.
Please see below for the deployed bug fixes:
Print 2.0
- We have applied a solution to ensure that when a sub-section is used as selectable, the system now properly regenerates the list of selectables on the Print page whenever a new section is added to a publication.
- We have implemented a solution to ensure that when a sub-section is used as a choice option, the order of the options is now correctly maintained.
-
We have applied a solution to ensure that the performance and stability of nightly batches are improved, with a focus on optimizing data preparation and system cleanup processes.
- We have applied a solution to ensure that when exporting print data in JSON, XLSX, or CSV formats, the downloaded file now correctly includes the selectable name.
-
We have applied a solution to ensure that when the browser window is too small and the left menu transitions into a popup, the logo inside the popup menu is now properly displayed.
- We have applied a solution to ensure that when a column is removed and then added back from a source file in the file import process, the column can once again be selected in the File Import configuration.
inriver Implementation Standards
inriver's ambition is to collaborate with our partners in providing our customers with as safe and secure a PIM system as possible. With that in mind, inriver is improving the information on our Community to help implementation partners ensure quality, optimize implementations, and avoid pitfalls.
Read more about inriver Implementation Standards
Comments
5 comments
Hi!
Regarding the caching of EntityTypes and FieldTypes; it would be nice if this could be disabled/enabled in all environments except Prod, since development of extensions are mainly done against a Dev or Test env.
I can think of a few of our projects that have tests that now will fail.
// Kind regards, Torbjörn
Hi Torbjorn Stavas
thanks for the feedback! I have provided your feedback to the development team, and it will be looked into as a potential feature improvement/request.
Hi,
Sounds good with a cache, is there any way to force empty that cache? For example a Restart Service?
Regards
Peter
Hi Peter Norlander (ICP),
Yes, restarting the service will clear the cache.
Cheers
//Helena
Hi,
Being able to empty the cache via a restart of the service is good enough, no need for a enable/disable the cache then Helena Gerebro
// Kind regards, Torbjörn
Please sign in to leave a comment.