Static JSF Pages
It is possible to use JSF (XHTML) pages outside of a normal User Dialogs.
If you want such a static JSF page, you can create a new subfolder view
inside the webContent
directory. The concept is mostly the same as
described in HTML Dialogs. Those pages run on an application and process
model but without a case or task.
Because these pages are outside of a normal User Dialogs structure, it is not possible to access any Axon Ivy data or logic classes. If you want logic and data you need to implement ManagedBeans (see Managed Beans) which will provide this for you.
Warning
It is not possible to use HTML Dialog Component inside of static JSF pages. Even if you use a static JSF page as the workflow end page, it is not possible to access the case and task context.
Access Static Pages
URL
To access these pages with a browser you need to call
http://<servername>:<port>/<application>/faces/view/<process model>/<xhtml
file in webContent/view>
. Assuming that 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/App/faces/view/PM/test.xhtml
to get your static
JSF page.
Note
Please note that any page located within the folder webContent/view
is accessible via this static URL. So you should only have pages in this location
which are fully functional (i.e., no template pages), and you should secure them
via a login page.
EndPage
If you want to call a static JSF page from an Axon Ivy process, you can implement a End Page, Task Switch Gateway or Task Switch Event element and choose the XHTML file as its end page. See the related example in the HTMLDialogDemos.