Yes this can be done.
The links on the 'Application Map' screen control the flow through the application. Each controller represents some server processing, and the links from a controller out to the pages control what the user will see as a result of the processing.
You can have as many outgoing links from a controller to different pages as required. If you click on each link, in the advanced options you can enter an XPath to indicate when that link should be followed. You can edit this information more easily using RuleMaker by selecting 'View Controller Rules' from the source controller.
These XPaths are used as conditions for the 'write_targetPage' rules, and can be edited as required. A common option would be to use the count() function within the XPath to show different screens depending on the number of results returned from a search for example.
It is also possible to create a rule manually to change the target page. This could be useful in the situation where you do not want to add a link to the 'Application Map' diagram as it is not part of the normal process flow. E.g. showing an error page.
To do this you would need to add an 'Assign' action to your manually created rule, and set the to location XPath parameter to '/mvc:eForm/mvc:Control/mvc :P age'. The value parameter needs to contain the name of the XSL that is used to display the required page. This is the name of the page within FormMaker, with the .xsl extension. E.g. start.xsl
The links on the 'Application Map' screen control the flow through the application. Each controller represents some server processing, and the links from a controller out to the pages control what the user will see as a result of the processing.
You can have as many outgoing links from a controller to different pages as required. If you click on each link, in the advanced options you can enter an XPath to indicate when that link should be followed. You can edit this information more easily using RuleMaker by selecting 'View Controller Rules' from the source controller.
These XPaths are used as conditions for the 'write_targetPage' rules, and can be edited as required. A common option would be to use the count() function within the XPath to show different screens depending on the number of results returned from a search for example.
It is also possible to create a rule manually to change the target page. This could be useful in the situation where you do not want to add a link to the 'Application Map' diagram as it is not part of the normal process flow. E.g. showing an error page.
To do this you would need to add an 'Assign' action to your manually created rule, and set the to location XPath parameter to '/mvc:eForm/mvc:Control/mvc :P age'. The value parameter needs to contain the name of the XSL that is used to display the required page. This is the name of the page within FormMaker, with the .xsl extension. E.g. start.xsl