Overriding an out-of-the-box Task JSP
Once a custom task page is created, the "Create Task Form Template" page is used to upload the custom page, and register it with the given change item, task type, and container.
Customer authors a JSP template and uses the following UI to upload it to Windchill for a given combination of task type and PBO Class.
Clicking Create Template opens up the following page using which the JSP file can be uploaded
Once the new template is uploaded, a new JSP file gets created in the codebase/netmarkets/jsp/customtemplates folder. The name of the new JSP is generated based off a mapping mechanism, using the Container, PBO class, Activity Type, and JSP template name. (See Project 14216460 Workflow Task Forms).
The JSP name is generated using the mapping mechanism as follows:
<ContainerName>_<PBOType>_<ActivityType>_<Template Name>.jsp
|
|
It is assumed that at least the out-of-the-box templates are present in the system. If no template is found due to deletion of templates, then an exception is raised.
|
