WebCenter Portal Task Flows: Parametros de entrada de tipo Boolean

Customizando los Task Flow de WebCenter Portal puede requerir añadir nuevos parámetros de entrada.

English version

En este caso hablamos de los parámetros de tipo java.lang.Boolean.

¿Qué ocurre cuando añadimos un parámetro de tipo Boolean?

Parámetro adherido de tipo Boolean
Cuando adhieres un parámetro de tipo Boolean se mostrará mediante Oracle Composer como un Checkbox por lo que parece que todo va correcto.

Parámetro Boolean en Content Presenter

Sin embargo, cuando se intenta utilizar el valor de éste parámetro en, por ejemplo, un Router en el Task Flow. Se producirá el siguiente error:

<Jan 10, 2014 11:52:12 AM CET> <Error> <oracle.adf.controller.internal.binding.TaskFlowRegionModelViewPort> <BEA-000000> <
oracle.adf.controller.activity.ActivityLogicException: ADFC-06008: Router case expression '#{pageFlowScope.analytics}' does not evaluate to a boolean.

¿Por qué ocurre este error? 
Si se observa los valores registrados en el MDS se verá que almacena para el parámetro los siguientes valores:

Registro del nuevo parámetro en MDS
  • ${'true'}
  • ${'false'}
Estos valores son interpretados como String.

¿Como solucionarlo?
La solución se basa en la de tener un Managed Bean con una variable de tipo java.lang.Boolean y mapear / enlazar esta propiedad al valor del parámetro de entrada del Task Flow.

Clase Java para mapear el valor del parámetro de entrada


Parámetro de entrada mapeado a propiedad de Manage Bean
 Al realizar esto la conversión será a Boolean y no habrá problemas para usar el parámetro dentro de Routers.

Comments

  1. Edwind B20 January 2014 at 21:22

    Excelente post! muchas gracias por la información, tu blog como la ayuda en los foros es genial.

    ReplyDelete

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