Scoping Actions Overview

A scoping action is an automation that runs when a specific response is selected on a scoping requirement. Scoping actions are triggered when an estimate has been made from the associated scoping session. The following scoping actions are available:

Set Field Value

Administrators define a value to be set on a specific field for each of the specified target records.

Example:
  • Task: The name of the estimate product must be updated to reflect the complexity.
  • Requirement: What is the complexity of the Services Estimator Implementation estimate product?
  • Response: Low
  • Action Type: Set Field Value
  • Target Object: Estimate Product Instance
  • Target Field: Name
  • Field Value: Services Estimator Implementation - Low Complexity
  • Outcome: The Services Estimator Implementation estimate product is renamed based on the complexity of the product.

Modify Field Value

Only used on numerical fields. Administrators specify a value and operator to adjust the value on the field being modified.

Example:

Task: The number of hours for all role requests needs updating based on the amount of users.

Requirement: How many users are there?

Response: 500+

Action Type: Modify Field Value

Target Object: Estimate Role Request

Target Field: Hours

Operator: Multiply

Field Value: 1.25

Outcome: The hours for each role request are multiplied by 1.25 if there are 500+ users.

Delete Record

Deletes the records, including child records, that match the filter criteria.

Example:

Task: Remove a task from the estimate product if it is out of scope.

Requirement: Is Data Migration in scope for this estimate product?

Response: No.

Action Type: Delete Record

Target Object: Estimate Line Set

Field: Line Set Name

Operator: Equals

Value: Data Migration

Outcome: The Data Migration task is deleted if it is out of scope on the estimate product.

Run Flow

Runs an active autolaunched flow. By default, only active autolaunched flows containing the string Guided Scoping in their description are displayed. To customize the flows displayed, you can update the string value in the Guided Scoping Flow Identifier field in the Services Estimator Settings custom setting. For more information about flow types, see the Salesforce Help.

Example:

Task: A review task needs to be created if a non-standard discount is required on this estimate product.

Requirement: Does this estimate product require a discount exceeding 15%?

Response: Yes.

Action Type: Run Flow

Flow: Create Review Task Flow

Outcome: The Create Review Task Flow is ran because there is a discount over 15% on the estimate product.

Set Input as Value

Only used on custom responses. This action takes the value the user enters during the scoping session and directly maps it to the target field of relevant target object records on the estimate.

  • URL
  • BOOLEAN
  • REFERENCE
  • PICKLIST
  • STRING
  • TEXTAREA
  • DOUBLE
  • CURRENCY
  • PERCENT
  • EMAIL
  • PHONE

The type of data input displayed in the scoping session is dependent on the selected target object and fields.

Example:

Task: The estimator is required to input the Upfront Bill amount for the estimate product during the scoping session.

Requirement: What is the Upfront Billing (%) for this fixed price estimate product?

Response: Use Integers Only.

Target Object: Estimate Product Instance

Target Field: Fixed Price Upfront Billing (%)

Outcome: The estimator sets the upfront bill amount for the fixed price estimate product.

Scoping Action Conditions

Scoping action conditions can be configured to have conditions, enabling you to filter the affected records. An administrator can configure these conditions by specifying a field, operator, and a value. This enables scoping actions to affect only the required records.