Class VersionProperties
Holds settings defined in OC, in Version Properties
Namespace: SuperOffice.Configuration
Assembly: SoCore.dll
Syntax
public class VersionProperties : ObjectRemarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.
Constructors
VersionProperties()
Holds settings defined in OC, in Version Properties
Declaration
public VersionProperties()Remarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.
Methods
GetBoolSetting(String, Boolean)
Holds settings defined in OC, in Version Properties
Declaration
public static bool GetBoolSetting(string settingName, bool defaultValue = false)Parameters
| Type | Name | Description |
|---|---|---|
| String | settingName | |
| Boolean | defaultValue |
Returns
| Type | Description |
|---|---|
| Boolean |
Remarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.
GetDoubleSetting(String, Double)
Holds settings defined in OC, in Version Properties
Declaration
public static double GetDoubleSetting(string settingName, double defaultValue = 0)Parameters
| Type | Name | Description |
|---|---|---|
| String | settingName | |
| Double | defaultValue |
Returns
| Type | Description |
|---|---|
| Double |
Remarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.
GetIntSetting(String, Int32)
Holds settings defined in OC, in Version Properties
Declaration
public static int GetIntSetting(string settingName, int defaultValue = 0)Parameters
| Type | Name | Description |
|---|---|---|
| String | settingName | |
| Int32 | defaultValue |
Returns
| Type | Description |
|---|---|
| Int32 |
Remarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.
GetSetting(String, String)
Holds settings defined in OC, in Version Properties
Declaration
public static string GetSetting(string settingName, string defaultValue = "")Parameters
| Type | Name | Description |
|---|---|---|
| String | settingName | |
| String | defaultValue |
Returns
| Type | Description |
|---|---|
| String |
Remarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.
UpdateSettings(IDictionary<String, String>)
Holds settings defined in OC, in Version Properties
Declaration
public static void UpdateSettings(IDictionary<string, string> rawSettings)Parameters
| Type | Name | Description |
|---|---|---|
| IDictionary<String, String> | rawSettings |
Remarks
This is a dictionary of key/value pairs. The Key can be the name of a setting, or <CustXXXX>:<name-of-setting>.
The forms are equivalent, except for the target. The plain form means every tenant in the process; the alternate form
can set or override for a particular tenant.
The value is whatever the setting requires
This mechanism is intended for experimental features that need (and must allow) repeated changes
to their state or configuration. It does not replace Feature Toggles, nor other ordinary settings for logging
or other product features.
It should only be used for temporary, explorative code that we need to test in Prod, but want/nees to be able
to fine-tune or turn off entirely, perhaps in a hurry when we realise it wasn't such a good idea after all.
These values are refreshed through the Local Service Proxy about every 30 seconds, giving a quite short latency
from setting in OC to actual effect in code.