PCS: Starting a process instance remotely
And click on the button in ‘Actions’ column.
If we open aproval form in the workspace we can see that the data sent from soapui has been successfuly sent.
And click on the button in ‘Actions’ column.
If we open aproval form in the workspace we can see that the data sent from soapui has been successfuly sent.
If we try to populate the table we can see tat we need to know the keys of the Map to get the values.
Now that we have created in our bean all that we need, we can start building the table structure.
On the table of the second image we need to make some changes. First, instead of using Map property, we have to use the key array we have just created as value property of the table.
And, as we have to access Map values, we have to add an af:iterator inside the table and add the columns we need inside this iterator. The value property of this iterator is the Map property in the bean.
This way, to retrieve keys we are going to use #{row} and to retrieve values asociated to a key we are going to use #{var[row]}.
Andrejus posted a couple of months ago how to switch between alta and skyros in ADF 12c. This is a cool way to start the migration from 11g to 12c and Alta UI. I am going to show you another way to use one skin or other based on the page you are.
Firstly we have to create a bean and a property inside it where we are going to store the current skin. We have to set this bean as sessionBean.
After that we have to set a bean property in skin-family in our trinidad-config so we can set the skin dynamicaly.
The next step is to create a filter. In doFilter we are going to evaluate the URL and set the skin based on that value. We also have to instantiate the bean and add it to sessionScope becasuse the first time it will be null.
Once we have the filter created we have to add it to web.xml
Now that we have all setup, having multiple pages, if we test it we can see that the the page “alta” will display AltaUI skin and “skyros” page wil dispklay Skyros skin,
In one of the other posts about MCS i showed how easy we can create an API that makes a call to an external REST web service. MCS Connectors also allows to connect to a SOAP web service. Although there is a couple of different things I am going to start the process from the beginning.
package.json is the file where we can set the dependencies of our API, in this case we have to add our connector’s URI.
The last step is to create a custom Selection Listener in our bean and associate it to the af:tree
component.
In this method, a part from ejecute makeCurrent method of the treeModel, we are going to get selected keys and execute setCurrentRowWithKey method with the selected key as parameter.
When we select the first node only one key is in the list, but if we select the second or third level we will have one key per level and we will have to use keyList.get(keyList.size() – 1) in order to get the last selected key.