Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Access
Policy Summary Contains an access policy that defines an identity's access to an IoT SiteWise Monitor resource.
- Action
Definition Contains a definition for an action.
- Action
Payload The JSON payload of the action.
- Action
Summary Contains the summary of the actions, including information about where the action resolves to.
- Aggregated
Value Contains aggregated asset property values (for example, average, minimum, and maximum).
- Aggregates
Contains the (pre-calculated) aggregate values for an asset property.
- Alarms
Contains the configuration information of an alarm created in an IoT SiteWise Monitor portal. You can use the alarm to monitor an asset property and get notified when the asset property value is outside a specified range. For more information, see Monitoring with alarms in the IoT SiteWise Application Guide.
- Asset
Binding Value Filter A filter used to match data bindings based on a specific asset. This filter identifies all computation models referencing a particular asset in their data bindings.
- Asset
Composite Model Contains information about a composite model in an asset. This object contains the asset's properties that you define in the composite model.
- Asset
Composite Model Path Segment Represents one level between a composite model and the root of the asset.
- Asset
Composite Model Summary Contains a summary of the composite model for a specific asset.
- Asset
Error Details Contains error details for the requested associate project asset action.
- Asset
Hierarchy Describes an asset hierarchy that contains a hierarchy's name and ID.
- Asset
Hierarchy Info Contains information about a parent asset and a child asset that are related through an asset hierarchy.
- Asset
Model Binding Value Filter A filter used to match data bindings based on a specific asset model. This filter identifies all computation models referencing a particular asset model in their data bindings.
- Asset
Model Composite Model Contains information about a composite model in an asset model. This object contains the asset property definitions that you define in the composite model.
- Asset
Model Composite Model Definition Contains a composite model definition in an asset model. This composite model definition is applied to all assets created from the asset model.
- Asset
Model Composite Model Path Segment Represents one level between a composite model and the root of the asset model.
- Asset
Model Composite Model Summary Contains a summary of the composite model.
- Asset
Model Hierarchy Describes an asset hierarchy that contains a hierarchy's name, ID, and child asset model ID that specifies the type of asset that can be in this hierarchy.
- Asset
Model Hierarchy Definition Contains an asset model hierarchy used in asset model creation. An asset model hierarchy determines the kind (or type) of asset that can belong to a hierarchy.
- Asset
Model Property Contains information about an asset model property.
- Asset
Model Property Binding Value Contains information about an
assetModelPropertybinding value.- Asset
Model Property Binding Value Filter A filter used to match data bindings based on a specific asset model property. This filter identifies all computation models that reference a particular property of an asset model in their data bindings.
- Asset
Model Property Definition Contains an asset model property definition. This property definition is applied to all assets created from the asset model.
- Asset
Model Property Path Segment Represents one level between a property and the root of the asset model.
- Asset
Model Property Summary Contains a summary of a property associated with a model. This includes information about which interfaces the property belongs to, if any.
- Asset
Model Status Contains current status information for an asset model. For more information, see Asset and model states in the IoT SiteWise User Guide.
- Asset
Model Summary Contains a summary of an asset model.
- Asset
Property Contains asset property information.
- Asset
Property Binding Value Represents a data binding value referencing a specific asset property. It's used to bind computation model variables to actual asset property values for processing.
- Asset
Property Binding Value Filter A filter used to match data bindings based on a specific asset property. This filter helps identify all computation models referencing a particular property of an asset in their data bindings.
- Asset
Property Path Segment Represents one level between a property and the root of the asset.
- Asset
Property Summary Contains a summary of a property associated with an asset.
- Asset
Property Value Contains asset property value information.
- Asset
Relationship Summary Contains information about assets that are related to one another.
- Asset
Status Contains information about the current status of an asset. For more information, see Asset and model states in the IoT SiteWise User Guide.
- Asset
Summary Contains a summary of an asset.
- Associated
Assets Summary Contains a summary of an associated asset.
- Attribute
Contains an asset attribute property. For more information, see Attributes in the IoT SiteWise User Guide.
- Batch
GetAsset Property Aggregates Entry Contains information for an asset property aggregate entry that is associated with the BatchGetAssetPropertyAggregates API.
To identify an asset property, you must specify one of the following:
-
The
assetIdandpropertyIdof an asset property. -
A
propertyAlias, which is a data stream alias (for example,/company/windfarm/3/turbine/7/temperature). To define an asset property's alias, see UpdateAssetProperty.
-
- Batch
GetAsset Property Aggregates Error Entry Contains error information for an asset property aggregate entry that is associated with the BatchGetAssetPropertyAggregates API.
- Batch
GetAsset Property Aggregates Error Info Contains the error code and the timestamp for an asset property aggregate entry that is associated with the BatchGetAssetPropertyAggregates API.
- Batch
GetAsset Property Aggregates Skipped Entry Contains information for an entry that has been processed by the previous BatchGetAssetPropertyAggregates request.
- Batch
GetAsset Property Aggregates Success Entry Contains success information for an entry that is associated with the BatchGetAssetPropertyAggregates API.
- Batch
GetAsset Property Value Entry Contains information for an asset property value entry that is associated with the BatchGetAssetPropertyValue API.
To identify an asset property, you must specify one of the following:
-
The
assetIdandpropertyIdof an asset property. -
A
propertyAlias, which is a data stream alias (for example,/company/windfarm/3/turbine/7/temperature). To define an asset property's alias, see UpdateAssetProperty.
-
- Batch
GetAsset Property Value Error Entry Contains error information for an asset property value entry that is associated with the BatchGetAssetPropertyValue API.
- Batch
GetAsset Property Value Error Info The error information, such as the error code and the timestamp.
- Batch
GetAsset Property Value History Entry Contains information for an asset property historical value entry that is associated with the BatchGetAssetPropertyValueHistory API.
To identify an asset property, you must specify one of the following:
-
The
assetIdandpropertyIdof an asset property. -
A
propertyAlias, which is a data stream alias (for example,/company/windfarm/3/turbine/7/temperature). To define an asset property's alias, see UpdateAssetProperty.
-
- Batch
GetAsset Property Value History Error Entry A list of the errors (if any) associated with the batch request. Each error entry contains the
entryIdof the entry that failed.- Batch
GetAsset Property Value History Error Info The error information, such as the error code and the timestamp.
- Batch
GetAsset Property Value History Skipped Entry Contains information for an entry that has been processed by the previous BatchGetAssetPropertyValueHistory request.
- Batch
GetAsset Property Value History Success Entry Contains success information for an entry that is associated with the BatchGetAssetPropertyValueHistory API.
- Batch
GetAsset Property Value Skipped Entry Contains information for an entry that has been processed by the previous BatchGetAssetPropertyValue request.
- Batch
GetAsset Property Value Success Entry Contains success information for an entry that is associated with the BatchGetAssetPropertyValue API.
- Batch
PutAsset Property Error Contains error information from updating a batch of asset property values.
- Batch
PutAsset Property Error Entry Contains error information for asset property value entries that are associated with the BatchPutAssetPropertyValue API.
- Citation
Contains text content to which the SiteWise Assistant refers to, and generate the final response. It also contains information about the source.
- Column
Info A description of the column in the query results.
- Column
Type The data type of the column.
- Composite
Model Property Contains information about a composite model property on an asset.
- Composition
Details Metadata for the composition relationship established by using
composedAssetModelIdinCreateAssetModelCompositeModel.- Composition
Relationship Item Represents a composite model that composed an asset model of type
COMPONENT_MODEL.- Composition
Relationship Summary Contains a summary of the components of the composite model.
- Computation
Model Anomaly Detection Configuration Contains the configuration of the type of anomaly detection computation model.
- Computation
Model Configuration The configuration for the computation model.
- Computation
Model Data Binding Usage Summary A summary of how a specific data binding is used across computation models. This tracks dependencies between data sources and computation models, allowing you to understand the impact of changes to data sources.
- Computation
Model Data Binding Value Contains computation model data binding value information, which can be one of
assetModelProperty,list.- Computation
Model Resolve ToResource Summary A summary of the resource that a computation model resolves to.
- Computation
Model Status Contains current status information for a computation model.
- Computation
Model Summary Contains a summary of a computation model.
- Configuration
Error Details Contains the details of an IoT SiteWise configuration error.
- Configuration
Status Contains current status information for the configuration.
- Content
Contains the cited text from the data source.
- Csv
A .CSV file.
- Customer
Managed S3Storage Contains information about a customer managed Amazon S3 bucket.
- Dashboard
Summary Contains a dashboard summary.
- Data
Binding Value Represents a value used in a data binding. It can be an asset property or an asset model property.
- Data
Binding Value Filter A filter used to match specific data binding values based on criteria. This filter allows searching for data bindings by asset, asset model, asset property, or asset model property.
- Data
SetReference Contains information about the dataset use and it's source.
- Dataset
Source The data source for the dataset.
- Dataset
Status The status of the dataset. This contains the state and any error messages. The state is
ACTIVEwhen ready to use.- Dataset
Summary The summary details for the dataset.
- Datum
Represents a single data point in a query result.
- Detailed
Error Contains detailed error information.
- Error
Details Contains the details of an IoT SiteWise error.
- Error
Report Location The Amazon S3 destination where errors associated with the job creation request are saved.
- Execution
Status The status of the execution.
- Execution
Summary Contains the execution summary of the computation model.
- Expression
Variable Contains expression variable information.
- File
The file in Amazon S3 where your data is saved.
- File
Format The file format of the data in S3.
- Forwarding
Config The forwarding configuration for a given property.
- Gateway
Capability Summary Contains a summary of a gateway capability configuration.
- Gateway
Platform The gateway's platform configuration. You can only specify one platform type in a gateway.
(Legacy only) For Greengrass V1 gateways, specify the
greengrassparameter with a valid Greengrass group ARN.For Greengrass V2 gateways, specify the
greengrassV2parameter with a valid core device thing name. If creating a V3 gateway (gatewayVersion=3), you must also specify thecoreDeviceOperatingSystem.For Siemens Industrial Edge gateways, specify the
siemensIEparameter with a valid IoT Core thing name.- Gateway
Summary Contains a summary of a gateway.
- Greengrass
Contains details for a gateway that runs on IoT Greengrass. To create a gateway that runs on IoT Greengrass, you must add the IoT SiteWise connector to a Greengrass group and deploy it. Your Greengrass group must also have permissions to upload data to IoT SiteWise. For more information, see Ingesting data using a gateway in the IoT SiteWise User Guide.
- Greengrass
V2 Contains details for a gateway that runs on IoT Greengrass V2. To create a gateway that runs on IoT Greengrass V2, you must deploy the IoT SiteWise Edge component to your gateway device. Your Greengrass device role must use the
AWSIoTSiteWiseEdgeAccesspolicy. For more information, see Using IoT SiteWise at the edge in the IoT SiteWise User Guide.- Group
Identity Contains information for a group identity in an access policy.
- Hierarchy
Mapping Maps a hierarchy from an interface asset model to a hierarchy in the asset model where the interface is applied.
- IamRole
Identity Contains information about an Identity and Access Management role. For more information, see IAM roles in the IAM User Guide.
- IamUser
Identity Contains information about an Identity and Access Management user.
- Identity
Contains an identity that can access an IoT SiteWise Monitor resource.
Currently, you can't use Amazon Web Services API operations to retrieve IAM Identity Center identity IDs. You can find the IAM Identity Center identity IDs in the URL of user and group pages in the IAM Identity Center console.
- Image
Contains an image that is one of the following:
-
An image file. Choose this option to upload a new image.
-
The ID of an existing image. Choose this option to keep an existing image.
-
- Image
File Contains an image file.
- Image
Location Contains an image that is uploaded to IoT SiteWise and available at a URL.
- Interface
Relationship Contains information about the relationship between an asset model and an interface asset model that is applied to it.
- Interface
Relationship Summary Contains summary information about an interface relationship, which defines how an interface is applied to an asset model. This summary provides the essential identifiers needed to retrieve detailed information about the relationship.
- Interface
Summary Contains summary information about an interface that a property belongs to.
- Interpolated
Asset Property Value Contains information about an interpolated asset property value.
- Invocation
Output This contains the SiteWise Assistant's response and the corresponding citation.
- JobConfiguration
Contains the configuration information of a job, such as the file format used to save data in Amazon S3.
- JobSummary
Contains the job summary information.
- Kendra
Source Detail The source details for the Kendra dataset source.
- Location
Contains location information about the cited text and where it's stored.
- Logging
Options Contains logging options.
- Matched
Data Binding Represents a data binding that matches the specified filter criteria.
- Measurement
Contains an asset measurement property. For more information, see Measurements in the IoT SiteWise User Guide.
- Measurement
Processing Config The processing configuration for the given measurement property. You can configure measurements to be kept at the edge or forwarded to the Amazon Web Services Cloud. By default, measurements are forwarded to the cloud.
- Metric
Contains an asset metric property. With metrics, you can calculate aggregate functions, such as an average, maximum, or minimum, as specified through an expression. A metric maps several values to a single value (such as a sum).
The maximum number of dependent/cascading variables used in any one metric calculation is 10. Therefore, a root metric can have up to 10 cascading metrics in its computational dependency tree. Additionally, a metric can only have a data type of
DOUBLEand consume properties with data types ofINTEGERorDOUBLE.For more information, see Metrics in the IoT SiteWise User Guide.
- Metric
Processing Config The processing configuration for the given metric property. You can configure metrics to be computed at the edge or in the Amazon Web Services Cloud. By default, metrics are forwarded to the cloud.
- Metric
Window Contains a time interval window used for data aggregate computations (for example, average, sum, count, and so on).
- Monitor
Error Details Contains IoT SiteWise Monitor error details.
- Multi
Layer Storage Contains information about the storage destination.
- Parquet
A parquet file.
- Portal
Resource Identifies an IoT SiteWise Monitor portal.
- Portal
Status Contains information about the current status of a portal.
- Portal
Summary Contains a portal summary.
- Portal
Type Entry The configuration entry associated with the specific portal type. The
portalTypeConfigurationis a map of theportalTypeKeyto thePortalTypeEntry.- Project
Resource Identifies a specific IoT SiteWise Monitor project.
- Project
Summary Contains project summary information.
- Property
Contains asset property information.
- Property
Mapping Maps a property from an interface asset model to a property in the asset model where the interface is applied.
- Property
Mapping Configuration Contains configuration options for mapping properties from an interface asset model to an asset model where the interface is applied.
- Property
Notification Contains asset property value notification information. When the notification state is enabled, IoT SiteWise publishes property value updates to a unique MQTT topic. For more information, see Interacting with other services in the IoT SiteWise User Guide.
- Property
Type Contains a property type, which can be one of
attribute,measurement,metric, ortransform.- Property
Value Null Value The value type of null asset property data with BAD and UNCERTAIN qualities.
- PutAsset
Property Value Entry Contains a list of value updates for an asset property in the list of asset entries consumed by the BatchPutAssetPropertyValue API operation.
- Reference
Contains the reference information.
- Resolve
To The detailed resource this execution summary resolves to.
- Resource
Contains an IoT SiteWise Monitor resource ID for a portal or project.
- Retention
Period The number of days your data is kept in the hot tier. By default, your data is kept indefinitely in the hot tier.
- Row
Represents a single row in the query results.
- Siemens
Ie Contains details for a SiteWise Edge gateway that runs on a Siemens Industrial Edge Device.
- Source
The data source for the dataset.
- Source
Detail The details of the dataset source associated with the dataset.
- Target
Resource The resource the action will be taken on. This can include asset-based resources and computation model resources.
- Time
InNanos Contains a timestamp with optional nanosecond granularity.
- Time
Series Summary Contains a summary of a time series (data stream).
- Trace
Contains tracing information of the SiteWise Assistant's reasoning and data access.
- Transform
Contains an asset transform property. A transform is a one-to-one mapping of a property's data points from one form to another. For example, you can use a transform to convert a Celsius data stream to Fahrenheit by applying the transformation expression to each data point of the Celsius stream. A transform can only have a data type of
DOUBLEand consume properties with data types ofINTEGERorDOUBLE.For more information, see Transforms in the IoT SiteWise User Guide.
- Transform
Processing Config The processing configuration for the given transform property. You can configure transforms to be kept at the edge or forwarded to the Amazon Web Services Cloud. You can also configure transforms to be computed at the edge or in the cloud.
- Tumbling
Window Contains a tumbling window, which is a repeating fixed-sized, non-overlapping, and contiguous time window. You can use this window in metrics to aggregate data from properties and other assets.
You can use
m,h,d, andwwhen you specify an interval or offset. Note thatmrepresents minutes,hrepresents hours,drepresents days, andwrepresents weeks. You can also usesto represent seconds inoffset.The
intervalandoffsetparameters support the ISO 8601 format. For example,PT5Srepresents 5 seconds,PT5Mrepresents 5 minutes, andPT5Hrepresents 5 hours.- User
Identity Contains information for a user identity in an access policy.
- Variable
Value Identifies a property value used in an expression.
- Variant
Contains an asset property value (of a single type only).
- Warm
Tier Retention Period Set this period to specify how long your data is stored in the warm tier before it is deleted. You can set this only if cold tier is enabled.
Enums§
- Aggregate
Type - When writing a match expression against
AggregateType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Asset
Error Code - When writing a match expression against
AssetErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Asset
Model State - When writing a match expression against
AssetModelState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Asset
Model Type - When writing a match expression against
AssetModelType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Asset
Model Version Type - When writing a match expression against
AssetModelVersionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Asset
Relationship Type - When writing a match expression against
AssetRelationshipType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Asset
State - When writing a match expression against
AssetState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Auth
Mode - When writing a match expression against
AuthMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
Entry Completion Status - When writing a match expression against
BatchEntryCompletionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
GetAsset Property Aggregates Error Code - When writing a match expression against
BatchGetAssetPropertyAggregatesErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
GetAsset Property Value Error Code - When writing a match expression against
BatchGetAssetPropertyValueErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
GetAsset Property Value History Error Code - When writing a match expression against
BatchGetAssetPropertyValueHistoryErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
PutAsset Property Value Error Code - When writing a match expression against
BatchPutAssetPropertyValueErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capability
Sync Status - When writing a match expression against
CapabilitySyncStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Column
Name - When writing a match expression against
ColumnName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Computation
Model State - When writing a match expression against
ComputationModelState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Computation
Model Type - When writing a match expression against
ComputationModelType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Compute
Location - When writing a match expression against
ComputeLocation, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Configuration
State - When writing a match expression against
ConfigurationState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Core
Device Operating System - When writing a match expression against
CoreDeviceOperatingSystem, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dataset
Source Format - When writing a match expression against
DatasetSourceFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dataset
Source Type - When writing a match expression against
DatasetSourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dataset
State - When writing a match expression against
DatasetState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Detailed
Error Code - When writing a match expression against
DetailedErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Disassociated
Data Storage State - When writing a match expression against
DisassociatedDataStorageState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Encryption
Type - When writing a match expression against
EncryptionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Error
Code - When writing a match expression against
ErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Execution
State - When writing a match expression against
ExecutionState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Forwarding
Config State - When writing a match expression against
ForwardingConfigState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Identity
Type - When writing a match expression against
IdentityType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Image
File Type - When writing a match expression against
ImageFileType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - JobStatus
- When writing a match expression against
JobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - List
Asset Model Properties Filter - When writing a match expression against
ListAssetModelPropertiesFilter, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - List
Asset Properties Filter - When writing a match expression against
ListAssetPropertiesFilter, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - List
Assets Filter - When writing a match expression against
ListAssetsFilter, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - List
Bulk Import Jobs Filter - When writing a match expression against
ListBulkImportJobsFilter, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - List
Time Series Type - When writing a match expression against
ListTimeSeriesType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Logging
Level - When writing a match expression against
LoggingLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Monitor
Error Code - When writing a match expression against
MonitorErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Permission
- When writing a match expression against
Permission, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Portal
State - When writing a match expression against
PortalState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Portal
Type - When writing a match expression against
PortalType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Property
Data Type - When writing a match expression against
PropertyDataType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Property
Notification State - When writing a match expression against
PropertyNotificationState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Quality
- When writing a match expression against
Quality, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - RawValue
Type - When writing a match expression against
RawValueType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Resolve
ToResource Type - When writing a match expression against
ResolveToResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Resource
Type - When writing a match expression against
ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Response
Stream Contains the response, citation, and trace from the SiteWise Assistant.
- Scalar
Type - When writing a match expression against
ScalarType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Storage
Type - When writing a match expression against
StorageType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Target
Resource Type - When writing a match expression against
TargetResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Time
Ordering - When writing a match expression against
TimeOrdering, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traversal
Direction - When writing a match expression against
TraversalDirection, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traversal
Type - When writing a match expression against
TraversalType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Warm
Tier State - When writing a match expression against
WarmTierState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.