Sharing is learning, sharing is life. What I learn, discover or face I will publish here
WCC - WCS Connector y el metadato xCollectionsID
Get link
Facebook
Twitter
Pinterest
Email
Other Apps
El conector de WebCenter Sites - WebCenter Content permite sincronizar y crear Assets en WebCenter Sites para acceder al contenido de WebCenter Content como se indica en la documentación oficial de Oracle.
En el caso de querer mostrar los contenidos asociados a una carpeta lo más natural es configurar las reglas para utilizar el metadato xCollectionID.
xCollectionID de una carpeta en WCC
Configurando el conector usando xCollectionID
Sin embargo, el conector no realiza la comparación correctamente dado que trata el xCollectionID como un int en lugar de un String. Esto dará lugar a que cuando se ejecute el conector diga No rule matched para cada contenido encontrado por la regla.
No rule matched porque compara xCollectionID mal
Workarounds:
Usar un metadato custom que se propage a todos los contenidos dentro de esa carpeta haciendo uso de Force Propagation de las carpetas. Folder Metadata Propagation
Cambiar manualmente el archivo <Sites_Shared_Dir>/clustersync/ucm/ini/wcc-matchers.ini que se crea cuando se utiliza la UI del Conector cambiando la regla manualmente para que compare con String en vez de Int.
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
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
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')
Buen post Dani, el primero de 2015! Keep it coming ;)
ReplyDelete