Article - CS34155
When defining a LifeCycle template with "revise" transition not checked for a specific state, "New View version" fails for objects in such state in Windchill PDMLink
Modified: 10-Feb-2025
Applies To
- Windchill PDMLink 9.1 to 12.1
- Windchill MPMLink 9.1 to 12.1
Description
- When defining a LifeCycle template with Revise transition not checked for a specific state, New View version fails for objects in such state
- The advanced LifeCycle can be viewed or edited from Utilities >LifeCycle Template Administrator in the context where it has been defined or above
- When Revise box is not checked in Transitions area for a specific state of this advanced Lifecycle
- Action menu for WTPart in this state does not give access to Revise as expected
- Action Menu gives access to New > New View Version and New > New One Off Version as expected
- But when a new View Version or New One Off version is attempted, error message is issued in a new window
- Same error occurs in MPSE (MPMLink) when user tries to perform Selected > New Downstream View, New branch or New Alternate BOM
Revise Transitions not defined for latest version in lifecycle
- When New View Version, the initial state of new view version is not the initial state of lifecycle template
- How to create New Downstream View (service) using Service Associative Part Structure Browser (SAPSB) with out affecting the existing Transition rules
- Error while using Import from Spreadsheet functionality
Problem in export/import process. Nested exception is: wt.util.WTException: Revise transitions not defined for current version in life cycle template. (wt.ixb.publicforhandlers.ixbResource/8) wt.ixb.publicforhandlers.LogHelper$IxbException: Problem in export/import process. Nested exception is: (wt.lifecycle.lifecycleResource/223) wt.util.WTException: Revise transitions not defined for current version in life cycle template. at wt.lifecycle.StandardLifeCycleService.processReviseTransition(StandardLifeCycleService.java:11241) at wt.lifecycle.StandardLifeCycleService.processPreStoreEvent(StandardLifeCycleService.java:9402) at wt.lifecycle.StandardLifeCycleService$2.notifyVetoableMultiObjectEvent(StandardLifeCycleService.java:8568) at wt.events.StandardKeyedEventBranch.intDispatchEvent(StandardKeyedEventBranch.java:306) at wt.events.StandardKeyedEventBranch.dispatchVetoableMultiObjectEvent(StandardKeyedEventBranch.java:268) at wt.events.StandardKeyedEventDispatcher.intDispatchEvent(StandardKeyedEventDispatcher.java:306) at wt.events.StandardKeyedEventDispatcher.dispatchVetoableMultiObjectEvent(StandardKeyedEventDispatcher.java:244) at wt.services.StandardManagerService.intDispatchVetoableEvent(StandardManagerService.java:412) at wt.services.StandardManagerService.dispatchVetoableMultiObjectEvent(StandardManagerService.java:314) at wt.fc.StandardPersistenceManager.dispatchVetoableEvent(StandardPersistenceManager.java:2976) at wt.fc.StandardPersistenceManager.dispatchVetoableEvent(StandardPersistenceManager.java:2959) at wt.fc.StandardPersistenceManager.store(StandardPersistenceManager.java:708)
This is a printer-friendly version of Article 34155 and may be out of date. For the latest version click CS34155