Considerations for importing and exporting form tasks in workflow templates
You can save a project workflow as a template to use in other projects. You can export the template from the project and import it into another project. If the workflow template contains form tasks, the links to the form tasks might or might not be maintained, depending on whether the forms they refer to are present or not in the new project.
The following situations apply to importing a saved project workflow template into a new project instance. Administrators can also import workflow templates into templates for projects if the workflow template does not contain form tasks.
When you save a project workflow as a template with a linked form task and export it, then the link to the form is maintained. However, the form is not exported with the workflow template.
The following situations apply to importing a project workflow template into a new project.
If you import a workflow template and the linked form is present in the new project, then the link to the form works as expected.
If you import a workflow template and the linked form is not present in the new project, then the link is broken.
A warning lists form tasks with broken links. The form task is shown with an icon that indicates a broken link (
).
If you copy or clone the workflow, broken link copies as they are. The links remain broken in any copies.
You can save the workflow with broken links. A user who tries to complete a task with a broken link cannot access the form.
If you encounter a broken link in the workflow, the project owner can open the form task pop-up and select an available form before assigning the form task to a team member.
Copyright IBM Corporation 2014. All Rights Reserved.
).