Creating the Contexts from which Users Work
All Windchill solutions provide the capabilities for creating organization and application contexts.
There is only one site context, which is created when your Windchill solution is installed. No additional site contexts can be created.
* 
The base data installation can create an organization context. If one was not created by loading the base data, the site administrator creates the organization context from Organizations .
Application context managers can create application contexts. You become an application context manager for products, libraries, projects, or programs by being in the creators group for products, libraries, projects, or programs. The creators groups are maintained from Organizations > Creators. When you create an organization from Windchill ProjectLink, you can choose to automatically add those organization members who log on to the project creators group; you manually add users to the program creators group. In all other Windchill solutions, you manually add users to the product and library creators groups.
As part of the process of creating a context, you select a context template. Context templates provide the administrative items (as described in Context Administrative Items) that you want set in the context, thus establishing the initial context framework for users. For the details on creating context templates, see Context Templates.
For information about creating organization contexts, see Creating an Organization Context.
For information about creating product and library contexts, see Products and Libraries.
For information about creating project and program contexts, see Projects and Programs.
Using Out-of-the-box Context Templates
Your Windchill solution provides a set of out-of-the-box context templates that you can use when creating contexts.
The text in the templates has been translated, and translated files are provided in the loadFiles and loadXMLFiles directories where your Windchill solution is installed. As part of the installation process, the installer can change the load set so that the base data loaded includes files translated into the language of choice at your site. The base data that is loaded determines which language set of context templates is available.
For details on setting which language files are used when loading base data, see Database Initializing and Data Loading.
Use one of the out-of-the-box organization templates when creating organization contexts, or you can create a customized organization template, as described in the next section.
For application contexts, you can use one of the out-of-the-box product, library, project, or program templates, or you can create additional application context templates, as described in the next section.
The details of what is in each out-of-the-box context template can be found in the following chapters:
Organization templates are described in Organizations.
Product and library templates are described in Products and Libraries.
Project and program templates are described in Projects and Programs.
For information on creating context templates, see Context Templates.
* 
The role names used in Windchill solution context templates are included as references to the <Windchill>\src\wt\project\RoleRB.rbinfo resource bundle so that when they are used, they appear in the language specified by the browser language. This means that the translated templates do not contain translated role names.
Was this helpful?