Package com.ptc.windchill.option.variantspec.loader

Class ATORuleConfigSpecXMLLoader

java.lang.Object

com.ptc.windchill.option.variantspec.loader.ATORuleConfigSpecXMLLoader

All Implemented Interfaces:

Serializable

public class ATORuleConfigSpecXMLLoader
extends Object
implements Serializable

Processes the "csvBeginOptionFilterConfigSpecs,csvOptionFilterConfigSpec,csvEndOptionFilterConfigSpecs" directives in the XML load file. Creates and persists option filter configuration specification objects based on input from a XML file. Method names and parameters are defined in csvmapfile.txt.

Supported API: true

Extendable: false This API supports creation of two types of option filter configuration specifications - Latest, Effectivity Confguration specification. Sample Example: Below example is provided to create two different types of option filter configuration specification - Latest, Effectivity configuration specfications. yyyy-MM-dd partConfigSpec1 Design INWORK partConfigSpec2 2020-02-07

See Also:

• Serialized Form

Method Summary

Modifier and Type	Method	Description
static boolean	loadConfigSpec(Hashtable<String,String> nv, Hashtable<String,Object> cmd_line, Vector<?> return_objects)	Processes the "csvOptionFilerConfigSpec" directive in the XML load file.

Methods inherited from class java.lang.Object

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

Method Details

loadConfigSpec

public static boolean loadConfigSpec(Hashtable<String,String> nv,
 Hashtable<String,Object> cmd_line,
 Vector<?> return_objects)
                              throws ParseException

Processes the "csvOptionFilerConfigSpec" directive in the XML load file. Creates a option filter configuration specifications for variant specification, persists it in the database. Should be enclosed with csvBeginOptionFilterConfigSpecs invalid input: '&' csvBeginOptionFilterConfigSpecs tags.

When using wt.load.LoadFromFile to load option filter configuration specifications for variant specification, use the following XML format:

XML Format

*

<csvPartConfigSpec handler="wt." >
	<csvconfigspecname>	part config spec name	</csvconfigspecname>
	<csvviewname>	view name	</csvviewname>
	<csvlifecyclestate>	lifecycle state	</csvlifecyclestate>
	<csveffectivitydate>	effectivity date	</csveffectivitydate>
</loadConfigSpec >

Tag Definitions

csvconfigspecname	This tag is mandatory invalid input: '&' should be unique in one loader file, which represents name of config spec.
csvviewname	Name of view to be considered for creating Latest configuration specification. This value is optional. If view is not provided, it will match to view of configurable module in case of traditional variant specification. In case of variant specifications associated with option set, it will match to root view from view hierchy..
csvlifecyclestate	Name of lifecyle state to be considered for creating Latest configuration specification. This value is optional. I value is not specified, lifecycle will be blank.
csveffectivitydate	Date to be considered for creating Effectivity configuration specification. This tag is optional. If this tag is provided, date format will be validated against user provided csveffectivityformat specified in csvBeginPartConfigSpecs. Otherwisename, this value will be validated against windchill session locale format. If value not given, latest configuration specification will be created with default view/lifecycle state

Supported API: true

Extendable: true

Throws:

ParseException