Runtime Settings are used throughout the system to determine the behavior of system operations at design time and also at runtime. This is a powerful feature that allows you to pre-configure the environments for running the projects that you will be composing and orchestrating.
You can create any number of Runtime Settings in your project database.
When a new project database is created, the system automatically adds the following Runtime Settings into your project database as a starting point:
This is the default Runtime Setting that is assigned when you do not choose a specific one. You can also use this as your main runtime setting if you are working on a small or medium sized project where the same computer will be used for development, testing and deployment. The Default runtime setting is required by the system.
If your organization follows the normal Development, Test, Production cycle, you can use Development when you are developing your projects. In this case you will set your connection strings, web service login credentials etc. to your development computer/environment.
If you will be using a Test bed you can use this runtime setting for testing.
This is the out-of-the-box Runtime Setting for your production environment. You and add to it or you can create a brand new one to suit your needs.
To add, change, or delete a Runtime setting, select “Runtime Settings” from the “Settings” menu of the appRules Portal Application.
The following window will be displayed:
When adding a new Runtime Settings record, you must add a unique name for the Setting. Note that Setting Name and Runtime Setting Name are used interchangeably.
You can also use the preset Setting Names (Production, Test...)
Note that field descriptions are displayed at the bottom of the window.
To Add a RunTimeSetting, click the “New” button; enter the field values and click the “Save” button to add the new record to the project database.
To Change or Update a RuntimeSetting, select the specific entry in the Setting Name list, make changes to the field values and click the “Save” button to update the values.
To Delete a RuntimeSetting select the specific entry and click the “Remove” button to remove the record from the project database.
Default Culture: determine the culture that will be used when running the workflows or validating data. For example, if the en-US culture is selected, the dates handled will be in US format (Date in MM/DD/YY).
If the Default Culture is set to 'Default', System culture will be used.
Caching Option: specify the cache engine used when running in the specified environment (Redis or Internal, if Redis specify the connection string (installed by default by the appRules Setup))
Optional Runtime Fields: define runtime variables and values associated to the current RunTimeSetting. For example, the default file path for all files used in a project can have different values when a project is launched in a Production or Test environment.
NB: the master admin can secure the runtimesettings with a password. (Secure Button at the top). In this case the developers or simple users will not be able to display or change the related runtimesettings.