emxEngineeringCentral.omitAllRevisions | Determines whether to include development parts when selecting Show Highest Released
and un-Released Revisions.
-
TRUE = The BOM search to connect parts by 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 phase 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.
| True or False |
emxEngineeringCentral.AllowMassEBOMChangeUptoLevel | Determines the level at which users can select the assemblies for a mass BOM
change. If set to 0, there is no restriction and assemblies at any level can be chosen
for a mass BOM change. | Any positive integer |
emxBOMPartManagement.ReplaceBOM.Derived | Determines whether a derived relationship is set.
-
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
specified.
| True or False |
emxEngineeringCentral.EBOMFrozenStates | Specifies the list of state-policy pairs to be considered frozen. By default, only production parts in the Release state and development
parts in the Complete state can be connected to a BOM. | policy_ECPart,state_Released,policy_DevelopmentPart,state_Released |
emxEngineeringCentral.ECPart.AllowSaveMarkup | Specifies the states at which users can create BOM Markups. | state_In Work,state_Frozen,state_Approved,state_Released |
emxEngineeringCentral.Part.RestrictPartModification | Specifies 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. | state_In Work,state_Frozen,state_Approved,state_Released, state_Obsolete |
emxEngineeringCentral.DevelopmentPart.AllowApply | 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. | state_In Work,state_Frozen,state_Released |
emxBOMPartManagement.ECPart.AllowApply | Specifies whether changes and markups for
production parts can be applied directly in the BOM or must
always be applied via a markup. The default value is state_In Work. | state_In Work,state_Frozen,state_Released |
unit#{Delimiter}unit#{ContiguousDelimiter}unit#{Delimiter}unit#{ContiguousDelimiter} {SubsequentValue} | Specifies the format for unit range notation. The following properties can be defined in the emxProductLine.properties file to specify the valid unit range format. Delimiter value. Since unit ranges can be a group of many separate range values, a delimiter character is used to identify the correct set of range values. The default delimiter value is a comma (,). emxProductLine.Delimiter.Value=, Contiguous delimiter value. Build ranges can be contiguous, for example: 1,2,3,4. So the system represents it as a 1-4 range. By default, the value is a hyphen (-). emxProductLine.Contiguous.Delimiter.Value=- Subsequent value. Unit ranges include a special code / character at the end of the string that indicates “and subsequent.” This means that all subsequent units will include the defined change effectivity. By default, the value is a caret (^). emxProductLine.Subsequent.Value=^ | The following are valid unit range notation examples: 1,2,3,4,5 1,2,5-10,15-^ 1-^ 1-10,1-^ 1,2,6,8,15-30,40,50-^,1-40,52,67,85 1-10,!11-12,^ [The exclamation point (!) denotes NOT. This example indicates units 1 to infinity, excluding 11 and 12.] |
emxEngineeringCentral.Resequence.InitialValue | Specifies the initial Find Number value for resequencing parts when using the Add Next command in a BOM. | Any integer |
emxEngineeringCentral.Resequence.IncrementValue | Specifies the value by which to increment the Find Number when using the Add Next command in a BOM. | Any integer |
emxUnresolvedEBOM.WIPBOM.Allowed | Enables configured BOM in development mode. 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.
| True or False |
emxBOMPartManagement.StructureBrowser.FNIncrement | Determines the default incremental value for Find Numbers when adding multiple parts to the BOM. The default value is 1. | Any numeric positive value. |
emxBOMPartManagement.AllowUnReleasedRevs | Controls how released and unreleased revisions are handled when importing a BOM.
-
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.
| True or False |
emxEngineeringCentral.Resequence.AllowedStates | Specifies the policy and corresponding states in which the Reorder Tree feature needs to be allowed. 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" | |