start_engagement_from_opportunity_task
async
¶
start_engagement_from_opportunity_task(
catalog: CatalogIdentifier,
client_token: ClientToken,
identifier: OpportunityIdentifier,
aws_submission: AwsSubmission,
*,
config_overrides: Optional[AsyncPartnerCentralSellingClientConfig] = None,
tags: Optional[TagList] = None,
) -> StartEngagementFromOpportunityTaskResponse
Similar to StartEngagementByAcceptingInvitationTask, this action is asynchronous and performs multiple steps before completion. This action orchestrates a comprehensive workflow that combines multiple API operations into a single task to create and initiate an engagement from an existing opportunity. It automatically executes a sequence of operations including GetOpportunity, CreateEngagement (if it doesn't exist), CreateResourceSnapshot, CreateResourceSnapshotJob, CreateEngagementInvitation (if not already invited/accepted), and SubmitOpportunity.
Parameters:
-
catalog(CatalogIdentifier) –Specifies the catalog in which the engagement is tracked. Acceptable values include
AWSfor production andSandboxfor testing environments. -
client_token(ClientToken) –A unique token provided by the client to help ensure the idempotency of the request. It helps prevent the same task from being performed multiple times.
-
identifier(OpportunityIdentifier) –The unique identifier of the opportunity from which the engagement task is to be initiated. This helps ensure that the task is applied to the correct opportunity.
-
tags(Optional[TagList], default:None) –A map of the key-value pairs of the tag or tags to assign.
Raises:
-
AccessDeniedException–This error occurs when you don't have permission to perform the requested action.
You don’t have access to this action or resource. Review IAM policies or contact your AWS administrator for assistance.
-
ConflictException–This error occurs when the request can’t be processed due to a conflict with the target resource's current state, which could result from updating or deleting the resource.
Suggested action: Fetch the latest state of the resource, verify the state, and retry the request.
-
InternalServerException–This error occurs when the specified resource can’t be found or doesn't exist. Resource ID and type might be incorrect.
Suggested action: This is usually a transient error. Retry after the provided retry delay or a short interval. If the problem persists, contact AWS support.
-
ResourceNotFoundException–This error occurs when the specified resource can't be found. The resource might not exist, or isn't visible with the current credentials.
Suggested action: Verify that the resource ID is correct and the resource is in the expected AWS region. Check IAM permissions for accessing the resource.
-
ServiceQuotaExceededException–This error occurs when the request would cause a service quota to be exceeded. Service quotas represent the maximum allowed use of a specific resource, and this error indicates that the request would surpass that limit.
Suggested action: Review the Quotas for the resource, and either reduce usage or request a quota increase.
-
ThrottlingException–This error occurs when there are too many requests sent. Review the provided quotas and adapt your usage to avoid throttling.
This error occurs when there are too many requests sent. Review the provided Quotas and retry after the provided delay.
-
ValidationException–The input fails to satisfy the constraints specified by the service or business validation rules.
Suggested action: Review the error message, including the failed fields and reasons, to correct the request payload.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_partnercentral_selling/_services/async_partner_central_selling.py
1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 | |