EnterpriseCrmFrontendsEventbusProtoTaskConfigResponse

data class EnterpriseCrmFrontendsEventbusProtoTaskConfigResponse(val alertConfigs: List<EnterpriseCrmEventbusProtoTaskAlertConfigResponse>, val createTime: String, val creatorEmail: String, val description: String, val disableStrictTypeValidation: Boolean, val errorCatcherId: String, val externalTaskType: String, val failurePolicy: EnterpriseCrmEventbusProtoFailurePolicyResponse, val incomingEdgeCount: Int, val jsonValidationOption: String, val label: String, val lastModifiedTime: String, val nextTasks: List<EnterpriseCrmEventbusProtoNextTaskResponse>, val nextTasksExecutionPolicy: String, val parameters: Map<String, String>, val position: EnterpriseCrmEventbusProtoCoordinateResponse, val precondition: String, val preconditionLabel: String, val rollbackStrategy: EnterpriseCrmFrontendsEventbusProtoRollbackStrategyResponse, val successPolicy: EnterpriseCrmEventbusProtoSuccessPolicyResponse, val synchronousCallFailurePolicy: EnterpriseCrmEventbusProtoFailurePolicyResponse, val taskEntity: EnterpriseCrmFrontendsEventbusProtoTaskEntityResponse, val taskExecutionStrategy: String, val taskName: String, val taskNumber: String, val taskSpec: String, val taskTemplateName: String, val taskType: String)

The task configuration details. This is not the implementation of Task. There might be multiple TaskConfigs for the same Task.

Constructors

fun EnterpriseCrmFrontendsEventbusProtoTaskConfigResponse(alertConfigs: List<EnterpriseCrmEventbusProtoTaskAlertConfigResponse>, createTime: String, creatorEmail: String, description: String, disableStrictTypeValidation: Boolean, errorCatcherId: String, externalTaskType: String, failurePolicy: EnterpriseCrmEventbusProtoFailurePolicyResponse, incomingEdgeCount: Int, jsonValidationOption: String, label: String, lastModifiedTime: String, nextTasks: List<EnterpriseCrmEventbusProtoNextTaskResponse>, nextTasksExecutionPolicy: String, parameters: Map<String, String>, position: EnterpriseCrmEventbusProtoCoordinateResponse, precondition: String, preconditionLabel: String, rollbackStrategy: EnterpriseCrmFrontendsEventbusProtoRollbackStrategyResponse, successPolicy: EnterpriseCrmEventbusProtoSuccessPolicyResponse, synchronousCallFailurePolicy: EnterpriseCrmEventbusProtoFailurePolicyResponse, taskEntity: EnterpriseCrmFrontendsEventbusProtoTaskEntityResponse, taskExecutionStrategy: String, taskName: String, taskNumber: String, taskSpec: String, taskTemplateName: String, taskType: String)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

Alert configurations on error rate, warning rate, number of runs, durations, etc.

Link copied to clipboard

Auto-generated.

Link copied to clipboard

The creator's email address. Auto-generated from the user's email.

Link copied to clipboard

User-provided description intended to give more business context about the task.

Link copied to clipboard

If this config contains a TypedTask, allow validation to succeed if an input is read from the output of another TypedTask whose output type is declared as a superclass of the requested input type. For instance, if the previous task declares an output of type Message, any task with this flag enabled will pass validation when attempting to read any proto Message type from the resultant Event parameter.

Link copied to clipboard

Optional Error catcher id of the error catch flow which will be executed when execution error happens in the task

Link copied to clipboard
Link copied to clipboard

Optional. Determines the number of times the task will be retried on failure and with what retry strategy. This is applicable for asynchronous calls to Eventbus alone (Post To Queue, Schedule etc.).

Link copied to clipboard

The number of edges leading into this TaskConfig.

Link copied to clipboard

If set, overrides the option configured in the Task implementation class.

Link copied to clipboard

User-provided label that is attached to this TaskConfig in the UI.

Link copied to clipboard

Auto-generated.

Link copied to clipboard

The set of tasks that are next in line to be executed as per the execution graph defined for the parent event, specified by event_config_id. Each of these next tasks are executed only if the condition associated with them evaluates to true.

Link copied to clipboard

The policy dictating the execution of the next set of tasks for the current task.

Link copied to clipboard

The customized parameters the user can pass to this task.

Link copied to clipboard

Optional. Informs the front-end application where to draw this task config on the UI.

Link copied to clipboard

Optional. Standard filter expression evaluated before execution. Independent of other conditions and tasks. Can be used to enable rollout. e.g. "rollout(5)" will only allow 5% of incoming traffic to task.

Link copied to clipboard

Optional. User-provided label that is attached to precondition in the UI.

Link copied to clipboard

Optional. Contains information about what needs to be done upon failure (either a permanent error or after it has been retried too many times).

Link copied to clipboard

Determines what action to take upon successful task completion.

Link copied to clipboard

Optional. Determines the number of times the task will be retried on failure and with what retry strategy. This is applicable for synchronous calls to Eventbus alone (Post).

Link copied to clipboard

Copy of the task entity that this task config is an instance of.

Link copied to clipboard

The policy dictating the execution strategy of this task.

Link copied to clipboard

The name for the task.

Link copied to clipboard

REQUIRED: the identifier of this task within its parent event config, specified by the client. This should be unique among all the tasks belong to the same event config. We use this field as the identifier to find next tasks (via field next_tasks.task_number).

Link copied to clipboard

A string template that allows user to configure task parameters (with either literal default values or tokens which will be resolved at execution time) for the task. It will eventually replace the old "parameters" field.

Link copied to clipboard

Used to define task-template name if task is of type task-template

Link copied to clipboard

Defines the type of the task