Package com.ptc.windchill.option.bean

Class VariantLoadPartConfigSpecBean

java.lang.Object

com.ptc.windchill.option.bean.VariantLoadPartConfigSpecBean

All Implemented Interfaces:

Serializable

public class VariantLoadPartConfigSpecBean
extends Object
implements Serializable

This bean is used to provide part configuration information from Java Variant Specification Loader API. This bean is also used to store part configuration specification data that was read from VariantSpec load Excel sheet.

Supported API: true

Extendable: false

See Also:

• Serialized Form

Constructor Summary

Constructors

Constructor	Description
VariantLoadPartConfigSpecBean(String argConfigSpecName, String argViewName, String argLifeCycleState, String argBaselineName, Date argEffectivityDate)	Supported API: true This API can be used to create object of part configuration specification.

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Details

VariantLoadPartConfigSpecBean

public VariantLoadPartConfigSpecBean(String argConfigSpecName,
 String argViewName,
 String argLifeCycleState,
 String argBaselineName,
 Date argEffectivityDate)

Supported API: true This API can be used to create object of part configuration specification. It supports creation of Latest,Baseline invalid input: '&' Date Effectivity Configuration specifications. Out of API parameters, configSpecName is required. All other are optional. If viewName, lifeCycleState, baselineName and effectivityDate are all null, then a Latest PartConfigSpec will be created. If only argConfigSpecName, argViewName or argLifeCycleState are provided, then Latest configuration specification will be created. If only argConfigSpecName invalid input: '&' argBaselineName are provided, then baseline configuration specification will be created. If only argConfigSpecName invalid input: '&' argEffectivityDate are provided, then effectivity configuration specification will be created. If is advised that, no two different types of configuration specification parameters should be provided. So following are NOT valid combinations - 1. argViewName or argLifeCycleState AND argBaselineName 1. argViewName or argLifeCycleState AND argEffectivityDate 1. argBaselineName AND argEffectivityDate

Parameters:

argConfigSpecName - Required. Provide a unique name for a config spec e.g. MyATOConfigSpec1

argViewName - - View names e.g. "Design", "Manufacturing" etc. Can be null.

argLifeCycleState - - LifeCycle names in the form of "INWORK", "RELEASED". Can be null.

argBaselineName - - An existing Baseline name. NOTE: Baseline is assumed to be persisted.

argEffectivityDate - - Effectivity date for the config spec. Can be null.