In this release, we are pleased to announce a significant upgrade to our infrastructure to improve performance and resolveout of memory exception issues.
We are also excited to follow up on our React SDK release with a Vue.js SDK to provide another option for building and launching Single Page Applications with Crownpeak DXM.
Customers with large assets andfrequent publishing activitysometimes encountered out of memory errors.This was one of the top reported issues impacting the performance of DXM.Our infrastructure upgrade coversseveral different areas including Publishing, Job, Image, and FTP services to increase performance, add robustness, and eliminate out of memory exceptions.
DXM Software Development Kit (SDK) for Vue.js
Runtime libraries to handle communication with either Dynamic (DXM Dynamic Content API) or Static (On-disk JSON payload) Data Sources
As a development team runs their build process, the underlying Vue.js Application will be minified and likely packed into a set of browser-compatible libraries (e.g., ES5). We expect any DXM NPM Packages also to be compressed in this manner. To facilitate communication between the Vue.js Application and content managed within DXM, a runtime NPM Package is provided. The purpose of this package is:
To read application configuration detail from a global environment file (e.g., Dynamic Content API endpoint and credentials, static content disk location, etc.);
Making data models available to the Vue.js Application, which a developer can map against
Dynamic Data - Asynchronously processing data from the DXM Dynamic Content API, using the Search G2 Raw JSON endpoint; and
Static Data - Loading JSON payload data directly from local storage.
DXM Content-Type Scaffolding
Developers will continue to work with their Continuous Integration / Delivery and source control tooling to create a Vue.js application. However, the purpose of the DXM Content-Type Scaffolding build step is to convert the Vue.js Components in a single direction (Vue.js > DXM) into the necessary configuration to support CMS operations. At present, the DXM Component Library includes the capability to auto-generate Templates (input.aspx, output.aspx, post_input.aspx) based upon a moustache-style syntax (decorating of editable properties). We have not re-designed this process, as it is fully supported within DXM and customer-battle-tested. Therefore, in order to create a Template configuration, the build step:
Converts Vue.js Components into Crownpeak Components by using the existing Component Builder Process via the CMS Access API (DXM's RESTful Content Manipulation API), and then existing "post_save" process;
Creates Templates for each Vue.js Page (One of the DXM Vue.js Component Types) by using the existing Template Builder Process, again via the CMS Access API and existing "post_save" process;
Creates a new Model for the Vue.js Page Content-Type, via the CMS Access API, so that authors can create multiple versions of a structured Page or Component, without needing to run an entire development/test cycle.
Use the following link to learn more and to take advantage of the new SDK: DXM VueJS SDK
Resolvedthe issue where the Upload.aspxwas not running in V3(OCD- 18808)
Updated thePublishing library to support RebexSFTP (OCD- 18997)