A group of settings, or a configuration.
There can be parameter sets on the following levels:
The most common: Every process step has one configurable parameter set. (Exception: Delete Documents – no parameters are needed.)
A process can have one or more parameter sets (see registering an activity in XBOUND).
A client can have one or more parameter sets ( " ).
There can also be one or more global parameter sets ( " ).
Parameter sets are normally saved in the main database. Internally, all four kinds listed above are the same. However, their scope is different. To access a parameter set on process, client or global level, you (the developer) must know the key that is assigned to a parameter set.
Third-party products used with XBOUND load their parameter sets from the file system. But XBOUND needs the parameter set, too. In that case the parameter set must include a path to the third-party project file – which must be in a location that is available to the activities. The location or resource is accessed with the user credentials of the XBOUND Activities Service that the activity is assigned to. Therefore, the XBOUND service user needs sufficient access rights to that location or resource.
Theoretically, it is possible to save binaries as part of the parameter set.