Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

InvokeScreenAutomationRequest

import type { InvokeScreenAutomationRequest } from "https://aws-api.deno.dev/v0.4/services/honeycode.ts?docs=full";
interface InvokeScreenAutomationRequest {
appId: string;
clientRequestToken?: string | null;
rowId?: string | null;
screenAutomationId: string;
screenId: string;
variables?: {
[key: string]: VariableValue | null | undefined;
}
| null;
workbookId: string;
}

§Properties

§
appId: string
[src]

The ID of the app that contains the screen automation.

§
clientRequestToken?: string | null
[src]

The request token for performing the automation action. Request tokens help to identify duplicate requests. If a call times out or fails due to a transient error like a failed network connection, you can retry the call with the same request token. The service ensures that if the first call using that request token is successfully performed, the second call will return the response of the previous call rather than performing the action again.

Note that request tokens are valid only for a few minutes. You cannot use request tokens to dedupe requests spanning hours or days.

§
rowId?: string | null
[src]

The row ID for the automation if the automation is defined inside a block with source or list.

§
screenAutomationId: string
[src]

The ID of the automation action to be performed.

§
screenId: string
[src]

The ID of the screen that contains the screen automation.

§
variables?: {
[key: string]: VariableValue | null | undefined;
}
| null
[src]

Variables are specified as a map where the key is the name of the variable as defined on the screen. The value is an object which currently has only one property, rawValue, which holds the value of the variable to be passed to the screen. Any variables defined in a screen are required to be passed in the call.

§
workbookId: string
[src]

The ID of the workbook that contains the screen automation.