Windchill does no checking to ensure that the international code designator numbers and coding system names set are valid. It is your responsibility to ensure the use of valid coding systems.

Use the xconfmanager utility to add the wt.org.organizationTypes property. For more information, see the PTC Windchill Specialized Administration Guide.

•The Windchill Domain attribute identifies the administrative area where the organization object resides. The domain selected must have access control rules set for the WTOrganization object type so that the users who create part and documents have read access to the organization objects that you want to use as internal organizations. For information on how to set up a domain for this use, see Setting Up Domains for Use with Owning Organization

If you enter a type and value for Organization ID in an organization participant, then Windchill combines the organization ID type number and ID and stores the resulting value in the organizationIdentifier attribute of the organization directory entry. The format of the attribute is:

<ICD_number>$<org_ID>

where:

<ICD_number> is the international code designator number assigned to the organization ID type. For example, the CAGE ICD number is 0141. For a list of ICD numbers, see the Registration Authority

<org_ID> is the organization identification number assigned when the organization was registered.

Using the Organization Utilities Page

The utilities listed on Organizations Utilities allow you to perform administrative actions at an organization level. Some of these utilities also appear in other locations. The difference is the context from which the utility is launched.

The utilities are grouped according to whether they are system administration utilities or business administration utilities. Many of links provided on the page give you access to the utilities that you need to use to perform the duties described in Typical Duties of Organization Administrators on page 143

To explore the use of each utility, click the corresponding link on the page and then click the help icon in the window that opens.

Changing an Established Internet Domain

If the internet domain associated with an organization context is changed by modifying the organization participant using the Participant Administration utility, the previous internet domain is no longer recognized as being associated with the organization context. Any types associated with the organization context’s previous internet domain are no longer recognized as mapping to the organization.

If the internet domain name of the organization is changed, each type associated with the organization context’s previous internet domain must be edited in the

Manage Types window of the Type and Attribute Management utility so that the type internal name contains the new internet domain reversed.

For example, the World Wide Tractors organization participant has an internet domain of worldwidetractors.com. A subtype of Engine created in that organization has the internal name of com.worldwidetractors.Engine.

If the internet domain is later changed using the Participant Administration utility to wwtractor.com, then the com.worldwidetractors.Engine subtype is no longer associated with the organization’s internet domain.

To associate the com.worldwidetractors.Engine subtype with the organization’s new internet domain name, the type’s internal name must be edited from com. worldwidetractors.Engine to com.wwtractor.Engine.

For more information on assigning domains to organization contexts, see

Participants (Users, Groups, and Organizations) on page 251 For more . information on types, see the help available from the Type and Attribute

Management utility.

Using the OrganizationSync Utility for

User Organization Changes

When a user is moved from one organization to another by using a third party tool that allows your site to modify user entries in your directory service, the domains of the user and of the user's personal cabinet are not automatically changed. As the site administrator, you can use the OrganizationSync command-line utility to update organization-related information for users who have changed organizations. After changing the user's organization through a third party tool, run the OrganizationSync utility to change the other organization-related information for the user. Using the utility ensures that properties of a user or set of users are in sync with their current organization.

Note

If you use the Participant Administration utility (and not a third party tool) to update user information in your directory service, then the OrganizationSync utility is automatically run as a result of changing a user's organization from the Edit User window.

The OrganizationSync utility does the following:

•Assigns a set of user-related business objects to the administrative domain of the user’s current organization. If a user does not have an organization, these objects are assigned to the Unaffiliated domain. The objects reassigned include the WTUser object, the user’s personal cabinet and content of that personal cabinet, and the user’s notebook.

•Removes the user from the administrators and creators groups of their previous organization context, if necessary. The utility determines the previous context by extracting the context of the user’s previous administrative domain.

•Updates the organization groups of any teams, in which the user was a member, to reflect the user’s current organizational membership.

Note

It is safe to run the OrganizationSync utility on a user that was not actually updated.

The syntax of the OrganizationSync command is as follows:

java wt.inf.container.OrganizationSync {--users -<user_list>} {--domains- <domain_list>}

{--domain--hierarchies <domain_list>} {--organizations- <organization_list>}

The brackets ({}) in the syntax indicate optional parameters and indicate parameters that you specify together. Parameter names are case-sensitive; enter the names using the case shown in the syntax and the following table.

<organization_list> A space-separated list of organization names.

When <domain_list> is used with the –domains parameter, all users in the domain are synchronized. When <domain_list> is used with the –domain- hierarchies parameter, all the users in each domain and in all descendent domains are synchronized.