Static JSF Pages

It is possible to use JSF (xhtml) pages outside of a normal User Dialogs. If you want a such static JSF page you can create a new sub folder view inside the webContent directory. The concept is mostly the same as in Html Dialogs described. The special part about this approach is, that those pages run on an application and process model but without a process or task.

Because this pages are outside of a normal User Dialogs structure, it is not possible to access any ivy data or logic classes. If you want logic and data you need to implement ManagedBeans (same way as known from Managed Beans) which will provide this stuff for you.


It is not possible to use Html Dialog Component inside of static JSF pages. Even if you use a static JSF page as workflow end page, it is not possible to access the case and task context.

Access static pages


To access this pages with a browser you need to call http://<servername>:<port>/ivy/faces/view/<application>/<process model>/<xhtml file in webContent/view>. Assumed you have a xhtml page with the name test.xhtml in your webContent/view folder, an <application name> App and a <processmodel> PM, you can call the URL http://localhost:8080/ivy/faces/view/App/PM/test.xhtml to get your static JSF page.


Please note that any page located within the webContent/view folder is accessible via this static URL. So you should only have pages in here, which are fully functional (e.g no template pages) and you should secure them via a login page.


If you want to call this static JSF pages from a ivy process, you can implement a End Page, Task Switch Gateway or Task Switch Event element and choose the xhtml file as end page. For this approach exists an example in the HtmlDialogDemos.