Accessing the Workflow Template Administration Utility
You can access the Workflow Template Administration utility on the Utilities page from the Site , Organizations , Products , and Libraries contexts. Site, organization, and application context administrators manage workflow templates, as described below:
When accessed from the Site level, the site administrator has unrestricted access to all workflow templates in the site context.
Site administrators create, modify, delete, and view workflow templates in the site context.
When accessed from the Organizations level, access to the workflow templates in the site context and the templates that are within the active organization context is available to site and organization administrators.
Organization administrators create, modify, delete, and view workflow templates in the given organization context. Organization administrators can view workflow templates from the site context.
The Products and Libraries level utilities provide access to the workflow templates that are in the active context, plus access to the templates that are inherited from the organization and site contexts.
Product and library administrators create, modify, delete, and view workflow templates in their respective context. They can view organization templates from the parent organization context and the site context.
* 
The Workflow Template Administration utility is not available in the Projects or Programs contexts to administrators of these contexts. For more information about the specific workflow process support in Windchill ProjectLink, see Workflow Process Support in Windchill ProjectLink.
The Workflow Template Administration utility displays a table that lists all workflow templates belonging to the given context, plus those belonging to its parent contexts. The Context column in the table identifies the context owning each workflow template.
When you create a workflow process in Windchill PDMLink, the system saves the new workflow process in the System cabinet of the context in which it is created. The system, not the user, decides where the new workflow template is to be located.
Workflow templates may be moved if certain conditions are met:
The workflow template must be checked in.
There must be a higher level context in the hierarchy than the one in which the workflow template currently resides.
The name of the workflow template must be unique in the target context.
For more information on moving workflow templates, see Moving a Workflow Template.
Est-ce que cela a été utile ?