|
Working with Set App Param File Process |
  
|
Working with Set App Param File Process
|
Working with Set App Param File Process |
|
Process Purpose
The "Set App Param File" process is used to define which parameters file to use, in case you have more than one parameters file.
When you add a process, you are required to define its settings. This occurs in the process's properties window which is displayed automatically after having added the "Set App Param File" process.
If any subsequent edition is required, double-click the process to open its properties window and enter the necessary modifications.
Fill in the box:
Application Parameter File |
|
File Name |
Maintain the "default" option OR click
The "<Default>" option refers to the "project.par" file - the default parameters file that is generated when App Param variables are created during project development and which can be exported and edited according to the current requirements and deployed to devices whenever needed. See Parameters File. |
PURPOSE: a project requires different values for the same application parameters throughout its execution so, 2 parameters files must be created. The objective is to start with the default parameters file and, then, at some point in the application’s execution, set another parameters file to feed its values to the App Param variables.
1. Create the necessary App Param variables in the “App Params” tab (in the "Variable Select" window).
2. The corresponding “project.par” file is generated and stored in the project’s directory, in the “Data” folder.
3. Add the “Set App Param File” process to the intended point in the project’s workflow to set “project2.par” as the file that will feed the App Param variables from that moment on.
4. Once the project is fully developed, generate and/or publish the project and deploy it to the target devices.
5. Create the alternate parameters file:
a. Retrieve the original parameters file. b. Rename it “project2.par". c. Use an external edition application (ex: “Notepad”) to edit the parameter values as required.
6. Deploy the file “project2.par” to the device manually or via MCL-Mobility Platform to its “res” folder ("<Apps>App name\res").
|
If required, click 
to attach any relevant notes to this process. Click it and enter your notes in the resulting text box. These notes will be displayed in the corresponding "Actions" tab or "Process" window (in the "Notes" field) and in the "Developer Report".
After filling in the required options, click 
to conclude or 
to abort the operation.
The added process is displayed in the corresponding "Actions" tab or "Process" window.
Use the right-click in MCL-Designer's input boxes to access some related options as well as the general "Cut", "Copy"; "Paste"; "Search" actions (active/inactive according to the current context).
Ex: If you right-click the "Variable" input box (included in a "Conversion's" properties window), you are provided with general editing/search actions and other more specific options such as "Variable Select" (see "Variable Select"); "Variable Insert" (see "Variable Insert"); "Insert Special Character" (see To Insert Special Characters into a Control's Text Input Field) and "Localization Select" (see Localization List).
If you right-click another input box, it may provide other possibilities.
and select a variable with the name of the alternative parameters file that will replace the parameters file currently in use.