- Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.
-
To include development parts when selecting Show Highest Released
and un-Released Revisions, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.omitAllRevisions = FALSE
By default, the BOM search to
connect parts via many relationships finds only parts that use the EC
Part policy when Show Highest Released & un-Released Revisions is
selected as part of the search criteria.
-
Set the value for this property depending on your business requirements:
-
TRUE - The BOM search to
connect parts via many relationships finds only parts that use the EC
Part policy when Show Highest Released & un-Released Revisions is
selected as part of the search criteria.
-
FALSE - To include Development parts,
set the property to false. When set to false,
it shows another radio button to show all revisions of the parts and
all policies. Development parts show up in this result.
-
To set levels for mass BOM change, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.AllowMassEBOMChangeUptoLevel=3
When selecting
assemblies for a mass BOM change, the level at which the assemblies can
be selected is restricted by this property.
-
Set an integer value.
If the property is set
to 0, it implies that there is no restriction and assemblies at any level
can be chosen for a mass BOM change.
-
To set derived relationship, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxBOMPartManagement.ReplaceBOM.Derived=true
-
Set the value for this property depending on your business requirements:
-
TRUE - A
derived relationship is set between the replaced part and the source part in
a Replace with Existing or Replace with New operation.
-
FALSE - This is the default value. No derived relationship is set.
-
To specify the list of state-policy pairs to be considered frozen:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.EBOMFrozenStates =
policy_ECPart,state_Released,policy_DevelopmentPart,state_Released
By default, only production parts in the Release state and development
parts in the Complete state can be connected to a BOM.
-
Add or remove states.
-
To specify the states where BOM Markups can be created, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.ECPart.AllowSaveMarkup = state_In Work,state_Frozen,state_Approved,state_Released
This property setting is provided to specify in which states the BOM markups can be created.
-
Add or remove states.
-
To specify whether BOM editing is allowed, select from these options, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.Part.RestrictPartModification = state_Obsolete
This property setting is provided to specify whether BOM editing is allowed, depending on the state of the Root Part (Context Part). This key used to show/hide the Enable Edit Mode command in the EBOM Page.
emxEngineeringCentral.DevelopmentPart.AllowApply=state_In Work,state_Frozen,state_Released This property specifies which state direct BOM edits can be made without markups. This property setting specifies whether changes and markups for production parts can be applied directly in the BOM or must always be applied via markup. This property is specific to development Parts.
-
Add or remove states.
-
To specify in which state direct BOM edits without markups can be
done, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxBOMPartManagement.ECPart.AllowApply=state_In Work
This property setting is provided to specify whether changes and markups for
production parts can be applied directly in the BOM or must
always be applied via a markup.
-
Add or remove states.
-
To specify the format for unit range notation: , follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
unit#{Delimiter}unit#{ContiguousDelimiter}unit#{Delimiter}unit#{ContiguousDelimiter} {SubsequentValue}
Unit range notation is used to define a range of units within a mod stack in unresolved BOMs. Unit ranges are used during BOM filtering to filter on a specific unit or range of units. Similarly, the PUE ECO Effectivity attribute also requires the same unit range notation, which indicates a range of units the ECO will be applied to. The format of the unit range value is validated against the unit range notation format specified in the Product Line properties file.
-
Change the standard unit range notation.
-
To specify the initial value for resequencing in BOM: , follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.Resequence.InitialValue = 10
When using the Add Next command in a BOM, this property specifies the initial Find Number value for resequencing parts.
-
Change the integer value.
-
To specify the incremental value for resequencing in BOM, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.Resequence.IncrementValue = 10
When using the Add Next command in a BOM, this property specifies the value by which to increment the Find Number.
-
Change the integer value.
-
To allow configured BOM in development mode, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxUnresolvedEBOM.WIPBOM.Allowed=true
-
Set the value for this property depending on your business requirements:
-
TRUE - This is the Default value. This enables users to remove configured parts from a CA with applicability. This mode of working is treated as development or WIP configured EBOM. See the Enterprise Change Management User's Guide.
-
FALSE - This prevents users from removing configured parts from a CA with applicability.
-
To change the default incremental value for Find Numbers when adding multiple parts to the BOM, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxBOMPartManagement.StructureBrowser.FNIncrement=1
The default is 1.
-
Set the property to any numeric positive value.
-
To control how released and unreleased revisions are handled when importing a BOM, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxBOMPartManagement.AllowUnReleasedRevs=True
-
Set the value for this property depending on your business requirements:
-
TRUE - To use either an unreleased or released revision. Unreleased revisions take precedence.
-
FALSE - To use the latest released revision. Children will not be imported under this node as it was released. If there is no latest released revision, then the first unreleased revision will be used.
-
To specify the policy and corresponding states in which the Reorder Tree feature needs to be allowed, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxEngineeringCentral.Resequence.AllowedStates = policy_ECPart:state_Preliminary,policy_DevelopmentPart:state_Create|state_PeerReview
By default the value is "policy_ECPart:state_Preliminary,policy_DevelopmentPart:state_Create|state_PeerReview" . Policies are separated by "," and states are
separated by "|". For example, for adding a policy with name
"policy_A" and re-sequence allowed states "state_X", " state_Y" and
"state_Z", the value of the key will be:
"policy_ECPart:state_Preliminary,policy_DevelopmentPart:state_Create|state_PeerReview,policy_A:state_X|state_Y|state_Z"
-
Set the policies based on your business requirements.
-
If needed, continue editing the page object. If finished,
save the page.
- When finished updating the text file with all properties you want to modify, including the ones shown here, use the text file to modify the emxEngineeringCentral.properties page object. For more information, see Editing Properties Using MQL.
|