ADF wildcard control flow rule
ADF Wild Card can be used in bounded and unbounded task flow. It is used to control what activity in a task flow Is allowed to access other activity in the same task flow. Use the single wildcard * if you want to allow any activity in the task flow allow to pass through the wild card. Use trailing wildcard index* if you want to restrict the activities in the task flow to pass through the wildcard.
Look at the below image; it is my unbounded task flow. I have used three wildcard activity. Below I have detailed each one:
ADF Wildcard Index* control flow to two view activities A1 and A2, so any activity in the task flow starts with the ‘index’ can access A1 and A2. In this case, indexPage and indexHome are two activities start with index can access A1 and A2
ADF Wildcard view* control flow to two view activities C1 and C2, so any activity in the task flow starts with the ‘view’ can access C1 and Ce. In this case, viewPage and viewHome are two activities starts with view can access C1 and C2
ADF Wildcard * control flow to two view activities B1 and B2, so any activity in the task flow can access B1 and B2. In this case, all view activities (A1, A2, B1, B2, C1, C2,indexPage, indexHome, viewPage, viewHome) an access B1 and B2
I have a command button in the viewPage.jsf. As mentioned above this page can access C1, C2, B1 and B2. (B1 and B2 are accessible by any activity because it uses wildcard *)
The same way, command button in the indexPage.jsf can access A1, A2, B1 and B2
The views expressed on this blog are my personal views and do not necessarily reflect the views of my employer.
Please feeling free to reach me on any comments and feedbacks you have. Would be more than glad to listen and reply 🙂