The ocid of the compartment that contains the work request. Work requests should be scoped to the same compartment as the resource the work request affects. If the work request affects multiple resources, and those resources are not in the same compartment, it is up to the service team to pick the primary resource whose compartment should be used.
The id of the work request.
The work request's operation type.
Percentage of the request completed. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The resources affected by this work request.
Status of current work request.
The date and time the request was created. The format is defined by RFC3339, such as {@code 2016-08-25T21:10:29.600Z}.
The date and time the request was finished. The format is defined by RFC3339, such as {@code 2016-08-25T21:10:29.600Z}.
The date and time the request was started. The format is defined by RFC3339, such as {@code 2016-08-25T21:10:29.600Z}.
The API operations that create and configure GoldenGate resources do not take effect immediately. In these cases, the operation spawns an asynchronous workflow to fulfill the request. Work requests provide visibility into the status of these in-progress, long-running asynchronous workflows.