Execution definition contains 100% complete description of what will the execution compute and how will the resulting data look like.
export interface IExecutionDefinition
While the execution definition is part of the public API, it is a low-level structure and as such SHOULD NOT be used in the typical application code. The UI.SDK offers several convenience layers to construct the execution definition. The typical flows start in the Analytical Workspace.
|attributes||IAttribute||Attributes to slice the results by. MAY be empty. If not specified, then measures MUST be specified.|
|buckets||IBucket||Buckets describe logical grouping within attributes and measures - they serve as a metadata about the execution. They ARE NOT used during the execution itself. MAY be empty.|
Dimensionality and contents of dimensions. MUST be specified.
The dimensions specify how the result should be organized. For instance which attributes should be used to slice the row dimension, in which dimension should the measures be located.
|executionConfig?||IExecutionConfig||(Optional) additional configuration of the execution|
|filters||IFilter||Filters to apply during the execution. MAY be empty.|
|measures||IMeasure||Measures to calculate. MAY be empty. If not specified, then attributes MUST be specified.|
|postProcessing?||IPostProcessing||(Optional) Contains any configuration that should be done with the data after they are obtained from the server and before they are passed to the user.|
|sortBy||ISortItem||Sorting to apply on the results. MAY be empty.|
|workspace||string||Analytical Workspace against which the execution should be run.|