See ADT installRuntime command for more information. You do not install a separate runtime component. Adobe AIR. View Help PDF 5. Installing Adobe AIR. To install or update the runtime, a user must have administrative privileges for the computer.
Double-click the runtime installation file. See the field groups endpoint guide for more information. Mixins are reuseable components which define one or more fields that represent a particular concept, such as an individual person, a mailing address, or a web browser environment. Mixins are intended to be included as part of a schema that implements a compatible class, depending on the behavior of data they represent record or time series. Before continuing, please review the getting started guide for links to related documentation, a guide to reading the sample API calls in this document, and important information regarding required headers that are needed to successfully make calls to any Experience Platform API.
When listing resources, the Schema Registry limits result sets to items. In order to return resources beyond this limit, you must use paging parameters. It is also recommended that you use additional query parameters to filter results and reduce the number of resources returned. See the section on query parameters in the appendix document for more information.
The following request retrieves a list of mixins from the tenant container, using an orderby query parameter to sort the mixins by their title attribute. The response format depends on the Accept header sent in the request. The following Accept headers are available for listing mixins:. Select the appropriate Accept header depending on the information you require in your response.
The following request retrieves a mixin by its meta:altId value provided in the path. All lookup requests require a version be included in the Accept header. The following Accept headers are available:. A successful response returns the details of the mixin. The fields that are returned depend on the Accept header sent in the request. Experiment with different Accept headers to compare the responses and determine which header is best for your use case.
In this example, the mixin is compatible with a Property class that was defined previously. For details on how to define different field types to include in your mixin, see the field constraints guide.
These values are read-only and are assigned by the Schema Registry. You can replace an entire mixin through a PUT operation, essentially re-writing the resource. When updating a mixin through a PUT request, the body must include all of the fields that would be required when creating a new mixin in a POST request. If you only want to update part of a mixin instead of replacing it entirely, see the section on updating a portion of a mixin.
The following request re-writes an existing mixin, adding a new propertyCountry field. If you want to replace an entire resource with new values instead of updating individual fields, see the section on replacing a mixin using a PUT operation.
The example request below updates the description of an existing mixin, and adds a new propertyCity field. The request body takes the form of an array, with each listed object representing a specific change to an individual field.
Active 6 years, 10 months ago. Viewed 3k times. Improve this question. Hi viery, welcome to GDSE and thanks for your question. If you want to know more about the site, please see the help center or ping one of us in chat once your reputation is sufficient Keep contributing and enjoy the site! Add a comment. Active Oldest Votes. It seems it's a file created in photoshop, most likely. Improve this answer. Sam Collins Sam Collins 6 6 silver badges 21 21 bronze badges.
0コメント