There are times when you'll need to replace a stock .jsp page in Enterprise Workflow with one that provides custom functionality for your deployment. I'm assuming you've created this replacement .jsp page, and moved it to the CustomClients folder in your Tomcat install.
You will also need to make a copy of the JspMappingRules.xml file from the WorkflowWebserviceClients folder to the CustomClients folder.
Assuming the modified page is the workbasket TOC page, you would modify the following section:

<workbasketTOC-rules>
	<rule expression='true'>WorkbasketTOC.jsp</rule>
</workbasketTOC-rules>

This can be modified to either fully replace the page for all users (in which case WorkbasketTOC.jsp could simply be replaced with /CustomClients/YourNewJSPPage.jsp), or you can add rules for when your custom page will be displayed, as opposed to the default page.

<workbasketTOC-rules>
	<rule expression='workbasketName.matches("AP")'>/CustomClients
	/YourNewJSPPage.jsp</rule>
	<rule expression='Arrays.asList(new String[] {"Bob","Susan"})contains(user)'>
	/CustomClients/YourNewJSPPage.jsp</rule>
	<rule expression='true'>WorkbasketTOC.jsp</rule>
</workbasketTOC-rules>

In the example above, the new custom .jsp page will appear in two situations; when any user views the AP workbasket, or when the users Bob and Susan view any workbasket. In all other cases, the default .jsp is used.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: December 10, 2016