Include control parameters with HTTP requests to alter the way that the REST Web Services handle them. For example, if you would like the server to include an identifying string in the response, you can use the atg-rest-user-input
control parameter to specify that identifying string.
You can include control parameters either in the URL for the REST Web Service or in the message body of a POST or PUT request.
Note: Several control parameters have equivalent configuration properties. Set these configuration properties to control the way that REST MVC Web Services are processed by default. See The REST MVC Definition Framework.
The following table explains the control parameters recognized by the REST Web Services server. This table also identifies if the parameter is used in the Legacy REST Web Services or the REST MVC Web Services.
Parameter | REST Version | Explanation |
---|---|---|
| Legacy Only | Use this parameter to control whether setting a value on a repository item property will add the value to an existing set of values or replace them. This only applies to repository item properties that hold multiple values. |
| Both Legacy and | Use this parameter to specify the container and element Java classes for nested object property values. For additional information, refer to the Using Nested Multiple Value Objects in Input section. |
| Both Legacy and MVC | Use this parameter to specify a Java class when you are setting an object property value. For additional information, refer to the Using Object Values in Input section. |
| Legacy Only | For requests which return an array or ordered list, adding this parameter with an integer value allows the caller to specify the number of elements to return. Used with |
| Legacy Only | The number of references to traverse when rendering output. By default it is zero which causes only the top level object to be returned. |
| Legacy Only | Use this parameter to specify which form handler values should be processed first. |
| Legacy Only | Use this parameter to send the Legacy REST Web Server a POST HTTP request but have it process the request as if it used a different HTTP method. For example you can use this control parameter to include message body data in a POST HTTP request but have the server process the request as if it used the GET method. Set the value of this parameter to GET, PUT, or DELETE. |
| Legacy Only | Use this parameter to specify the entry in an array or ordered list that will be the starting point when that array or ordered list is returned by the server. Set the value of the parameter to the integer value of the starting position. Use this parameter with |
| Both Legacy and MVC | Use this parameter to override the default input format configured for the server. Set the value of this parameter to |
| Legacy Only | Use this parameter to control whether the Legacy REST Web Services server will accept standard JSON markup for setting collection or map values on repository item properties. |
| Legacy Only | Use this parameter to specify the Java method signature when calling an overloaded method. This parameter is only needed if two or more instances of the overloaded method have the same number of arguments. |
| Both Legacy and MVC | Use this parameter to set the value of a component or repository item property to null. Set the property and include this parameter as the new value. |
| Both Legacy and MVC | Use this parameter to override the default output format configured for the server. Set the value of this parameter to |
| Both Legacy and MVC | Use this parameter to specify the Java classes for multiple values in JSON functional parameters. The For example, if a functional parameter is a
Use the
|
| Legacy Only | Use this parameter to apply property filtering to individual Legacy REST Web Services Requests. |
| Legacy Only | Use this parameter to apply property filter templates to individual REST Web Services Requests. |
| Legacy Only | Use this parameter to specify that the Legacy REST Web Services server should return exceptions it encounters when invoking form handlers in the HTTP response. |
| Legacy Only | Use this parameter to specify that the Legacy REST Web Services server should return the properties of the form handler objects it invokes in the HTTP response. |
| Legacy Only | Include RQL query strings in this parameter. |
| Legacy Only | Include this parameter to cause the server to return OK (200) for success rather than CREATED (201) or GONE (410). |
| Legacy Only | Use this parameter to create transient repository items. Include the parameter with the value |
| Both Legacy and MVC | Use this parameter to specify an identifying string that the REST Web Services server will include in the HTTP response. |