Rich Client Customization Types   The rich client uses several methods to control how it presents information. Stylesheet Stylesheets controls the layout of the user interface based on the object being viewed and the user session. Stylesheets are customized using configuration instead of coding. Stylesheet are defined in XMLRenderingStylesheet datasets. Stylesheets does not require deploy, it is stored on the server. New Stylesheets can be registered. Each commonly used business objects in Teamcenter (such as item revisions, forms, datasets and so on) has a stylesheet that defines the layout of its properties in the user interface. Stylesheets are used in: Summary view Property dialog box Create dialog box Save As dialog box Revise dialog box Form display How Stylesheet Works The Object type being viewed and the viewer being used determines name of the preference that has to be used. For example, if ItemRevision object is being viewed in Summary viewer. then the preference used is ...

  Teamcenter preferences are settings stored in the Teamcenter database that provide a mechanism to control and define Teamcenter behavior by letting you modify the interface, set default behavior, and specify default values. Use Teamcenter preferences to configure many aspects of a session of application behavior, such as how assemblies are revised, whether extension rules are bypassed for specified operations, and which Teamcenter objects are displayed in integrations. Each application may have associated preferences. They are similar to environment variables, except that they operate with several layers of permissions

Organization application enables you to create and maintain your company’s organization within Teamcenter by organizing user accounts and their respective permissions and user groups. User accounts help to: Track changes to objects. Control access and privileges. Manage default object ownership. Organization is made of groups. Group contains subgroups, roles, users and person.  Organization is an administrative application and used for the following, Viewing information of the organization. Defining Groups, Roles, Users, Person, Volume, Sites, etc. Establish administrative privileges. Defining optional Calendars, Disciplines and Part Libraries. Organization is read-only to non-dba group users unless they have been granted authorization to make modifications by a user with system administration privileges. Organization Tree: Group is for grouping of users who share data. Subgroup is a group with another group designated as its parent. Role represents specific skills and/or responsib...

Workflows is the automation of business processes in which documents, information and tasks are passed between the authorized users of the organization in a way that is controlled by rules and conditions. It comes from the old school concept, that all work goes through one or more process/approvals to accomplish an objective. It replaces the paper approvals through digitally capturing the all the information happened on the workflow lifecycle. Who has initiated, Who has approved or completed the task, When the task is completed, What are the comments, etc. Workflows are designed by system administrator using Workflow Designer application of Teamcenter. Workflows are designed based on the company's business process with defined practices and procedures. End users use the templates to initiate workflow processes in My Teamcenter application on the objects. Workflow Elements Workflow Template: Templates are blueprints of workflow processes. Administrators creates the workflow proces...

Query Builder application in Teamcenter allows you to create customized searches for objects  in both local and remote Teamcenter databases. Basics of Query Builder Teamcenter Query is based on Teamcenter persistence data model. Refer  Teamcenter Data Model Layer   section to understand Teamcenter data model Query is created against any of the Teamcenter persistence class. Query criteria can be defined either on attribute of target object or for the related object which are related to search class through either GRM relation or reference. Referenced-by clauses allows creating query based on reversed-reference relationship. For example, query to find dataset objects that are referenced, through an IMAN_specification relationship, by an item revision with a specific name. Query hints assist user to navigate the schema by presenting a relationship to traverse and the steps required to build the relationships into query definition. For example, item to item-master f...