XperienCentral R28Release date: May 13, 2020
Note |
---|
Upgrading to XperienCentral R28 Minimum Version RequiredUpgrading to XperienCentral R28 R29 requires a minimum version of R26. If you are upgrading from XperienCentral R25 or lower, you must first upgrade to R26 and then upgrade to XperienCentral R28. |
The Performance Dashboard has been removed from XperienCentral in R28. Use the Monitoring Dashboard to view statistics and metrics related to your XperienCentral deployment. See also Administrative Pages. Code ChangesThe nestedPath attribute has been removed from fragmentValue.tag in the wmpformelement plugin. It has been replaced by the attribute formFragment . The value of this attribute contains an object with a nestedPath property. Wherever you use the <forms:fragmentValue> tag, you have to replace the nestedPath property. For example: {{ <forms:fragmentValue nestedPath="${formFragment.nestedPath}" />}}
must be changed to: <forms:fragmentValue formFragment="${formFragment}" />
JCR IndexBeginning in R28, XperienCentral uses an XperienCentral-optimized indexing solution to support queries on frontend nodes instead of the Apache Jackrabbit JCR. This solution generally improves performance and drastically reduces the amount of time it takes to bring a new frontend node online in cloud deployments when traffic demands increase. The new indexing solution will always be used in XperienCentral even if the old JCR index is not disabled. The old JCR index should be disabled on production environments if possible. See also the new JCR Index Settings that have been added to the Setup Tool. JCR Query ReplacementIf you use custom JCR queries in your deployment, they should be replaced in order to use the new API. The following shows a typical query replacement: Queries similar to this: Code Block | title
With the JCR index wo:personalization_category)[@wo:items
|
wmSession.getJcrSession().getWorkspace().getQueryManager();
|
queryManager.createQuery(xPathQuery,
|
elementsQuery.execute().getNodes();
|
should be changed to something like this: | After upgrading to R28, the existing username(s) will still be used by the Connector API. As soon as you open either of the panels, however, the user(s) might not be selectable anymore and if you re-save the configuration, the jobs might stop running. This is the intended behavior. The solution is to navigate to the Authorization panel, designate new system users and then designate them as the user accounts that run jobs on the Configuration and Job tabs in Import/Export Configuration.