[true|false]
The first two entries take true/false arguments and are set automatically during the installation and setup process.

The third takes a path argument for locating the cache in a custom directory. These properties generally should not be modified except under the direction of aPriori Professional Services or Support. For an explanation of the document cache, see the aPriori Installation Guide.

Note: The Bulk Costing properties file (install\ext\analysis-purchasing-module\plugin.properties) contains a setting to control cache cleaning upon execution of the Bulk Loader: launcher.set.apriori.enable.doc.cache.cleaner=false

This cleaner addresses the VPE and cost model caches but does not touch GCD/images. aPriori provides a separate script to clean the GCD/images cache:

 

 

The flattening cache applies only to the flattening capabilities of the Sheet Metal Process Group. See the aPriori Cost Model Guide for more information about this capability.

The timeout value determines how long cached flattened output is kept. The default value is 4 days.

The folder path determines where the files are cached. The default is:
C:\Users\<username>\AppData\Local\aPriori\<version>\tmp\flatteningCache

Note that the third property is for debugging use only and should only be changed in consultation with aPriori Support.

Can be set to true or false. Default = false. If set to true, intermediate input files that aPriori sends to the flattening subsystem are dumped to the user's cache location, e.g.

Files will be saved in

<partName> is the filename of the component being costed.

There will be an XML and a SAT file for input, and another XML/SAT pair for output. The output files will be in a bseOut subfolder.

The output XML contains all error codes reported by the flattening subsystem.

de_DE = German
fr_FR = French
en_US = American English (default)

Specify the language and its locale for the aPriori GUI. For a full description of these options, see "Selecting a Language for the aPriori Interface" in the aPriori User Guide.

Specifies the number of rows that are expanded in the Assembly Details tab. Default is 1000 rows

 

 

 

 

 

Allows you to cost CAD models that are either "surface-only" (having no solid geometry), or hybrids that have some combination of solid and surface-only features. Applies ONLY to User Guided process groups.

 

Allows you to cost CAD models that are either "surface-only" (having no solid geometry), or hybrids that have some combination of solid and surface-only features. Applies ONLY to Sheetmetal and Sheetmetal – Transfer Die process groups.

 

NOTE: For details about the interaction between these two similar properties, see the section following this table, “The enable.surface.model Properties”.

These properties specify how aPriori should handle CAD files containing more than one distinct solid body. Siemens NX files in particular may contain a combination of sub-components and other solid bodies due to specific NX modeling techniques.
All of these properties take [true|false]values, and the default is false.

apriori.keep.free.bodies – The behavior of this property depends on whether or not the CAD file is an NX assembly file. When set to true:

 Any CAD part file which contains multiple distinct (detached) solid bodies causes aPriori to interpret the file as an assembly with a subcomponent for each solid body. (For all CAD systems, a part file can contain detached solids, e.g. two extruded profiles which are not attached. Also note an NX file is considered a “part” if there is only one component in the Assembly Navigator pane AND an icon of a single cube appears beside it.)

 An NX assembly file causes aPriori to interpret the file as an assembly scenario with a subcomponent for each solid body and NX subcomponent. When set to false, only the largest solid body in the part file will be extracted as a part scenario. In an NX assembly file, only the subcomponents will be extracted, not the solid bodies. (When aPriori creates additional subcomponents from the free bodies, it generates names for them following the convention <filename>-AP_PART-1, <filename>-AP_PART-2, etc.)

Note: apriori.keep.free.bodies does not apply to Creo or CATIA assemblies, as it is not possible to have a “free body” protrusion existing in an assembly in those file formats.

apriori.free.bodies.preserve.CAD – Applies only to NX assembly files when apriori.keep.free.bodies is set to “true.” When set to true, all solid bodies and subcomponents in the NX file are imported. When set to false, aPriori excludes subcomponents that significantly overlap solid bodies as the solid bodies typically represent a finished part derived from the subcomponent.

apriori.free.bodies.ignore.missing.component – Applies only to NX files with a rare error: When set to “true” NX assembly files containing exactly one free body and one missing component will be interpreted as a part with the free body’s geometry. A “missing component” is one for which the corresponding CAD file cannot be found in the expected location.

NOTE: These properties apply to both interactive costing and Bulk Costing and Analysis. However, the Bulk Loader also recognizes two additional properties. See bulkLoad.properties below as well as the “Bulk Costing and Analysis” chapter in the aPriori Professional User Guide for more information.

As of Release 19.1, aPriori Professional also provides a Multi-Body Options dialog for setting these values. See “Multi-Body Options” in the “Changing User Preferences” section of the aPriori Professional User Guide.

Changes the Component Viewer display from Orthographic (default) to Perspective.

Use this property to increase the size of component images that are permitted to be saved to the database. For example, if you open a large part but its image does not appear in the UI, try increasing this value. Default value is “10”. Recommended increased value is “50”.

By default, aPriori plugins use DLLs from Spatial Interop as specified by the installer. For example: (<install_dir>\WIN64\catia\NT_VC11_64_DLL\code\bin)

However, some plugins might require different versions of these DLLs. This property allows you to specify a directory containing DLLs of a different version.

Implemented for efficient handling of large parts with thousands of GCDs. aPriori will only automatically highlight and select GCDs when the GCD category node has fewer GCDs than this setting. If this threshold is exceeded, NO automatic highlighting occurs, in order to prevent unacceptable delays in the GUI.