...
The user must manually initiate a synchronization session with the master controller to download the latest configuration files. Seeing that the configuration manager works independent from FEWS, this is a required action to ensure that the local datastore is up to date. Only configuration files need to be synchronized.
| Wiki Markup |
|---|
Click on \ [Download\] to download all configuration files. The download button is only available if a connection has been established with a master controller.
In the screen above the download button is not available.
...
| Anchor |
|---|
| _Toc154574511 |
|---|
| _Toc154574511 |
|---|
|
Make a selected configuration file the active file
| Wiki Markup |
|---|
Of any configuration file instance, only one can be the active file. After selecting a file, click on \ [Set Active\] to make the selected file the active file. Only one configuration file may be active at any moment.
\\
| Anchor |
|---|
| _Toc154574512 |
|---|
| _Toc154574512 |
|---|
|
Delete a configuration file
...
Configuration files may only be deleted in the following situation:
The configuration file ID is a local ID, ie it starts with the prefix "CM: ".
The configuration file is not the active configuration file, i.e. it is not referenced in the default tableunmigrated-wiki-markup
To delete a configuration file, select the file and click on \ [Delete\]
\\
| Anchor |
|---|
| _Toc154574513 |
|---|
| _Toc154574513 |
|---|
|
Export a configuration file
...
The procedure to follow when certain configuration file needs to be changed is simple. To do so, carry out the following steps:
| Wiki Markup |
|---|
Step 1: Select the configuration that needs to be changed
Step 2: Export the file by clicking on \ [Export\]. This will start the 'editor' that has been configured for the selected configuration file. If the editor does not allow editing, close the editor and open the configuration file in an appropriate editor
Step 3: Make the required changes and save the file. Give the configuration file an appropriate name, using the file naming convention given in paragraph 13.2.5
Step 4: Import the modified file. Note that the filename is now shown in the description field.
Step 5: Set the newly imported file Active
Step 6: Use the analysis section to verify that the configuration is still correct. Verify the relevant workflows.
Step 7: Upload the configuration to the master controller. Check that the file has indeed been uploaded by verifying that the ID has been changed from a Local ID to a Master Controller ID