|
|||||||||||
PREV NEXT | FRAMES NO FRAMES |
Packages that use com.ptc.windchill.upgrade.directives | |
com.ptc.core.meta.type.mgmt.upgrade | |
com.ptc.netmarkets.register | |
com.ptc.windchill.upgrade.directives | |
com.ptc.windchill.upgrade.directives.mig | |
com.ptc.windchill.upgrade.directives.postmigschemaupgrade | |
wt.access |
The access control service is responsible for defining and
enforcing access to business and system objects. |
wt.admin |
Provides classes to represent and manage AdministrativeDomain objects. |
wt.eff | Provides generic base effectivity functionality via EffService , EffConfigSpecAssistant and EffGroupAssistant to assert that a PDM object is effective under certain conditions; an out-of-the-box reference implementation of this base functionality is defined by wt.effectivity . |
wt.epm.upgrade | |
wt.fc | Provides high level datastore access by using the PersistenceManager (and server-side-only
PersistenceManagerSvr ) to find and manage Persistable objects. |
wt.federation | The federation service (wt.federation package) provides functionality to create and manage proxy objects of remote systems and perform utility functions supporting the federation system. |
wt.folder |
Provides classes to represent and manage folder and cabinet objects. |
wt.iba.definition.upgrade | |
wt.inf.container | |
wt.intersvrcom | Site External API: |
wt.lifecycle | |
wt.meeting | Uses the
MeetingService to manage
Meeting s of various
MeetingType s having
Agenda s and producing
Minutes , in particular
MeetingCenterMeeting s with their associated
MeetingCenterMeetingInfo (also see the
WebexOperationHelper ). |
wt.org | |
wt.query.template | Provides generic support for saved report queries using ReportTemplate and various
methods in ReportTemplateHelper for executing and generating reports. |
wt.queue | Overview |
wt.replication | |
wt.team | |
wt.vc | |
wt.vc.wip | |
wt.viewmarkup | Uses the
ViewMarkUpService
to view and add
MarkUp to
Viewable objects and to publish
DerivedImage s. |
wt.workflow.engine |
Provides workflow classes responsible for the flow of
control and data from an execution point of view. |
wt.workflow.forum | |
wt.workflow.notebook |
Classes in com.ptc.windchill.upgrade.directives used by com.ptc.core.meta.type.mgmt.upgrade | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by com.ptc.netmarkets.register | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by com.ptc.windchill.upgrade.directives | |
ForEachPersistentDescendant.ClassInfoVisitor
|
|
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
ParameterizedString
Works in conjunction with the ParameterizedStringScope and an
UpdateDirective which will configure the scope such as
ForEachConcreteImplementorOf to allow you to parameterize a
string using the ClassInfo that is in scope. |
|
ParameterizedString.StringPart
|
|
ParameterizedStringException
|
Classes in com.ptc.windchill.upgrade.directives used by com.ptc.windchill.upgrade.directives.mig | |
ForEachClassNameDbColumn
Given a database connection, find all columns containing java classnames and allow an extending class to specify a SQL update statement to be executed on the column. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
|
ParameterizedString
Works in conjunction with the ParameterizedStringScope and an
UpdateDirective which will configure the scope such as
ForEachConcreteImplementorOf to allow you to parameterize a
string using the ClassInfo that is in scope. |
Classes in com.ptc.windchill.upgrade.directives used by com.ptc.windchill.upgrade.directives.postmigschemaupgrade | |
ParameterizedString
Works in conjunction with the ParameterizedStringScope and an
UpdateDirective which will configure the scope such as
ForEachConcreteImplementorOf to allow you to parameterize a
string using the ClassInfo that is in scope. |
Classes in com.ptc.windchill.upgrade.directives used by wt.access | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.admin | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.eff | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.epm.upgrade | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.fc | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.federation | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.folder | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.iba.definition.upgrade | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.inf.container | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.intersvrcom | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.lifecycle | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.meeting | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.org | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.query.template | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.queue | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.replication | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.team | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.vc | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.vc.wip | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.viewmarkup | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.workflow.engine | |
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.workflow.forum | |
JavaMigrator
Migration of data in a new schema can occur in two ways. |
|
Migrator
Migration of data in a new schema can occur in two ways. |
Classes in com.ptc.windchill.upgrade.directives used by wt.workflow.notebook | |
Migrator
Migration of data in a new schema can occur in two ways. |
|
|||||||||||
PREV NEXT | FRAMES NO FRAMES |