The following problem scopes are supported.
For any problem scope other than None, the transfer set can define a change request query expression. The expression does not need to include a query clause for problem types — a query clause is automatically added when the query expression is used. Thus, a blank query string returns all change request objects. The query expression can include any problem attribute using standard query syntax. For example, a query that is based on product name might be: "product_name='foobar'"
Problem query strings must be typed. However, you can use the problem query dialog to help you determine an appropriate query string to specify for a transfer set. The table shows some standard keywords that can be used in problem query strings in transfer set definitions.
Keyword | Resulting Action |
---|---|
%to_db_id | This keyword is replaced with the dbid of the DCM database for which the generate is performed. This action allows the same transfer set definition to apply to a number of target databases. |
%from_db_id | This keyword is replaced with the dbid of the current database from which a transfer package is being generated. |