Add GroupByTypeRuleEntry element. Add plm:refType attribute to various attributes. PLM XML PDM Schema extension This element represents an Engineering Change. Each Change has a number of related objects, with relation type such as Affected, Problem, or Reference. Attributes: type: changeId: change id changeRevisionId: revision string, e.g. "B" ownerRef: Sub-elements: RelatedItem: related elements ReleaseStatus: ChangeRecord: records of adds, deletions and other changes ChangeRecordGroup: Workflow template classification's enumeration values. There are two kinds of templates: process template and task template. Workflow template's stage enumeration values. A template could be in a stage as being available for use, or being under construction, or being obsoleted. The WorkflowTemplateType represents the type for the workflow templates. Typically workflow template is used to initialize workflow processes. A workflow template have actions associated with it to represent a list of workflow actions that will be triggered during a workflow process. The actions objects are WorkflowAction objects. A workflow template also might have a parent task template, one or more dependency task templates, and one or more child task templates associated with it. These are also WorkflowTemplate objects. validate=skipName Each WorkflowAction object has one or more action handlers and business rules associated with it. The action handlers are represented by a list WorkflowHandlers, while the business rules are represented WorkflowBusinessRules. The WorkflowAction object also has a back pointer to its parent task template. A WorkflowHandler is a small program or function. Handlers are used to extend and customize workflow tasks. A WorkflowHandler object has one or more arguments associated with it. It also has a back pointer to its parent workflow action object. A WorkflowBusinessRule represents some conditions that must be met to perform a workflow action. It consists of one or more WorkflowBusinessRuleHandlers, and a rule quorum specifying the number of rule handlers that must return go for the workflow action to complete. It also has a back pointer to its parent workflow action object. A WorkflowSignoffProfile is used in a workflow review task template to define which a user will comply with to assign review responsibilities to other Users. A signoff profile consists of a group and a role for a user, while the group object should be of type plm:OrganisationType, and the role object should be of type plm:RoleType. The signoff profile object also has a back pointer to its related task template. A base type for defining relations between workflow task template and signoff profile elements. ownerRef is a reference to an owning object, such as a task template or a task. profileRefs is a reference to one or many signoff profiles that this owner object is associated to. Base type for Revision Rule Entries. Specifies a date to be used by other Rule Entries. Attributes: refDate: the dateTime isToday: if 'true', the dateTime is today (at 00.00 hours). A RevisionRule Entry for selecting a Revision by its Release Status. Attributes: status: This specifies the required release status of the Revision. It corresponds to the 'name' attribute of the corresponding ReleaseStatus element. If 'status' has the value "any", then any status is acceptable. type: specifies whether the rule is to use the release date, the effectivity dates, or the serial number range, in the ReleaseStatus, when choosing an element. May use the date or serial number from a DateRuleEntry or a SerialNumberRuleEntry. Latest Working Rule - select the most recent element with status Working (i.e. no ReleaseStatus). Working Rule Entry - i.e. no Release Status, selecting by user or group. Attributes: userRef: reference to User groupRef: isCurrentUser: if 'true', then select by the current user isCurrentGroup: if 'true', then select by the current group. Latest Rule Entry - i.e. most recent by creation date, numeric productId, or alphanumeric productId. Specifies a Serial Number to be used by other Rule Entries. This RuleEntry contains subordinate RuleEntries, which are of equal precedence. They are all processed; if there is at least one match, then the revision with the most recent creation date is configured. SubElements: RuleEntry: Each sub-element is a subordinate RuleEntry. This RuleEntry contains subordinate RuleEntries, and only applies to Structures with 'subType' attribute corresponding to one of a specified set of allowed types. The RuleEntry sub-elements are processed sequentially. SubElements: AllowedType: Each sub-element specifies an allowed 'subType' RuleEntry: Each sub-element is a subordinate RuleEntry. Note that these subordinate RuleEntries cannot be of type GroupByTypeRuleEntry. A Revision Rule is a rule specifying which Revisions of Structures should be configured. Sub-elements: RuleEntry: the clauses (entries) in the Rule. They are applied sequentially. A Form is a way of associating additional freeform attributes with an element, effectively defining a subclass of element. (The subclass can be specified by means of the "subType" attribute on the element). The attributes are attached to the Form by using UserData. The Form is attached to the element by means of an AssociatedForm element. Attributes: mainClass: subClass: A Folder is a general-purpose collection of other elements. Attributes: subType: Inherited from ManagedBase. A string representing the sub-type of the Folder. The string, "viewSet", is reserved for a set of Model Views in NX. folderContentRefs: The contents of the Folder. When the subType attribute is set to "viewSet", folderContentsRefs references a list of ProductViews with their usage attributes set to "modelView". The first reference in the list references the Base View. plm:Attribute used to associate a Folder with a PLM XML element. Attributes: folderRef reference to the Folder role role/purpose of Folder. plm:Attribute used to associate a Form with a PLM XML element. Attributes: formRef reference to the Form role role/purpose of Form. This defines an alternative id for an element, in some context. Attributes: identifierId: the alternative id. idContext: a context string supplementalContext: a list of context elements, such as Organisations alternativeIdOf: a list of elements that this is an id of isDispDefault: true if this is the id to display by default when displaying the identified element. validate=skipName validate=skipName validate=skipName ClosureRule is used to define what type of associated data gets exported. It consists of a sequence of clauses, each one defining a primary class, a secondary class, a relation, and an action. It is used to drive a traversal process. Attributes: scope: PLMXML or application Sub-Elements: Clause: Closure rule clause in string form, e.g. "CLASS.*:CLASS.*:ATTRIBUTE.*:TRAVERSE_AND_PROCESS" This element defines a configuration rule by referencing closure rule, variant rule and revision rule. Attributes: closureRuleRef: reference to a ClosureRule variantRuleRef: reference to a VariantRule revisionRuleRef: reference to a RevisionRule StructureContext is used to group together all the objects that the user would like to treat as a project for analysis. Attributes: configurationRuleRef: configurationRule for this element. structureRefs: structureRevisionRefs: occurrenceRefs: managedRefs: CollaborationContext is used to group together several StructureContext elements, and a default configuration rule. Attributes: currentContextRef: The current StructureContext. configurationRuleRef: configuration rule for this element. structureContextRefs: References to StructureContextRefs. managedRefs: references to attachments. This element gives the result of a Validation Check performed on an object. Attributes: name: name of the check result: true if check passed, false if failed status: an integer return code from the check comments: a comment string adHoc: true if the validation is ad-hoc. reportRef: URI of the validation report file. This element, derived from plm:Attribute, is used to give the results of applying a validation check to its parent element. Attributes: application: the validating application Sub-elements: Checker: the name and result of each check performed This element describes a change in terms of one or two Instances. Attributes: originalRef: the original Instance, if any. modifiedRef: the modified Instance, if any. select: If both Instances are present, the 'select' attribute can be used to specify what attribute or sub-element of the Instance has changed, by using an XPATH syntax (for example, "@quantity", or "Transform"). derived: true if the ChangeRecord exists as a result of an addition of a higher-level structure. parentRef: The parent StructureRevisionView of the 'Modified' Instance, unless 'derived' is true, in which case it is the higher-level StructureRevisionView from which this ChangeRecord is derived. This element defines a group of ChangeRecords which together define a logical or functional replacement. Attributes: transfer: true if the ChangeRecordGroup is the result of transferring the same component from one assembly to another. modifiedRootRef: The StructureRevisionView which is at the root of the Modified assembly. memberRefs: The ChangeRecord elements in the group.