Teamcenter: Introduction to Stylesheets

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 ItemRevision.SUMMARYRENDERING
Preferences used for stylesheet registration are hierarchical, a group, role, or user preference of the same name would override the site default.
The appropriate preference is retrieved. It contains the name of the XMLRenderingStylesheet dataset that contains the rendering information.
The XMLRenderingStylesheet dataset is retrieved by name. Its contents are parsed and the view layout is generated.
The view is rendered and displayed to the user.

Registering Stylesheet

Select the style sheet, and in the Viewer tab, see the business object listed in the Registered Type box on the style sheet. Select the object for which you are defining the stylesheet.
To specify how the style sheet is to be used, select it in the Stylesheet Type box (for example, for properties display, form rendering, Summary view, or creation dialog boxes).

The preferences that register style sheets have the generic syntax.

objectType.RENDERINGTYPE

objectType – Refers to database name of the object as found in Business Modeler IDE.

RENDERINGTYPE – One of the supported rendering locations.

Two preferences are created after registering

REGISTEREDTO
RENDERING

The preferences are created depending on the type of style sheet that is registered.

Property (View Properties dialog box or Viewer tab)

<dataset_name>.REGISTEREDTO=<type-name>
<type_name>.RENDERING=<dataset_name>

Form (From object dialog box)

<dataset-name>.FORM_REGISTEREDTO=<type-name>
<type-name>.FORMRENDERING=<dataset-name>

Summary (Summary View tab)

<dataset-name>.SUMMARY_REGISTEREDTO=<type-name>
<type-name>.SUMMARYRENDERING=<dataset-name>

Create (creation wizard)

<dataset-name>.CREATE_REGISTEREDTO=<type-name>
<type-name>.CREATERENDERING=<dataset-name>

Save As (Save As Panel)

<dataset-name>.SAVEAS_REGISTEREDTO=<type-name>
<type-name>.SAVEASRENDERING=<dataset-name>

Revise (Revise Panel)

<dataset-name>.REVISE_REGISTEREDTO=<type-name>
<type-name>.REVISERENDERING=<dataset-name>

Creating a custom stylesheet based on an existing stylesheet

In Rich client, search for a style sheet you can base your new style sheet on.
In the Search Results view, select the style sheet you want to use, choose File→Save As, and rename it.
The new style sheet dataset is saved in your Newstuff folder in the Home view
Edit the style sheet in the Viewer tab to include the elements you want displayed in the layout.
In the Viewer tab, click the arrow in the Registered Type box and select the business object type you want to register it to.
To change the style sheet type, click the arrow in the Stylesheet Type box.
When you are done making changes, click the Apply button in the lower right corner of the view.
To see the two new preferences, choose Edit→Options and at the bottom of the dialog box, click Search.

Viewing the <dataset_name>.REGISTEREDTO and <type_name>.RENDERING preferences

Comments

Teamcenter Relations

Teamcenter Relation objects are created to relate two objects. It connects the primary business object and secondary business object through relation property. Relations are widely used in Teamcenter. Out of the Box Teamcenter provides various relation objects to relate objects. Always we can create new relations through BMIDE under ImanRelation business object. ImanRelation B.O Steps to create new relation Open BMIDE and load the custom template. Search for ImanRelation in Business object tab. Right click ImanRelation -> New Business Object. Type in the Name (real name) and Display Name (This name will be shown to end user for pseudo folder name). Relation creation window

Teamcenter custom handler build in BMIDE

In this blog we can see how to register and build a custom handler through BMIDE. Please refer my previous blog Setting up BMIDE for coding and building DLL to set up BMIDE for coding. Register Custom Handler Make sure you have a active library defined in Extensions\Code Generation folders. If you need a new library for managing handlers, create a new library and make it as active library. Create a custom extension rule. Open the Extensions\Rules folders, right-click the Extensions folder, and choose New Extension Definition. In Extension dialog box, along with Name of the extension and click the Add button to the right of Availability table. Select the business object as Session, Business object as Type, Operation as BMF_SESSION_register_epm_handlers and Extension Point as BaseAction. Extension availability Click Finish Extension view Add your custom extension as a base action on the BMF_SESSION_register_epm_handlers operation. Open the Session business o...

Setting up BMIDE for coding and building DLL

Coding can be done either in external coding platforms like visual studio or using Teamcenter BMIDE application. Siemens suggests BMIDE for coding the server side customization. In this blog, let us see how to set up BMIDE for coding. Set up a Business Modeler IDE project for coding Modify BMIDE.bat file When you install or configure the Business Modeler IDE, set up the JDK location and a compiler application. The bmide.bat file starts the Business Modeler IDE. Set the location of the JDK in the install-location\bmide\client\bmide.bat file. set JRE_HOME=C:\Program Files (x86)\Java\jrex set JAVA_HOME=C:\Program Files (x86)\Java\jdkx.x.x set JDK_HOME=C:\Program Files (x86)\Java\jdkx.x.x Set TC_ROOT variable to Teamcenter installation path. if not defined TC_ROOT set TC_ROOT=C:\Apps\Teamcenter12\TC_ROOT On Windows when Microsoft Visual Studio is used for compiling, a call to the vcvarsall.bat file in the bmide.bat file is required. The call should be before the PATH statement. Add V...

Types of Property in Teamcenter

Properties contains information describing the business object like name, description and so on. For Example, A screw object can contain properties like name, description, length, diameter, material, etc. A business object derive its properties from its persistent storage class. In addition to the persistent properties from storage class, business object can also have additional properties like run-time properties, compound properties and relation properties. Properties shown for business object in Rich client Types of Properties Persistent Persistent properties are properties of business objects that remain constant on the object. A simple value (for example, integer, string, or date). The value is stored in the database as an attribute and mapped to the property. Run-time A property that is defined at run time and attached to types. Run-time properties are derived each time the property is displayed. Run-time properties do not map directly to persistent ...

Teamcenter Batch LOV

Teamcenter offers 3 types of LOV and based on the use case, choose the LOV type. Unlike Classic and Dynamic LOVs, Batch LOVs are managed externally. To update or remove values from Classic or Dynamic LOV, we need to update LOV via BMIDE and deploy the changes as templates using tem.bat. Where as in Batch LOV, the updates happen using utility and does not require system downtime. Initially Batch LOV should be created in BMIDE and added to the respective property or properties. Once you deploy the batch lov to the database via tem, you can subsequently add values to the LOV using xml and load it into Teamcenter using bmide_manage_batch_lovs utility. To update existing Batch LOVs, you can extract the existing LOV values through the same utility in XML format, update the xml files and load it back using same utility. Creating new Batch LOV 1. In BMIDE, open Extensions\LOV Folder. Right click Batch LOV folder and choose New Batch LOV. Batch LOV 2. Click Finish 3. Add the Batch ...

Teamcenter: Basics of Report Builder

Teamcenter Report builder module allows to create custom reports based on PLM data from Teamcenter. Teamcenter Reports are mainly based on queries and PLMXML framework. Report definition specifies the data to display in the report. This includes the data source, additional properties to be extracted, and the rules for importing the data. XSL style sheets allow to control the properties you want to display in the report and the display order. They also help to define the look and format of the report. Report Administrators (DBA or non-DBA users) creates and manages the report definitions. End users uses these report definitions to generate various types of reports in Teamcenter or Active Workspace. Optional Teamcenter Reporting and Analytics( TcRA ) standalone application is used to create advanced reports using various data sources. Types of Reports Summary Reports Summary reports present information based on a Teamcenter saved query definition. No object selection...

Basics of Teamcenter Query Builder

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...

Cascading vs Interdependent LOV

Cascading LOV Cascading LOV or hierarchical LOV is an LOV whose values have their own sub-lovs. In Teamcenter, the cascading lovs are display as levels. We can setup multiple levels of values, the final level value selected is stored as property value Foe example, to define city property with cascading lov of st level as country, 2nd level as states and 3rd level as cities. Steps to create cascading LOV Create a main classic LOV to hold the sub LOV's. All the values of the main LOV should have a sub LOV assigned. For example, in main LOV create with state names as value, then create sub LOV for each state with city names. Main LOV Open the main LOV created in BMIDE. Select the Show Cascading View check box. Cascading LOV view is not shown unless the check box is selected. Select a value in the main LOV and choose sub LOV. In the LOV selection dialog box, select the sub lov. In case not created, create the sub lov for each value in main LOV. Sub LOV Cascading View Attach...

Teamcenter Preferences

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

Teamcenter Item Business Object (Item Data Model)

Items are the fundamental object used to model data in Teamcenter. They are commonly used to identify an element of a product (component, assembly, end item) or other data such as procurement specification, test procedure, standard part, shop tooling, change, and so on. Data modeled using the Item business object is generally revision controlled data and all revisions of the information must be maintained, tracked, and recoverable. Data must also be modeled using the Teamcenter concept of item if you want to build a structure of the items such as a bill of material (BOM) for items that represent a product. Item is the most common business object under which you create a new business object. Use the Item business object or its children when you want to create business objects to represent product parts. When you create a business object using Item (or one of its children) as the parent, in addition to the new business object, system also create an item master form, an item revision, and...

Search This Blog