Skip to main content

Programmatically triggering navigation in ADF Mobile

In your ADF mobile application, sometimes you may want to programmatically trigger navigation from some listener code that you may have in your manged bean. You can use the following piece of code for such use cases.

//Some action listener for a button
public void goToNextViewProgrammatically(ActionEvent actionEvent){
//The client side business logic go here...

//Now you can trigger navigation 
 new Object[] { "gotoView2" }); 
//In the above case 'gotoView'2 is the from-outcome 
//defined in the underlying
//task flow which causes navigation to next view



Popular posts from this blog

Happy New Year 2018 !

We can't go back and change the beginning, but we always can start where we are and change the ending. Believe in yourself and you will be unstoppable!

Wishing you and your family a very happy new year 2018 !!!

How to set Bind Variable Values at runtime ?

In this post I'm sharing a couple of approaches for programmatically setting bind variables values at run time. This post is an attempt to explain 'When to use what ?'[ In case if you are familiar with 'Bind Variables' in ADF BC, please refer Section 5.10, Working with Bind Variables in Fusion Developer's Guide ]

1. Set the Bind Variable value using RowSet::setNamedWhereClauseParam(...)

You can use use the setNamedWhereClauseParam(...) method on the ViewObject interface (which extends oracle.jbo.RowSet) to set the value for bind variables. Please note this sets the value on default RowSet. In other words, this doesn't have any effect on the secondary RowSets that you/system generates.
ViewObject vo = am.findViewObject("EmployeesView1"); vo.setNamedWhereClauseParam("bindVarDeptId", new Number(10)); vo.executeQuery();
2. Set the Bind Variable value using ViewObject's VariableValueManager::setVariableValue(...)

VariableValueManager Ma…