Content Presenter: Wizard vs Page Definition

Content Presenter es uno de los Task Flow más populares en WebCenter Portal dado que permite la visualización de contentidos en WebCenter Content así como Assets del viejo Site Studio.

Content Presenter para mostrar contenido de Site Studio y Content

Este post explica las diferencias principales entre configurarlo utilizando el Content Presenter Wizard en Runtime y configurarlo en Design/Runtime a través de los parámetros de entrada.

Configuración a través de la Page Definition.

Configuración por parámetros de Content Presenter

Esta configuración está pensada para desarrolladores que usan Content Presenter en sus desarrollos en Design Time o para configurar de una manera más "avanzada" en Runtime cuando se requiere el uso de EL Expressions complicadas.

Configuración a través del Wizard

Content Presenter Wizard

Permite al usuario final configurar de manera sencilla los contenidos a visualizar y qué plantillas utilizar.

Diferencias

Las preferencias establecidas en Page Definition sobrescriben las realizadas en el Wizard.

La configuración de parámetros de Task Flow, obviamente se guarda en la Page Definition. Sin embargo... dónde se guarda las del Wizard?.

La configuración realizada mediante el Wizard se guarda en el MDS (Metadata Service) en la ruta:

oracle\webcenter\doclib\scopedMD\[GUID_Espacio]\[NombrePagina.jspx]\TaskFlowId.xml

Al exportar del MDS se encontrará un fichero XML por cada Content Presenter de la página con la configuración realizada mediante el Wizard.


ACTIVE

dsTypeSingleNode

ucm#dDocName:000225




oracle.webcenter.content.templates.default.detail
false

Referencias:

Comments

Post a Comment

Popular posts from this blog

OJET: Inter-Module communication in TypeScript Template

Image
In this post I bring another example on how to Communicate Modules using the Oracle JET - TypeScript Template based on the Oracle JET Cookbook: InterModule Communication From now and so on will create multiple examples using TypeScript for those who are not familiar with it and wants to turn the Cookbook examples into TypeScript :). The example ( ojet-typescript-list-detail ) can be found as usual in my GitHub repository: https://github.com/DanielMerchan/ojet-examples This example is a bit different compared to the Cookbook example where the modules are not running at the same time within a Module. This example is built as described in the following images: Customers module acts as the Wrapper Module. It coordinates when to load the list and detail modules. Customers module makes use also of signals npm module for communication between Customers-List, Customers-Detail. Explanation of the Example customers.js is the coordinator responsible module for: initiali
Read more

OJET: Build and Deploy in an Application Server

Image
There are some other sources where an Oracle JET Application is packaged and deployed as a WAR in Oracle WebLogic Application Server (Arda Eralp) https://blogs.oracle.com/ardaeralp/deploy-oracle-jet-application-to-weblogic-server (Andrejus Baranovski's) http://andrejusb.blogspot.com/2016/07/serving-oracle-jet-application-from.html They may look bit old or maybe because they call directly grunt tasks by using the grunt-cli . In this post I will update a bit these posts in Oracle JET 6.1.0 and the usage of ojet build (instead of calling the grunt tasks) for also building the corresponding WAR file. The example can be found in my GIT repository: https://github.com/DanielMerchan/ojet-examples Let's start... Install grunt-war module in your Oracle JET Application. npm install grunt-war --save-dev Create a war.js (or call it whatever you want) in /scripts/grunt/config folder under your souce files. This is a sample code inside of it, check https://www.npmjs.com/packag
Read more

OJET: Select All options using only Checkboxset

Image
This is an example on how to select all other options by using another oj-checkboxset. GitHub: ojet-checkbockset-select-all The idea is to keep track of the selection and make use of the on-value-changed as described in the following code. self.colorOptions = ko.observableArray([ { id: "blueopt", value: "blue", color: "Blue" }, { id: "greenopt", value: "green", color: "Green" }, { id: "redopt", value: "red", color: "Red" }, { id: "limeopt", value: "lime", color: "Lime" }, { id: "aquaopt", value: "aqua", color: "Aqua" }, ]); self.selectAll = ko.observableArray([]); self.currentColor = ko.observableArray(["red"]); self.selectAllOptionChanged = (event) => { const newSelection = event.detail.value; if (newSelection.indexOf('all')
Read more