In addition to the Execution_Parameters.xml file Process Composer creates a text-based file called Execution_Parameters.nv during the evaluate and export phase of a simulation process or activity. The text-based file contains only the name of the parameter and its value. Strings that span multiple lines are enclosed in single quotes. Some applications expect to read data in this name=value format and cannot interpret Execution_Parameters.xml. The following is an example of Execution_Parameters.nv: Finish = Plated Code = 34 Part numbers = 'a00034 a00035 b0634' Complete = true During the import and evaluate phase, Process Composer searches for the Execution_Parameters.xml file in the working directory. If the file is not found, Process Composer searches for Execution_Parameters.nv. During the import phase, Process Composer processes the value (Plated, 34, and true in the example shown here) in the same way it treats the content of the During the import phase, you cannot use the Execution_Parameters.nv file to create parameters that do not already exist in Process Composer. Note:
smaSimulationCentral.Range.legacyImportExport must be set to TRUE in the smaSimulationCentral.properties file to allow export/import to/from Execution_Parameters.nv during execution. See smaSimulationCentral.properties in the Process Composer Administrator's Guide.
|