Question

Difficulty: HardWorkflow Rules and Actions

An administrator is configuring automated processes on the Opportunity object to streamline sales operations. The leadership team requires immediate data synchronization, notifications, and integration with an external ERP system whenever an Opportunity reaches the 'Negotiation/Review' stage. Which TWO capabilities are natively available when using standard Workflow Actions to fulfill these requirements?

  1. Workflow Field Updates can modify fields on the triggering Opportunity record as well as fields on its parent Account record.Answer
  2. Workflow Outbound Messages can transmit designated field data in a SOAP-formatted XML message to a specified external endpoint without writing code.Answer
  3. C
    Workflow Tasks can automatically assign follow-up action items directly to a shared Case Queue or Lead Queue to distribute workload.
  4. D
    Time-dependent workflow actions can be configured on rules where the evaluation criteria is set to 'created, and every time it's edited'.

Answer

The correct capabilities are modifying parent Account fields via cross-object field updates from Opportunities, and sending SOAP-formatted XML notifications to an external system using Outbound Messages.
Workflow Rules support cross-object field updates from child objects (such as Opportunity) to parent objects (such as Account). Additionally, Outbound Messages natively transmit XML SOAP messages containing record fields to an external endpoint without requiring custom code.

Step-by-Step Solution

1
Evaluate cross-object capabilities of Workflow Field Updates.
Confirmed that Opportunity (child) can update fields on its parent Account object via standard cross-object field updates.
Salesforce permits cross-object field updates from specific standard/custom child objects up to their parent object.
2
Evaluate integration capabilities of Outbound Messages.
Confirmed that Outbound Messages send structured SOAP XML payloads declaratively to external HTTP/HTTPS listeners.
Outbound messaging is one of the four native workflow actions specifically designed for declarative API notifications.
3
Verify target assignment limitations for Workflow Tasks.
Identified that queues are invalid targets for Workflow Tasks.
Tasks require a single user assignment (e.g., user, record owner, role) and do not support queue assignments.
4
Check evaluation criteria restrictions for time-dependent actions.
Identified that 'created, and every time it's edited' invalidates time triggers.
To prevent infinite time-trigger loops on subsequent updates, Salesforce restricts time-dependent actions to specific evaluation criteria.

Key Concept

Workflow Action Capabilities and Restrictions
Rate this question