| Section | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
You will see the following message when the _data.properties file has been successfully uploaded to :
| Info |
|---|
|
Template Validation
Template Validation supports any properties locally available in the global _data managed by the super admin user. The _data property names that match a partially entered template name will be offered in the dropdown of matches. Any _data used on the URL at runtime is not supported (and will not validate) with this functionality because it is not known at design time, only runtime. A global _data property used in a template in a form/flow that is downloaded and uploaded into another frevvo instance that does not have that _data property will be flagged as an invalid template. In this situation, the designer can either ignore the error, update the default _data properties or, if the validation is for a flow/form or flow step property that prevents saving the properties, add a hidden control of the same name so that validation passes.
Setting Global Data in the Configuration
...
File
Properties listed in the the _data.properties can be overridden with properties prefixed by frevvo._data.<property name> in the following configuration filesthe frevvo-config.properties file located in <frevvohome>\tomcat\conf. Note the syntax for the properties has a dot before and after the _data.
...
.
This approach is helpful when deploying multiple environments. Let's say your organization has a Development, Production and UAT environment for . All three have the frevvo DB Connector configured for that environment. If you make a copy of the Production environment and database to create your UAT environment, you would have to download the _data properties file, make the changes to point to the DB Connector in the UAT environment, then upload the file again.
It is easier to create property files with a frevvo._data.dbURL parameter pointing to the correct locations for each environment.
This parameter in the frevvo.xml file would look like this:
| Code Block |
|---|
<Parameter name="frevvo._data.dbURL" value="http://<server>:<port>/database/listManagers" override="false" /> |
The same parameter in the web.xml file would look like this:
...
.
...
The same parameter in the frevvo-config.properties file would look like this:
...
As mentioned above, you can write the URL using a template such as {dbURLl}/database/listManagers. Then define the variable dbURL for the development, UAT and Production environments in the properties file you are using..