Contents
-
Writing Tachyon Instructions
-
Integrating with Tachyon
-
Introduction
-
Tachyon RunInstruction command-line tool
-
Consumer API reference
-
ApplicableOperations
-
Approvals
-
AuditLogs
-
Authentication
-
ComponentHealthManager
-
Consumers
-
CustomProperties
-
CustomPropertyTypes
-
CustomPropertyValues
-
DataExport
-
Deploy
-
Devices
-
EventSource
-
EventSubscriptionAssignments
-
EventSubscriptions
-
Expressions
-
Fragments
-
Information (default)
-
InstructionDefinitions
-
InstructionHierarchies
-
Instructions
-
InstructionSets
-
InstructionStatistics
-
ManagementGroups
-
Notifications
-
Permissions
-
Policies
-
Policy
-
PolicyAssignments
-
PrincipalRoleManagementGroups
-
PrincipalRoles
-
Principals
-
PrincipalSearch
-
ProductPacks
-
RelatedInstructionDefinitions
-
ResponseErrors
-
Responses
-
ResponseTemplates
-
Role
-
Rules
-
ScheduledInstructions
-
SecurableTypes
-
Settings
-
SystemInformation
-
SystemStatistics
-
Tasks
-
TriggerTemplates
-
ApplicableOperations
-
Using scope and filter expressions
-
How to guides
-
Introduction
-
Tachyon .NET Consumer SDK
-
Tachyon PowerShell Toolkit
-
Index
Entity - Expressions - Provides services pertaining expressions
Page version: 17, last updated:
Verb | Request | Notes | Permissions required |
---|---|---|---|
POST | /Consumer/Expressions /GetReadable | Converts given expression tree to human readable form | None |
POST | /Consumer/Expressions /CheckScope | Checks if given two expressions can be merged into a single valid scope. Example, two expressions to check wrapped in a JSON object: Post model { "First": { // 1st scope expression "Attribute": "ostype", "Operator": "=", "Value": "Windows" }, "Second": { // 2nd scope expression "Attribute": "rammb", "Operator": ">", "Value": "2048" } } More details can be found on Using scope and filter expressions page. | None |