Some limits enforced in the Campaign Manager Operator Interface (CMOI) are not enforced by the Campaign Manager (CM) web service:
MaximumActiveBatches — The CMOI implements a range between 1 and 99999. The CM web service only validates the lower limit (1).
Initial BatchCount — The CMOI implements a range between 0 and 99999. The CM web service only validates the lower limit (0).
The CM web service allows campaign and batch names of no more than 50 characters. This is the same behavior of the CMOI.
Batch Prefix can have no more than 22 characters. Also, if no prefix is defined and the campaign name is more than 22 characters, only the first 22 characters are used as the prefix. his is the same behavior of the CMOI.
Batch Suffix can have no more than 22 characters. Also, if no suffix is defined and the base recipe name is more than 22 characters, only the first 22 characters are used as the suffix. This is the same behavior of the CMOI.
Number of batches and sequence length — No limit is set. This should be handled by the API.
BaseRecipe.Scale greater than 100 — The CM web service validates if the scale value is between 1 and 100.
Other considerations:
The web service relies on the batch subsystem for parameter validation and does no validation itself.
The web service cannot provide the values of batch parameters of type Named Set. You can use the Recipe Exchange web service to get these values.
Batch parameters of type other than integer and real have Min and Max values of 0 (zero).
The web service ignores all values except the values it requires to perform an operation. For example, if a recipe has no aliases, the web service ignores the values of the UnitAliases property since they are not needed.
Unlike the CMOI, the Campaign Manager web service does not perform any filtering of UnitAliases. The web service returns the actual list of UnitAliases. Client programs must implement any filtering required.