Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
WCBasicAdminGuide.pdf
Скачиваний:
71
Добавлен:
23.03.2015
Размер:
3.31 Mб
Скачать

Object Type

State

Permissions

Choice

All

Full control (All)

ChoiceRule

All

Full control (All)

Group

All

Full control (All)

Rules in Default Domain for OWNER

OWNER is a pseudo role that is used by Windchill to represent the object owner. Out-of-the-box Product Design access control rule for the OWNER pseudo role is described in the following table. The table lists the combination of object type, life cycle state, and granted permissions that are defined in the Default domain out-of- the-box rules:

Object Type

State

Permissions

DiscreteActionItem

All

Modify

PromotionNotice

Under Review

Read, Download, and

 

 

Delete

PromotionNotice

Rejected

Read, Download, and

 

 

Delete

Updating Access Control Rules

Caution

PTC recommends that you use caution when modifying the access control rules that are set when contexts are created. Modifying rules can cause problems with access to data and administrative functionality.

To adjust the access control rules that are defined, you can use the Policy Administration utility. Navigate to the product or library and click the Policy Administration link from the Utilities page. Select the /Default domain and click

Update. From the Administrative Domain window, click the Access Control tab to view the access control rules for the domain. From this tab, you can create new rules and update or delete existing rules. When creating or updating rules, the Groups tab shows the groups available from in the current context. These groups include the groups that map to the roles being used in the product or library team.

For more information about creating or updating access control rules, see the Access Control chapter of the PTC Windchill Specialized Administration Guide.

Understanding Products and Libraries

227

Configuring Products or Libraries for

Dynamic Documents

Products and libraries that will be used primarily for managing dynamic documents are generally no different from products and libraries used for managing parts. When setting up a product or library for this purpose, review all of the activities described in Typical Duties of Product and Library Administrators on page 176 keeping in mind that the main business object, type being managed is the Dynamic Document object type.

Since the out-of-the-box context templates do not have anything specifically set up for this object type, you may want to look closely at the following administration activities as they relate to managing this type of object:

Create folders for use in organizing the dynamic documents that are checked into your Windchill solution.

Create additional subtypes and attributes for dynamic documents. The subtypes and attributes correspond with Arbortext document types and attributes that are set up for use with the Arbortext Editor.

For more information, see the PTC Windchill Specialized Administration Guide.

Set up specific teams, life cycle templates, and workflow templates for use

with dynamic documents. For more information about these topics, see the

 

teams help, Understanding Life Cycles on page 299

and Understanding

,

Workflow on page 337

.

 

Review and set object initialization rules for Dynamic Document subtypes. for more information on setting object initialization rules, see the PTC Windchill Specialized Administration Guide

228

PTC Windchill® Basic Administration Guide

Note

Autonumbering must be turned on for the Dynamic Document subtype and its subtypes. By default, autonumbering is turned on for the wt.epm. EPMDocument type and all of its subtypes through an object initialization rule in the site context. Since dynamic documents are subtypes of the wt. epm.EPMDocument type, the rule automatically applies dynamic documents unless additional rules have been set up that override the site context rule.

For more information about numbering objects, see the PTC Windchill Specialized Administration Guide.

Set access control policies on the Dynamic Document subtypes. For more

information on setting access control policies, see Administering Domains and Policies on page 85 .

Additionally, there are activities unique to using the Arbortext Editor and the Arbortext Publishing Engine with product and libraries that need to be performed. These include the following:

Establish the configuration settings used by the Windchill connection to Arbortext Editor. For more information, see the Windchill connection online help accessible from the Arbortext Editor.

Manage the bursting rules used when a dynamic document is stored in Windchill. For more information on bursting rules, see the Arbortext Editor online help.

Manage additional attributes for WTDocument object type that are used by the publishing agent when publishing dynamic documents. For more information on specifying publishing rules, including specifying rules for the resulting documents, see the PTC Windchill Visualization Services Guide.

For more information about using product and libraries with Arbortext products to manage dynamic documents, see the Getting Started Authoring PTC Arbortext Documents guide.

Configuring Part and Document

Relationships

The relationships between a part and a document, two parts, or two documents vary depending upon how the two objects are linked. This section briefly describes the different types of links that form these relationships and then describes the configuration options that are available.

Understanding Products and Libraries

229

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]