Tasks Reference¶

activate_flow¶

Description: Activates Flows identified by a given list of Developer Names

Class: cumulusci.tasks.salesforce.activate_flow.ActivateFlow

Command Syntax¶

$ cci task run activate_flow

Options¶

--developer_names DEVELOPERNAMES

Required

List of DeveloperNames to query in SOQL

add_page_layout_fields¶

Description: Adds specified Fields or Visualforce Pages to a Page Layout.

Class: cumulusci.tasks.metadata_etl.layouts.AddFieldsToPageLayout

Inserts the listed fields or Visualforce pages into page layouts specified by API name.

If the targeted item already exists, the layout metadata is not modified.

You may supply a single position option, or multiple options for both pages and fields. The first option to to be matched will be used.

Task option details:

fields:
- api_name: [field API name]
- required: Boolean (default False)
- read_only: Boolean (default False, not compatible with required)
- position: (Optional: A list of single or multiple position options.)
  relative: [before | after | top | bottom]
  
  field: [api_name] (Use with relative: before, after)
  
  section: [index] (Use with relative: top, bottom)
  
  column: [first | last] (Use with relative: top, bottom)
pages:
- api_name: [Visualforce Page API name]
- height: int (Optional. Default: 200)
- show_label: Boolean (Optional. Default: False)
- show_scrollbars: Boolean (Optional. Default: False)
- width: 0-100% (Optional. Default: 100%)
- position: (Optional: A list of single or multiple position options.)
  relative: [before | after | top | bottom]
  
  field: [api_name] (Use with relative: before, after)
  
  section: [index] (Use with relative: top, bottom)
  
  column: [first | last] (Use with relative: top, bottom)

Command Syntax¶

$ cci task run add_page_layout_fields

Options¶

--fields FIELDS

Optional

List of fields. See task info for structure.

--pages PAGES

Optional

List of Visualforce Pages. See task info for structure.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

add_standard_value_set_entries¶

Description: Adds specified picklist entries to a Standard Value Set.

Class: cumulusci.tasks.metadata_etl.AddValueSetEntries

Command Syntax¶

$ cci task run add_standard_value_set_entries

Options¶

--api_names APINAMES

Required

List of API names of StandardValueSets to affect, such as ‘OpportunityStage’, ‘AccountType’, ‘CaseStatus’, ‘LeadStatus’

--entries ENTRIES

Required

Array of standardValues to insert. Each standardValue should contain the keys ‘fullName’, the API name of the entry, and ‘label’, the user-facing label. OpportunityStage entries require the additional keys ‘closed’, ‘won’, ‘forecastCategory’, and ‘probability’; CaseStatus entries require ‘closed’; LeadStatus entries require ‘converted’.

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

add_picklist_entries¶

Description: Adds specified picklist entries to a custom picklist field.

Class: cumulusci.tasks.metadata_etl.picklists.AddPicklistEntries

Command Syntax¶

$ cci task run add_picklist_entries

Options¶

--picklists PICKLISTS

Required

List of picklists to affect, in Object__c.Field__c form.

--entries ENTRIES

Required

Array of picklist values to insert. Each value should contain the keys ‘fullName’, the API name of the entry, and ‘label’, the user-facing label. Optionally, specify default: True on exactly one entry to make that value the default. Any existing values will not be affected other than setting the default (labels of existing entries are not changed). To order values, include the ‘add_before’ key. This will insert the new value before the existing value with the given API name, or at the end of the list if not present.

--record_types RECORDTYPES

Optional

List of Record Type developer names for which the new values should be available. If any of the entries have default: True, they are also made default for these Record Types. Any Record Types not present in the target org will be ignored, and * is a wildcard. Default behavior is to do nothing.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

add_fields_to_field_set¶

Description: Adds specified fields to a given field set.

Class: cumulusci.tasks.metadata_etl.field_sets.AddFieldsToFieldSet

Command Syntax¶

$ cci task run add_fields_to_field_set

Options¶

--field_set FIELDSET

Required

Name of field set to affect, in Object__c.FieldSetName form.

--fields FIELDS

Required

Array of field API names to add to the field set. Can include related fields using AccountId.Name or Lookup__r.CustomField__c style syntax.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

add_permission_set_perms¶

Description: Adds specified Apex class access and Field-Level Security to a Permission Set.

Class: cumulusci.tasks.metadata_etl.AddPermissionSetPermissions

Command Syntax¶

$ cci task run add_permission_set_perms

Options¶

--field_permissions FIELDPERMISSIONS

Optional

Array of fieldPermissions objects to upsert into permission_set. Each fieldPermission requires the following attributes: ‘field’: API Name of the field including namespace; ‘readable’: boolean if field can be read; ‘editable’: boolean if field can be edited

--class_accesses CLASSACCESSES

Optional

Array of classAccesses objects to upsert into permission_set. Each classAccess requires the following attributes: ‘apexClass’: Name of Apex Class. If namespaced, make sure to use the form “namespace__ApexClass”; ‘enabled’: boolean if the Apex Class can be accessed.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

add_record_action_list_item¶

Description: Adds the specified ‘Record’ context Lightning button/action to the provided page layout.

Class: cumulusci.tasks.metadata_etl.layouts.AddRecordPlatformActionListItem

Inserts the targeted lightning button/action into specified layout’s PlatformActionList with a ‘Record’ actionListContext. - If the targeted lightning button/action already exists,

the layout metadata is not modified.

If there is no ‘Record’ context PlatformActionList,
we will generate one and add the specified action

Task definition example:

dev_inject_apply_quick_action_into_account_layout: group: “Demo config and storytelling” description: Adds an Apply Quick Action button to the beggining of the button list on the Experiences Account Layout. class_path: tasks.layouts.InsertRecordPlatformActionListItem options:

api_names: “Account-%%%NAMESPACE%%%Experiences Account Layout” action_name: “Account.Apply” action_type: QuickAction place_first: True

Reference Documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_layouts.htm#PlatformActionList

Command Syntax¶

$ cci task run add_record_action_list_item

Options¶

--action_type ACTIONTYPE

Required

platformActionListItems.actionType like ‘QuickAction’ or ‘CustomButton’

--action_name ACTIONNAME

Required

platformActionListItems.actionName. The API name for the action to be added.

--place_first PLACEFIRST

Optional

When ‘True’ the specified Record platformActionListItem will be inserted before any existing on the layout. Default is ‘False’

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

assign_compact_layout¶

Description: Assigns the Compact Layout specified in the ‘value’ option to the Custom Objects in ‘api_names’ option.

Class: cumulusci.tasks.metadata_etl.UpdateMetadataFirstChildTextTask

Metadata ETL task to update a single child element’s text within metadata XML.

If the child doesn’t exist, the child is created and appended to the Metadata. Furthermore, the value option is namespaced injected if the task is properly configured.

Example: Assign a Custom Object’s Compact Layout¶

Researching CustomObject in the Metadata API documentation or even retrieving the CustomObject’s Metadata for inspection, we see the compactLayoutAssignment Field. We want to assign a specific Compact Layout for our Custom Object, so we write the following CumulusCI task in our project’s cumulusci.yml.

tasks:
    assign_compact_layout:
        class_path: cumulusci.tasks.metadata_etl.UpdateMetadataFirstChildTextTask
        options:
            managed: False
            namespace_inject: $project_config.project__package__namespace
            entity: CustomObject
            api_names: OurCustomObject__c
            tag: compactLayoutAssignment
            value: "%%%NAMESPACE%%%DifferentCompactLayout"
            # We include a namespace token so it's easy to use this task in a managed context.

Suppose the original CustomObject metadata XML looks like:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
    ...
    <label>Our Custom Object</label>
    <compactLayoutAssignment>OriginalCompactLayout</compactLayoutAssignment>
    ...
</CustomObject>

After running cci task run assign_compact_layout, the CustomObject metadata XML is deployed as:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
    ...
    <label>Our Custom Object</label>
    <compactLayoutAssignment>DifferentCompactLayout</compactLayoutAssignment>
    ...
</CustomObject>

Command Syntax¶

$ cci task run assign_compact_layout

Options¶

--metadata_type METADATATYPE

Required

Metadata Type

Default: CustomObject

--tag TAG

Required

Targeted tag. The text of the first instance of this tag within the metadata entity will be updated.

Default: compactLayoutAssignment

--value VALUE

Required

Desired value to set for the targeted tag’s text. This value is namespace-injected.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

assign_permission_sets¶

Description: Assigns specified Permission Sets to the current user, if not already assigned.

Class: cumulusci.tasks.salesforce.users.permsets.AssignPermissionSets

Assigns Permission Sets whose Names are in api_names to either the default org user or the user whose Alias is user_alias. This task skips assigning Permission Sets that are already assigned.

Command Syntax¶

$ cci task run assign_permission_sets

Options¶

--api_names APINAMES

Required

API Names of desired Permission Sets, separated by commas.

--user_alias USERALIAS

Optional

Target user aliases, separated by commas. Defaults to the current running user.

assign_permission_set_groups¶

Description: Assigns specified Permission Set Groups to the current user, if not already assigned.

Class: cumulusci.tasks.salesforce.users.permsets.AssignPermissionSetGroups

Assigns Permission Set Groups whose Developer Names are in api_names to either the default org user or the user whose Alias is user_alias. This task skips assigning Permission Set Groups that are already assigned.

Command Syntax¶

$ cci task run assign_permission_set_groups

Options¶

--api_names APINAMES

Required

API Developer Names of desired Permission Set Groups, separated by commas.

--user_alias USERALIAS

Optional

Alias of target user (if not the current running user, the default).

assign_permission_set_licenses¶

Description: Assigns specified Permission Set Licenses to the current user, if not already assigned.

Class: cumulusci.tasks.salesforce.users.permsets.AssignPermissionSetLicenses

Assigns Permission Set Licenses whose Developer Names are in api_names to either the default org user or the user whose Alias is user_alias. This task skips assigning Permission Set Licenses that are already assigned.

Permission Set Licenses are usually associated with a Permission Set, and assigning the Permission Set usually assigns the associated Permission Set License automatically. However, in non-namespaced developer scratch orgs, assigning the associated Permission Set may not automatically assign the Permission Set License, and this task will ensure the Permission Set Licenses are assigned.

Command Syntax¶

$ cci task run assign_permission_set_licenses

Options¶

--api_names APINAMES

Required

API Developer Names of desired Permission Set Licenses, separated by commas.

--user_alias USERALIAS

Optional

Alias of target user (if not the current running user, the default).

batch_apex_wait¶

Description: Waits on a batch apex or queueable apex job to finish.

Class: cumulusci.tasks.apex.batch.BatchApexWait

Command Syntax¶

$ cci task run batch_apex_wait

Options¶

--class_name CLASSNAME

Required

Name of the Apex class to wait for.

--poll_interval POLLINTERVAL

Optional

Seconds to wait before polling for batch or queueable job completion. Defaults to 10 seconds.

check_my_domain_active¶

Description: Runs as a preflight check to determine whether My Domain is active.

Class: cumulusci.tasks.preflight.settings.CheckMyDomainActive

Command Syntax¶

$ cci task run check_my_domain_active

check_sobjects_available¶

Description: Runs as a preflight check to determine whether specific sObjects are available.

Class: cumulusci.tasks.preflight.sobjects.CheckSObjectsAvailable

As a MetaDeploy preflight check, validates that an sObject is present in the schema.

The task can be used as a preflight check thus:

3:
    task: insert_sobject_records
    checks:
        - when: "'ContentNote' not in tasks.check_sobjects_available()"
          action: error
          message: "Enhanced Notes are not turned on."

Command Syntax¶

$ cci task run check_sobjects_available

check_sobject_permissions¶

Description: Runs as a preflight check to determine whether specific sObjects are permissioned as desired (options are required).

Class: cumulusci.tasks.preflight.sobjects.CheckSObjectPerms

As a MetaDeploy preflight check, validates that an sObject’s permissions are in the expected state.

For example, specify:
check_sobject_permissions:
    options:
        Account:
            createable: True
            updateable: False
        Contact:
            createable: False
to validate that the Account object is createable but not updateable, and the Contact object is not createable. The output is True if all sObjects and permissions are present and matching the specification.

Given the above configuration, the task can be used as a preflight check in a MetaDeploy plan:
3:
    task: insert_sobject_records
    checks:
        - when: "not tasks.check_sobject_permissions()"
          action: error
          message: "sObject permissions are not configured correctly."

Command Syntax¶

$ cci task run check_sobject_permissions

Options¶

--permissions PERMISSIONS

Required

The object permissions to check. Each key should be an sObject API name, whose value is a map of describe keys, such as queryable and createable, to their desired values (True or False). The output is True if all sObjects and permissions are present and matching the specification. See the task documentation for examples.

check_advanced_currency_management¶

Description: Runs as a preflight check to determine whether Advanced Currency Management is active (True result means the feature is active).

Class: cumulusci.tasks.preflight.sobjects.CheckSObjectPerms

As a MetaDeploy preflight check, validates that an sObject’s permissions are in the expected state.

For example, specify:
check_sobject_permissions:
    options:
        Account:
            createable: True
            updateable: False
        Contact:
            createable: False
to validate that the Account object is createable but not updateable, and the Contact object is not createable. The output is True if all sObjects and permissions are present and matching the specification.

Given the above configuration, the task can be used as a preflight check in a MetaDeploy plan:
3:
    task: insert_sobject_records
    checks:
        - when: "not tasks.check_sobject_permissions()"
          action: error
          message: "sObject permissions are not configured correctly."

Command Syntax¶

$ cci task run check_advanced_currency_management

Options¶

--permissions PERMISSIONS

Required

Default: {‘DatedConversionRate’: {‘createable’: True}}

check_org_wide_defaults¶

Description: Runs as a preflight check to validate Organization-Wide Defaults.

Class: cumulusci.tasks.preflight.sobjects.CheckSObjectOWDs

As a MetaDeploy preflight check, validates that an sObject’s Org-Wide Defaults are in the expected state.

For example, specify:

check_org_wide_defaults:
    options:
        org_wide_defaults:
            - api_name: Account
              internal_sharing_model: Private
              external_sharing_model: Private
            - api_name: Contact
              internal_sharing_model: Private

to validate that the Account object has Private internal and external OWDs, and Contact a Private internal model. The output is True if all sObjects and permissions are present and matching the specification.

Given the above configuration, the task can be used as a preflight check in a MetaDeploy plan:

3:
    task: insert_sobject_records
    checks:
        - when: "not tasks.check_org_wide_defaults()"
          action: error
          message: "Org-Wide Defaults are not configured correctly."

Command Syntax¶

$ cci task run check_org_wide_defaults

Options¶

--org_wide_defaults ORGWIDEDEFAULTS

Required

The Organization-Wide Defaults to check, organized as a list with each element containing the keys api_name, internal_sharing_model, and external_sharing_model. NOTE: you must have External Sharing Model turned on in Sharing Settings to use the latter feature. Checking External Sharing Model when it is turned off will fail the preflight.

check_org_settings_value¶

Description: Runs as a preflight check to validate organization settings.

Class: cumulusci.tasks.preflight.settings.CheckSettingsValue

Command Syntax¶

$ cci task run check_org_settings_value

Options¶

--settings_type SETTINGSTYPE

Required

The API name of the Settings entity to be checked, such as ChatterSettings.

--settings_field SETTINGSFIELD

Required

The API name of the field on the Settings entity to check.

--value VALUE

Required

The value to check for

--treat_missing_as_failure TREATMISSINGASFAILURE

Optional

If True, treat a missing Settings entity as a preflight failure, instead of raising an exception. Defaults to False.

check_chatter_enabled¶

Description: Runs as a preflight check to validate Chatter is enabled.

Class: cumulusci.tasks.preflight.settings.CheckSettingsValue

Command Syntax¶

$ cci task run check_chatter_enabled

Options¶

--settings_type SETTINGSTYPE

Required

The API name of the Settings entity to be checked, such as ChatterSettings.

Default: ChatterSettings

--settings_field SETTINGSFIELD

Required

The API name of the field on the Settings entity to check.

Default: IsChatterEnabled

--value VALUE

Required

The value to check for

Default: True

--treat_missing_as_failure TREATMISSINGASFAILURE

Optional

If True, treat a missing Settings entity as a preflight failure, instead of raising an exception. Defaults to False.

check_enhanced_notes_enabled¶

Description: Preflight check to validate that Enhanced Notes are enabled.

Class: cumulusci.tasks.preflight.settings.CheckSettingsValue

Command Syntax¶

$ cci task run check_enhanced_notes_enabled

Options¶

--settings_type SETTINGSTYPE

Required

The API name of the Settings entity to be checked, such as ChatterSettings.

Default: EnhancedNotesSettings

--settings_field SETTINGSFIELD

Required

The API name of the field on the Settings entity to check.

Default: IsEnhancedNotesEnabled

--value VALUE

Required

The value to check for

Default: True

--treat_missing_as_failure TREATMISSINGASFAILURE

Optional

If True, treat a missing Settings entity as a preflight failure, instead of raising an exception. Defaults to False.

custom_settings_value_wait¶

Description: Waits for a specific field value on the specified custom settings object and field

Class: cumulusci.tasks.salesforce.custom_settings_wait.CustomSettingValueWait

Command Syntax¶

$ cci task run custom_settings_value_wait

Options¶

--object OBJECT

Required

Name of the Hierarchical Custom Settings object to query. Can include the %%%NAMESPACE%%% token.

--field FIELD

Required

Name of the field on the Custom Settings to query. Can include the %%%NAMESPACE%%% token.

--value VALUE

Required

Value of the field to wait for (String, Integer or Boolean).

--managed MANAGED

Optional

If True, will insert the project’s namespace prefix. Defaults to False or no namespace.

--namespaced NAMESPACED

Optional

If True, the %%%NAMESPACE%%% token will get replaced with the namespace prefix for the object and field.Defaults to False.

--poll_interval POLLINTERVAL

Optional

Seconds to wait before polling for batch job completion. Defaults to 10 seconds.

command¶

Description: Run an arbitrary command

Class: cumulusci.tasks.command.Command

Example Command-line Usage: cci task run command -o command "echo 'Hello command task!'"

Example Task to Run Command:

hello_world:
    description: Says hello world
    class_path: cumulusci.tasks.command.Command
    options:
        command: echo 'Hello World!'

Command Syntax¶

$ cci task run command

Options¶

--command COMMAND

Required

The command to execute

--pass_env PASSENV

Required

If False, the current environment variables will not be passed to the child process. Defaults to True

--dir DIR

Optional

If provided, the directory where the command should be run from.

--env ENV

Optional

Environment variables to set for command. Must be flat dict, either as python dict from YAML or as JSON string.

--interactive INTERACTIVE

Optional

If True, the command will use stderr, stdout, and stdin of the main process.Defaults to False.

composite_request¶

Description: Execute a series of REST API requests in a single call

Class: cumulusci.tasks.salesforce.composite.CompositeApi

This task is a wrapper for Composite REST API calls. Given a list of JSON files (one request body per file), POST each and process the returned composite result. Files are processed in the order given by the data_files option.

In addition, this task will process the request body and replace namespace (%%%NAMESPACE%%%) and user ID (%%%USERID%%%) tokens. To avoid username collisions, use the randomize_username option to replace the top-level domains in any Username field with a random string.

When the top-level allOrNone property for the request is set to true a SalesforceException is raised if an error is returned for any subrequest, otherwise partial successes will not raise an exception.

Example Task Definition¶

tasks:
    example_composite_request:
        class_path: cumulusci.tasks.salesforce.composite.CompositeApi
        options:
           data_files:
               - "datasets/composite/users.json"
               - "datasets/composite/setup_objects.json"

Command Syntax¶

$ cci task run composite_request

Options¶

--data_files DATAFILES

Required

A list of paths, where each path is a JSON file containing a composite request body.

--managed MANAGED

Optional

If True, replaces namespace tokens with the namespace prefix.

--namespaced NAMESPACED

Optional

If True, replaces namespace tokens with the namespace prefix.

--randomize_username RANDOMIZEUSERNAME

Optional

If True, randomize the TLD for any ‘Username’ fields.

create_community¶

Description: Creates a Community in the target org using the Connect API

Class: cumulusci.tasks.salesforce.CreateCommunity

Create a Salesforce Community via the Connect API.

Specify the template “VF Template” for Visualforce Tabs community, or the name for a specific desired template

Command Syntax¶

$ cci task run create_community

Options¶

--template TEMPLATE

Required

Name of the template for the community.

--name NAME

Required

Name of the community.

--description DESCRIPTION

Optional

Description of the community.

--url_path_prefix URLPATHPREFIX

Optional

URL prefix for the community.

--retries RETRIES

Optional

Number of times to retry community creation request

--timeout TIMEOUT

Optional

Time to wait, in seconds, for the community to be created

--skip_existing SKIPEXISTING

Optional

If True, an existing community with the same name will not raise an exception.

connected_app¶

Description: Creates the Connected App needed to use persistent orgs in the CumulusCI keychain

Class: cumulusci.tasks.connectedapp.CreateConnectedApp

Command Syntax¶

$ cci task run connected_app

Options¶

--label LABEL

Required

The label for the connected app. Must contain only alphanumeric and underscores

Default: CumulusCI

--email EMAIL

Optional

The email address to associate with the connected app. Defaults to email address from the github service if configured.

--username USERNAME

Optional

Create the connected app in a different org. Defaults to the defaultdevhubusername configured in sfdx.

--connect CONNECT

Optional

If True, the created connected app will be stored as the CumulusCI connected_app service in the keychain.

Default: True

--overwrite OVERWRITE

Optional

If True, any existing connected_app service in the CumulusCI keychain will be overwritten. Has no effect if the connect option is False.

create_network_member_groups¶

Description: Creates NetworkMemberGroup records which grant access to an Experience Site (Community) for specified Profiles or Permission Sets

Class: cumulusci.tasks.salesforce.network_member_group.CreateNetworkMemberGroups

Command Syntax¶

$ cci task run create_network_member_groups

Options¶

--network_name NETWORKNAME

Required

Name of Network to add NetworkMemberGroup children records.

--profile_names PROFILENAMES

Optional

List of Profile Names to add as NetworkMemberGroups for this Network.

--permission_set_names PERMISSIONSETNAMES

Optional

List of PermissionSet Names to add as NetworkMemberGroups for this Network.

insert_record¶

Description: Inserts a record of any sObject using the REST API

Class: cumulusci.tasks.salesforce.insert_record.InsertRecord

For example:

cci task run insert_record –org dev -o object PermissionSet -o values Name:HardDelete,PermissionsBulkApiHardDelete:true

Command Syntax¶

$ cci task run insert_record

Options¶

--object OBJECT

Required

An sObject type to insert

--values VALUES

Required

Field names and values in the format ‘aa:bb,cc:dd’, or a YAML dict in cumulusci.yml.

--tooling TOOLING

Optional

If True, use the Tooling API instead of REST API.

create_package¶

Description: Creates a package in the target org with the default package name for the project

Class: cumulusci.tasks.salesforce.CreatePackage

Command Syntax¶

$ cci task run create_package

Options¶

--package PACKAGE

Required

The name of the package to create. Defaults to project__package__name

--api_version APIVERSION

Required

The api version to use when creating the package. Defaults to project__package__api_version

create_package_version¶

Description: Uploads a 2nd-generation package (2GP) version

Class: cumulusci.tasks.create_package_version.CreatePackageVersion

Command Syntax¶

$ cci task run create_package_version

Options¶

--package_type PACKAGETYPE

Required

Package type (Unlocked or Managed)

--package_name PACKAGENAME

Optional

Name of package

--namespace NAMESPACE

Optional

Package namespace

--version_name VERSIONNAME

Optional

Version name

--version_base VERSIONBASE

Optional

The version number to use as a base before incrementing. Optional; defaults to the highest existing version number of this package. Can be set to latest_github_release to use the version of the most recent release published to GitHub.

--version_type VERSIONTYPE

Optional

The part of the version number to increment. Options are major, minor, patch, build. Defaults to build

--skip_validation SKIPVALIDATION

Optional

If true, skip validation of the package version. Default: false. Skipping validation creates packages more quickly, but they cannot be promoted for release.

--org_dependent ORGDEPENDENT

Optional

If true, create an org-dependent unlocked package. Default: false.

--post_install_script POSTINSTALLSCRIPT

Optional

Post-install script (for managed packages)

--uninstall_script UNINSTALLSCRIPT

Optional

Uninstall script (for managed packages)

--force_upload FORCEUPLOAD

Optional

If true, force creating a new package version even if one with the same contents already exists

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--ancestor_id ANCESTORID

Optional

The 04t Id to use for the ancestor of this package. Optional; defaults to no ancestor specified. Can be set to latest_github_release to use the most recent production version published to GitHub.

--resolution_strategy RESOLUTIONSTRATEGY

Optional

The name of a sequence of resolution_strategy (from project__dependency_resolutions) to apply to dynamic dependencies. Defaults to ‘production’.

--create_unlocked_dependency_packages CREATEUNLOCKEDDEPENDENCYPACKAGES

Optional

If True, create unlocked packages for unpackaged metadata in this project and dependencies. Defaults to False.

create_managed_src¶

Description: Modifies the src directory for managed deployment. Strips //cumulusci-managed from all Apex code

Class: cumulusci.tasks.metadata.managed_src.CreateManagedSrc

Apex classes which use the @deprecated annotation can comment it out using //cumulusci-managed so that it can be deployed as part of unmanaged metadata, where this annotation is not allowed. This task is for use when deploying to a packaging org to remove the comment so that the annotation takes effect.

Command Syntax¶

$ cci task run create_managed_src

Options¶

--path PATH

Required

The path containing metadata to process for managed deployment

Default: src

--revert_path REVERTPATH

Required

The path to copy the original metadata to for the revert call

Default: src.orig

create_permission_set¶

Description: Creates a Permission Set with specified User Permissions and assigns it to the running user.

Class: cumulusci.tasks.salesforce.create_permission_sets.CreatePermissionSet

Command Syntax¶

$ cci task run create_permission_set

Options¶

--api_name APINAME

Required

API name of generated Permission Set

--user_permissions USERPERMISSIONS

Required

List of User Permissions to include in the Permission Set.

--label LABEL

Optional

Label of generated Permission Set

create_bulk_data_permission_set¶

Description: Creates a Permission Set with the Hard Delete and Set Audit Fields user permissions. NOTE: the org setting to allow Set Audit Fields must be turned on.

Class: cumulusci.tasks.salesforce.create_permission_sets.CreatePermissionSet

Command Syntax¶

$ cci task run create_bulk_data_permission_set

Options¶

--api_name APINAME

Required

API name of generated Permission Set

Default: CumulusCI_Bulk_Data

--user_permissions USERPERMISSIONS

Required

List of User Permissions to include in the Permission Set.

Default: [‘PermissionsBulkApiHardDelete’, ‘PermissionsCreateAuditFields’]

--label LABEL

Optional

Label of generated Permission Set

Default: CumulusCI Bulk Data

create_unmanaged_ee_src¶

Description: Modifies the src directory for unmanaged deployment to an EE org

Class: cumulusci.tasks.metadata.ee_src.CreateUnmanagedEESrc

Command Syntax¶

$ cci task run create_unmanaged_ee_src

Options¶

--path PATH

Required

The path containing metadata to process for managed deployment

Default: src

--revert_path REVERTPATH

Required

The path to copy the original metadata to for the revert call

Default: src.orig

create_blank_profile¶

Description: Creates a blank profile, or a profile with no permissions

Class: cumulusci.tasks.salesforce.profiles.CreateBlankProfile

Command Syntax¶

$ cci task run create_blank_profile

Options¶

--name NAME

Required

The name of the the new profile

--license LICENSE

Optional

The name of the salesforce license to use in the profile, defaults to ‘Salesforce’

Default: Salesforce

--license_id LICENSEID

Optional

The ID of the salesforce license to use in the profile.

--description DESCRIPTION

Optional

The description of the the new profile

delete_data¶

Description: Query existing data for a specific sObject and perform a Bulk API delete of all matching records.

Class: cumulusci.tasks.bulkdata.DeleteData

Command Syntax¶

$ cci task run delete_data

Options¶

--objects OBJECTS

Required

A list of objects to delete records from in order of deletion. If passed via command line, use a comma separated string

--where WHERE

Optional

A SOQL where-clause (without the keyword WHERE). Only available when ‘objects’ is length 1.

--hardDelete HARDDELETE

Optional

If True, perform a hard delete, bypassing the Recycle Bin. Note that this requires the Bulk API Hard Delete permission. Default: False

--ignore_row_errors IGNOREROWERRORS

Optional

If True, allow the operation to continue even if individual rows fail to delete.

--inject_namespaces INJECTNAMESPACES

Optional

If True, the package namespace prefix will be automatically added to (or removed from) objects and fields based on the name used in the org. Defaults to True.

--api API

Optional

The desired Salesforce API to use, which may be ‘rest’, ‘bulk’, or ‘smart’ to auto-select based on record volume. The default is ‘smart’.

deploy¶

Description: Deploys the src directory of the repository to the org

Class: cumulusci.tasks.salesforce.Deploy

Command Syntax¶

$ cci task run deploy

Options¶

--path PATH

Required

The path to the metadata source to be deployed

Default: src

--unmanaged UNMANAGED

Optional

If True, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--check_only CHECKONLY

Optional

If True, performs a test deployment (validation) of components without saving the components in the target org

--test_level TESTLEVEL

Optional

Specifies which tests are run as part of a deployment. Valid values: NoTestRun, RunLocalTests, RunAllTestsInOrg, RunSpecifiedTests.

--specified_tests SPECIFIEDTESTS

Optional

Comma-separated list of test classes to run upon deployment. Applies only with test_level set to RunSpecifiedTests.

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--namespaced_org NAMESPACEDORG

Optional

If True, the tokens %%%NAMESPACED_ORG%%% and ___NAMESPACED_ORG___ will get replaced with the namespace. The default is false causing those tokens to get stripped and replaced with an empty string. Set this if deploying to a namespaced scratch org or packaging org.

--clean_meta_xml CLEANMETAXML

Optional

Defaults to True which strips the <packageVersions/> element from all meta.xml files. The packageVersion element gets added automatically by the target org and is set to whatever version is installed in the org. To disable this, set this option to False

deploy_marketing_cloud_package¶

Description: Deploys a package zip file to a Marketing Cloud Tenant via the Marketing Cloud Package Manager API.

Class: cumulusci.tasks.marketing_cloud.deploy.MarketingCloudDeployTask

Command Syntax¶

$ cci task run deploy_marketing_cloud_package

Options¶

--package_zip_file PACKAGEZIPFILE

Required

Path to the package zipfile that will be deployed.

--custom_inputs CUSTOMINPUTS

Optional

Specify custom inputs to the deployment task. Takes a mapping from input key to input value (e.g. ‘companyName:Acme,companyWebsite:https://www.salesforce.org:8080’).

--name NAME

Optional

The name to give to this particular deploy call. Defaults to a universally unique identifier.

--endpoint ENDPOINT

Optional

Override the default endpoint for the Marketing Cloud package manager API (optional)

marketing_cloud_create_subscriber_attribute¶

Description: Creates a Subscriber Attribute via the Marketing Cloud SOAP API.

Class: cumulusci.tasks.marketing_cloud.api.CreateSubscriberAttribute

Command Syntax¶

$ cci task run marketing_cloud_create_subscriber_attribute

Options¶

--attribute_name ATTRIBUTENAME

Required

The name of the Subscriber Attribute to deploy via the Marketing Cloud API.

marketing_cloud_create_user¶

Description: Creates a new User via the Marketing Cloud SOAP API.

Class: cumulusci.tasks.marketing_cloud.api.CreateUser

Command Syntax¶

$ cci task run marketing_cloud_create_user

Options¶

--parent_bu_mid PARENTBUMID

Required

Specify the MID for Parent BU.

--default_bu_mid DEFAULTBUMID

Required

Set MID for BU to use as default (can be same as the parent).

--user_email USEREMAIL

Required

Set the User’s email.

--user_password USERPASSWORD

Required

Set the User’s password.

--user_username USERUSERNAME

Required

Set the User’s username. Not the same as their name.

--external_key EXTERNALKEY

Optional

Set the User’s external key.

--user_name USERNAME

Optional

Set the User’s name. Not the same as their username.

--role_id ROLEID

Optional

Assign a Role to the new User, specified as an ID. IDs for system defined roles located here: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/setting_user_permissions_via_the_web_services_api.htm

marketing_cloud_update_user_role¶

Description: Assigns a Role to an existing User via the Marketing Cloud SOAP API.

Class: cumulusci.tasks.marketing_cloud.api.UpdateUserRole

Command Syntax¶

$ cci task run marketing_cloud_update_user_role

Options¶

--account_mid ACCOUNTMID

Required

Specify the Account MID.

--user_email USEREMAIL

Required

Specify the User’s email.

--user_password USERPASSWORD

Required

Specify the User’s password.

--role_id ROLEID

Required

Assign a Role to the User, specified as an ID. IDs for system defined roles located here: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/setting_user_permissions_via_the_web_services_api.htm

--external_key EXTERNALKEY

Optional

Specify the User’s external key.

--user_name USERNAME

Optional

Specify the User’s name. Not the same as their username.

deploy_pre¶

Description: Deploys all metadata bundles under unpackaged/pre/

Class: cumulusci.tasks.salesforce.DeployBundles

Command Syntax¶

$ cci task run deploy_pre

Options¶

--path PATH

Required

The path to the parent directory containing the metadata bundles directories

Default: unpackaged/pre

--unmanaged UNMANAGED

Optional

If True, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--check_only CHECKONLY

Optional

If True, performs a test deployment (validation) of components without saving the components in the target org

--test_level TESTLEVEL

Optional

Specifies which tests are run as part of a deployment. Valid values: NoTestRun, RunLocalTests, RunAllTestsInOrg, RunSpecifiedTests.

--specified_tests SPECIFIEDTESTS

Optional

Comma-separated list of test classes to run upon deployment. Applies only with test_level set to RunSpecifiedTests.

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--namespaced_org NAMESPACEDORG

Optional

--clean_meta_xml CLEANMETAXML

Optional

deploy_post¶

Description: Deploys all metadata bundles under unpackaged/post/

Class: cumulusci.tasks.salesforce.DeployBundles

Command Syntax¶

$ cci task run deploy_post

Options¶

--path PATH

Required

The path to the parent directory containing the metadata bundles directories

Default: unpackaged/post

--unmanaged UNMANAGED

Optional

If True, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--check_only CHECKONLY

Optional

If True, performs a test deployment (validation) of components without saving the components in the target org

--test_level TESTLEVEL

Optional

Specifies which tests are run as part of a deployment. Valid values: NoTestRun, RunLocalTests, RunAllTestsInOrg, RunSpecifiedTests.

--specified_tests SPECIFIEDTESTS

Optional

Comma-separated list of test classes to run upon deployment. Applies only with test_level set to RunSpecifiedTests.

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--namespaced_org NAMESPACEDORG

Optional

--clean_meta_xml CLEANMETAXML

Optional

deploy_qa_config¶

Description: Deploys configuration for QA.

Class: cumulusci.tasks.salesforce.Deploy

Command Syntax¶

$ cci task run deploy_qa_config

Options¶

--path PATH

Required

The path to the metadata source to be deployed

Default: unpackaged/config/qa

--unmanaged UNMANAGED

Optional

If True, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--check_only CHECKONLY

Optional

If True, performs a test deployment (validation) of components without saving the components in the target org

--test_level TESTLEVEL

Optional

Specifies which tests are run as part of a deployment. Valid values: NoTestRun, RunLocalTests, RunAllTestsInOrg, RunSpecifiedTests.

--specified_tests SPECIFIEDTESTS

Optional

Comma-separated list of test classes to run upon deployment. Applies only with test_level set to RunSpecifiedTests.

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--namespaced_org NAMESPACEDORG

Optional

--clean_meta_xml CLEANMETAXML

Optional

dx¶

Description: Execute an arbitrary Salesforce DX command against an org. Use the ‘command’ option to specify the command, such as ‘force:package:install’

Class: cumulusci.tasks.sfdx.SFDXOrgTask

Command Syntax¶

$ cci task run dx

Options¶

Options¶

--api_names APINAMES

Required

List of API names of the MLPredictionDefinitions.

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespaced_org NAMESPACEDORG

Optional

If False, changes namespace_inject to replace namespaced-org tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

ensure_record_types¶

Description: Ensure that a default Record Type is extant on the given standard sObject (custom objects are not supported). If Record Types are already present, do nothing.

Class: cumulusci.tasks.salesforce.EnsureRecordTypes

Command Syntax¶

$ cci task run ensure_record_types

Options¶

--record_type_developer_name RECORDTYPEDEVELOPERNAME

Required

The Developer Name of the Record Type (unique). Must contain only alphanumeric characters and underscores.

Default: Default

--record_type_label RECORDTYPELABEL

Required

The Label of the Record Type.

Default: Default

--sobject SOBJECT

Required

The sObject on which to deploy the Record Type and optional Business Process.

--record_type_description RECORDTYPEDESCRIPTION

Optional

The Description of the Record Type. Only uses the first 255 characters.

--force_create FORCECREATE

Optional

If true, the Record Type will be created even if a default Record Type already exists on this sObject. Defaults to False.

execute_anon¶

Description: Execute anonymous apex via the tooling api.

Class: cumulusci.tasks.apex.anon.AnonymousApexTask

Use the apex option to run a string of anonymous Apex. Use the path option to run anonymous Apex from a file. Or use both to concatenate the string to the file contents.

Command Syntax¶

$ cci task run execute_anon

Options¶

--path PATH

Optional

The path to an Apex file to run.

--apex APEX

Optional

A string of Apex to run (after the file, if specified).

--managed MANAGED

Optional

If True, will insert the project’s namespace prefix. Defaults to False or no namespace.

--namespaced NAMESPACED

Optional

If True, the tokens %%%NAMESPACED_RT%%% and %%%namespaced%%% will get replaced with the namespace prefix for Record Types.

--param1 PARAM1

Optional

Parameter to pass to the Apex. Use as %%%PARAM_1%%% in the Apex code. Defaults to an empty value.

--param2 PARAM2

Optional

Parameter to pass to the Apex. Use as %%%PARAM_2%%% in the Apex code. Defaults to an empty value.

generate_data_dictionary¶

Description: Create a data dictionary for the project in CSV format.

Class: cumulusci.tasks.datadictionary.GenerateDataDictionary

Generate a data dictionary for the project by walking all GitHub releases. The data dictionary is output as two CSV files. One, in object_path, includes

Object Label
Object API Name
Object Description
Version Introduced

with one row per packaged object.

The other, in field_path, includes

Object Label
Object API Name
Field Label
Field API Name
Field Type
Valid Picklist Values
Help Text
Field Description
Version Introduced
Version Picklist Values Last Changed
Version Help Text Last Changed

Both MDAPI and SFDX format releases are supported.

Command Syntax¶

$ cci task run generate_data_dictionary

Options¶

--object_path OBJECTPATH

Optional

Path to a CSV file to contain an sObject-level data dictionary.

--field_path FIELDPATH

Optional

Path to a CSV file to contain an field-level data dictionary.

--include_dependencies INCLUDEDEPENDENCIES

Optional

Process all of the GitHub dependencies of this project and include their schema in the data dictionary.

--additional_dependencies ADDITIONALDEPENDENCIES

Optional

Include schema from additional GitHub repositories that are not explicit dependencies of this project to build a unified data dictionary. Specify as a list of dicts as in project__dependencies in cumulusci.yml. Note: only repository dependencies are supported.

--include_prerelease INCLUDEPRERELEASE

Optional

Treat the current branch as containing prerelease schema, and included it as Prerelease in the data dictionary. NOTE: this option cannot be used with additional_dependencies or include_dependencies.

--include_protected_schema INCLUDEPROTECTEDSCHEMA

Optional

Include Custom Objects, Custom Settings, and Custom Metadata Types that are marked as Protected. Defaults to False.

generate_and_load_from_yaml¶

Description: None

Class: cumulusci.tasks.bulkdata.generate_and_load_data_from_yaml.GenerateAndLoadDataFromYaml

Command Syntax¶

$ cci task run generate_and_load_from_yaml

Options¶

--data_generation_task DATAGENERATIONTASK

Required

Fully qualified class path of a task to generate the data. Look at cumulusci.tasks.bulkdata.tests.dummy_data_factory to learn how to write them.

--generator_yaml GENERATORYAML

Required

A Snowfakery recipe file to use

--num_records NUMRECORDS

Optional

Target number of records. You will get at least this many records, but may get more. The recipe will always execute to completion, so if it creates 3 records per execution and you ask for 5, you will get 6.

--num_records_tablename NUMRECORDSTABLENAME

Optional

A string representing which table determines when the recipe execution is done.

--batch_size BATCHSIZE

Optional

How many records to create and load at a time.

--data_generation_options DATAGENERATIONOPTIONS

Optional

Options to pass to the data generator.

--vars VARS

Optional

Pass values to override options in the format VAR1:foo,VAR2:bar

--replace_database REPLACEDATABASE

Optional

Confirmation that it is okay to delete the data in database_url

--working_directory WORKINGDIRECTORY

Optional

Default path for temporary / working files

--database_url DATABASEURL

Optional

A path to put a copy of the sqlite database (for debugging)

--mapping MAPPING

Optional

A mapping YAML file to use

--start_step STARTSTEP

Optional

If specified, skip steps before this one in the mapping

--sql_path SQLPATH

Optional

If specified, a database will be created from an SQL script at the provided path

--ignore_row_errors IGNOREROWERRORS

Optional

If True, allow the load to continue even if individual rows fail to load.

--reset_oids RESETOIDS

Optional

If True (the default), and the _sf_ids tables exist, reset them before continuing.

--bulk_mode BULKMODE

Optional

Set to Serial to force serial mode on all jobs. Parallel is the default.

--inject_namespaces INJECTNAMESPACES

Optional

If True, the package namespace prefix will be automatically added to (or removed from) objects and fields based on the name used in the org. Defaults to True.

--drop_missing_schema DROPMISSINGSCHEMA

Optional

Set to True to skip any missing objects or fields instead of stopping with an error.

--set_recently_viewed SETRECENTLYVIEWED

Optional

By default, the first 1000 records inserted via the Bulk API will be set as recently viewed. If fewer than 1000 records are inserted, existing objects of the same type being inserted will also be set as recently viewed.

--plugin_options PLUGINOPTIONS

Optional

Pass values to override plugin options in the format VAR1:foo,VAR2:bar

--generate_mapping_file GENERATEMAPPINGFILE

Optional

A path to put a mapping file inferred from the generator_yaml

--continuation_file CONTINUATIONFILE

Optional

YAML file generated by Snowfakery representing next steps for data generation

--generate_continuation_file GENERATECONTINUATIONFILE

Optional

Description: Retrieves all Record Types in the org as a dict, with sObject names as keys and lists of Developer Names as values.

Class: cumulusci.tasks.preflight.recordtypes.CheckSObjectRecordTypes

Command Syntax¶

$ cci task run get_existing_record_types

get_existing_sites¶

Description: Retrieves a list of any existing Experience Cloud site names in the org.

Class: cumulusci.tasks.salesforce.ListCommunities

Lists Communities for the current org via the Connect API.

Command Syntax¶

$ cci task run get_existing_sites

github_parent_pr_notes¶

Description: Merges the description of a child pull request to the respective parent’s pull request (if one exists).

Class: cumulusci.tasks.release_notes.task.ParentPullRequestNotes

Aggregate change notes from child pull request(s) to a corresponding parent pull request.

When given the branch_name option, this task will: (1) check if the base branch of the corresponding pull request starts with the feature branch prefix and if so (2) attempt to query for a pull request corresponding to this parent feature branch. (3) if a pull request isn’t found, the task exits and no actions are taken.

If the build_notes_label is present on the pull request, then all notes from the child pull request are aggregated into the parent pull request. if the build_notes_label is not detected on the parent pull request then a link to the child pull request is placed under the “Unaggregated Pull Requests” header.

If you have a pull request on branch feature/myFeature that you would like to rebuild notes for use the branch_name and force options:

cci task run github_parent_pr_notes –branch-name feature/myFeature –force True

Command Syntax¶

$ cci task run github_parent_pr_notes

Options¶

--branch_name BRANCHNAME

Required

Name of branch to check for parent status, and if so, reaggregate change notes from child branches.

--build_notes_label BUILDNOTESLABEL

Required

Name of the label that indicates that change notes on parent pull requests should be reaggregated when a child branch pull request is created.

--force FORCE

Optional

force rebuilding of change notes from child branches in the given branch.

github_clone_tag¶

Description: Clones a github tag under a new name.

Class: cumulusci.tasks.github.CloneTag

Command Syntax¶

$ cci task run github_clone_tag

Options¶

--src_tag SRCTAG

Required

The source tag to clone. Ex: beta/1.0-Beta_2

--tag TAG

Required

The new tag to create by cloning the src tag. Ex: release/1.0

github_automerge_main¶

Description: Merges the latest commit on the main branch into all open feature branches

Class: cumulusci.tasks.github.MergeBranch

Merges the most recent commit on the current branch into other branches depending on the value of source_branch.

If source_branch is a branch that does not start with the specified branch_prefix, then the commit will be merged to all branches that begin with branch_prefix and are not themselves child branches (i.e. branches don’t contain ‘__’ in their name).

If source_branch begins with branch_prefix, then the commit is merged to all child branches of source_branch.

Command Syntax¶

$ cci task run github_automerge_main

Options¶

--commit COMMIT

Optional

The commit to merge into feature branches. Defaults to the current head commit.

--source_branch SOURCEBRANCH

Optional

The source branch to merge from. Defaults to project__git__default_branch.

--branch_prefix BRANCHPREFIX

Optional

A list of prefixes of branches that should receive the merge. Defaults to project__git__prefix_feature

--skip_future_releases SKIPFUTURERELEASES

Optional

If true, then exclude branches that start with the branch prefix if they are not for the lowest release number. Defaults to True.

--update_future_releases UPDATEFUTURERELEASES

Optional

If true, then include release branches that are not the lowest release number even if they are not child branches. Defaults to False.

github_automerge_feature¶

Description: Merges the latest commit on a source branch to all child branches.

Class: cumulusci.tasks.github.MergeBranch

Merges the most recent commit on the current branch into other branches depending on the value of source_branch.

If source_branch begins with branch_prefix, then the commit is merged to all child branches of source_branch.

Command Syntax¶

$ cci task run github_automerge_feature

Options¶

--commit COMMIT

Optional

The commit to merge into feature branches. Defaults to the current head commit.

--source_branch SOURCEBRANCH

Optional

The source branch to merge from. Defaults to project__git__default_branch.

Default: $project_config.repo_branch

--branch_prefix BRANCHPREFIX

Optional

A list of prefixes of branches that should receive the merge. Defaults to project__git__prefix_feature

--skip_future_releases SKIPFUTURERELEASES

Optional

If true, then exclude branches that start with the branch prefix if they are not for the lowest release number. Defaults to True.

--update_future_releases UPDATEFUTURERELEASES

Optional

If true, then include release branches that are not the lowest release number even if they are not child branches. Defaults to False.

github_copy_subtree¶

Description: Copies one or more subtrees from the project repository for a given release to a target repository, with the option to include release notes.

Class: cumulusci.tasks.github.publish.PublishSubtree

Command Syntax¶

$ cci task run github_copy_subtree

Options¶

--repo_url REPOURL

Required

The url to the public repo

--branch BRANCH

Required

The branch to update in the target repo

--version VERSION

Optional

(Deprecated >= 3.42.0) Only the values of ‘latest’ and ‘latest_beta’ are acceptable. Required if ‘ref’ or ‘tag_name’ is not set. This will override tag_name if it is provided.

--tag_name TAGNAME

Optional

The name of the tag that should be associated with this release. Values of ‘latest’ and ‘latest_beta’ are also allowed. Required if ‘ref’ or ‘version’ is not set.

--ref REF

Optional

The git reference to publish. Takes precedence over ‘version’ and ‘tag_name’. Required if ‘tag_name’ is not set.

--include INCLUDE

Optional

A list of paths from repo root to include. Directories must end with a trailing slash.

--renames RENAMES

Optional

A list of paths to rename in the target repo, given as local: target: pairs.

--create_release CREATERELEASE

Optional

If True, create a release in the public repo. Defaults to False

--release_body RELEASEBODY

Optional

If True, the entire release body will be published to the public repo. Defaults to False

--dry_run DRYRUN

Optional

If True, skip creating Github data. Defaults to False

github_package_data¶

Description: Look up 2gp package dependencies for a version id recorded in a commit status.

Class: cumulusci.tasks.github.commit_status.GetPackageDataFromCommitStatus

Command Syntax¶

$ cci task run github_package_data

Options¶

--context CONTEXT

Required

Name of the commit status context

--version_id VERSIONID

Optional

Package version id

github_pull_requests¶

Description: Lists open pull requests in project Github repository

Class: cumulusci.tasks.github.PullRequests

Command Syntax¶

$ cci task run github_pull_requests

github_release¶

Description: Creates a Github release for a given managed package version number

Class: cumulusci.tasks.github.CreateRelease

Command Syntax¶

$ cci task run github_release

Options¶

--version VERSION

Required

The managed package version number. Ex: 1.2

--package_type PACKAGETYPE

Required

The package type of the project (either 1GP or 2GP)

--tag_prefix TAGPREFIX

Required

The prefix to use for the release tag created in github.

--version_id VERSIONID

Optional

The SubscriberPackageVersionId (04t) associated with this release.

--message MESSAGE

Optional

The message to attach to the created git tag

--dependencies DEPENDENCIES

Optional

List of dependencies to record in the tag message.

--commit COMMIT

Optional

Override the commit used to create the release. Defaults to the current local HEAD commit

--resolution_strategy RESOLUTIONSTRATEGY

Optional

The name of a sequence of resolution_strategy (from project__dependency_resolutions) to apply to dynamic dependencies. Defaults to ‘production’.

gather_release_notes¶

Description: Generates release notes by getting the latest release of each repository

Class: cumulusci.tasks.release_notes.task.AllGithubReleaseNotes

Command Syntax¶

$ cci task run gather_release_notes

Options¶

--repos REPOS

Required

The list of owner, repo key pairs for which to generate release notes. Ex: ‘owner’: SalesforceFoundation ‘repo’: ‘NPSP’

github_release_notes¶

Description: Generates release notes by parsing pull request bodies of merged pull requests between two tags

Class: cumulusci.tasks.release_notes.task.GithubReleaseNotes

Command Syntax¶

$ cci task run github_release_notes

Options¶

--tag TAG

Required

The tag to generate release notes for. Ex: release/1.2

--last_tag LASTTAG

Optional

Override the last release tag. This is useful to generate release notes if you skipped one or more releases.

--link_pr LINKPR

Optional

If True, insert link to source pull request at end of each line.

--publish PUBLISH

Optional

Publish to GitHub release if True (default=False)

--include_empty INCLUDEEMPTY

Optional

If True, include links to PRs that have no release notes (default=False)

--version_id VERSIONID

Optional

The package version id used by the InstallLinksParser to add install urls

--trial_info TRIALINFO

Optional

If True, Includes trialforce template text for this product.

--sandbox_date SANDBOXDATE

Optional

The date of the sandbox release in ISO format (Will default to None)

--production_date PRODUCTIONDATE

Optional

The date of the production release in ISO format (Will default to None)

github_release_report¶

Description: Parses GitHub release notes to report various info

Class: cumulusci.tasks.github.ReleaseReport

Command Syntax¶

$ cci task run github_release_report

Options¶

--date_start DATESTART

Optional

Filter out releases created before this date (YYYY-MM-DD)

--date_end DATEEND

Optional

Filter out releases created after this date (YYYY-MM-DD)

--include_beta INCLUDEBETA

Optional

Include beta releases in report [default=False]

--print PRINT

Optional

Print info to screen as JSON [default=False]

install_managed¶

Description: Install the latest managed production release

Class: cumulusci.tasks.salesforce.InstallPackageVersion

Command Syntax¶

$ cci task run install_managed

Options¶

--namespace NAMESPACE

Required

The namespace of the package to install. Defaults to project__package__namespace

--version VERSION

Required

The version of the package to install. “latest” and “latest_beta” can be used to trigger lookup via Github Releases on the repository.

Default: latest

--name NAME

Optional

The name of the package to install. Defaults to project__package__name_managed

--version_number VERSIONNUMBER

Optional

If installing a package using an 04t version Id, display this version number to the user and in logs. Has no effect otherwise.

--activateRSS ACTIVATERSS

Optional

Deprecated. Use activate_remote_site_settings instead.

--retries RETRIES

Optional

Number of retries (default=5)

--retry_interval RETRYINTERVAL

Optional

Number of seconds to wait before the next retry (default=5),

--retry_interval_add RETRYINTERVALADD

Optional

Number of seconds to add before each retry (default=30),

--security_type SECURITYTYPE

Optional

Which Profiles to install packages for (FULL = all profiles, NONE = admins only, PUSH = no profiles, CUSTOM = custom profiles). Defaults to FULL.

--name_conflict_resolution NAMECONFLICTRESOLUTION

Optional

Specify how to resolve name conflicts when installing an Unlocked Package. Available values are Block and RenameMetadata. Defaults to Block.

--activate_remote_site_settings ACTIVATEREMOTESITESETTINGS

Optional

Activate Remote Site Settings when installing a package. Defaults to True.

--password PASSWORD

Optional

The installation key for the managed package.

install_managed_beta¶

Description: Installs the latest managed beta release

Class: cumulusci.tasks.salesforce.InstallPackageVersion

Command Syntax¶

$ cci task run install_managed_beta

Options¶

--namespace NAMESPACE

Required

The namespace of the package to install. Defaults to project__package__namespace

--version VERSION

Required

The version of the package to install. “latest” and “latest_beta” can be used to trigger lookup via Github Releases on the repository.

Default: latest_beta

--name NAME

Optional

The name of the package to install. Defaults to project__package__name_managed

--version_number VERSIONNUMBER

Optional

If installing a package using an 04t version Id, display this version number to the user and in logs. Has no effect otherwise.

--activateRSS ACTIVATERSS

Optional

Deprecated. Use activate_remote_site_settings instead.

--retries RETRIES

Optional

Number of retries (default=5)

--retry_interval RETRYINTERVAL

Optional

Number of seconds to wait before the next retry (default=5),

--retry_interval_add RETRYINTERVALADD

Optional

Number of seconds to add before each retry (default=30),

--security_type SECURITYTYPE

Optional

Which Profiles to install packages for (FULL = all profiles, NONE = admins only, PUSH = no profiles, CUSTOM = custom profiles). Defaults to FULL.

--name_conflict_resolution NAMECONFLICTRESOLUTION

Optional

Specify how to resolve name conflicts when installing an Unlocked Package. Available values are Block and RenameMetadata. Defaults to Block.

--activate_remote_site_settings ACTIVATEREMOTESITESETTINGS

Optional

Activate Remote Site Settings when installing a package. Defaults to True.

--password PASSWORD

Optional

The installation key for the managed package.

list_communities¶

Description: Lists Communities for the current org using the Connect API.

Class: cumulusci.tasks.salesforce.ListCommunities

Lists Communities for the current org via the Connect API.

Command Syntax¶

$ cci task run list_communities

list_community_templates¶

Description: Prints the Community Templates available to the current org

Class: cumulusci.tasks.salesforce.ListCommunityTemplates

Lists Salesforce Community templates available for the current org via the Connect API.

Command Syntax¶

$ cci task run list_community_templates

list_metadata_types¶

Description: Prints the metadata types in a project

Class: cumulusci.tasks.util.ListMetadataTypes

Command Syntax¶

$ cci task run list_metadata_types

Options¶

--package_xml PACKAGEXML

Optional

The project package.xml file. Defaults to <project_root>/src/package.xml

meta_xml_apiversion¶

Description: Set the API version in *meta.xml files

Class: cumulusci.tasks.metaxml.UpdateApi

Command Syntax¶

$ cci task run meta_xml_apiversion

Options¶

--version VERSION

Required

API version number e.g. 37.0

--dir DIR

Optional

Base directory to search for *-meta.xml files

meta_xml_dependencies¶

Description: Set the version for dependent packages

Class: cumulusci.tasks.metaxml.UpdateDependencies

Command Syntax¶

$ cci task run meta_xml_dependencies

Options¶

--dir DIR

Optional

Base directory to search for *-meta.xml files

metadeploy_publish¶

Description: Publish a release to the MetaDeploy web installer

Class: cumulusci.tasks.metadeploy.Publish

Command Syntax¶

$ cci task run metadeploy_publish

Options¶

--tag TAG

Optional

Name of the git tag to publish

--commit COMMIT

Optional

Commit hash to publish

--plan PLAN

Optional

Name of the plan(s) to publish. This refers to the plans section of cumulusci.yml. By default, all plans will be published.

--dry_run DRYRUN

Optional

If True, print steps without publishing.

--publish PUBLISH

Optional

If True, set is_listed to True on the version. Default: False

--labels_path LABELSPATH

Optional

Path to a folder containing translations.

org_settings¶

Description: Apply org settings from a scratch org definition file or dict

Class: cumulusci.tasks.salesforce.org_settings.DeployOrgSettings

Command Syntax¶

$ cci task run org_settings

Options¶

--definition_file DEFINITIONFILE

Optional

sfdx scratch org definition file

--settings SETTINGS

Optional

A dict of settings to apply

--api_version APIVERSION

Optional

API version used to deploy the settings

promote_package_version¶

Description: Promote a 2gp package so that it can be installed in a production org

Class: cumulusci.tasks.salesforce.promote_package_version.PromotePackageVersion

Promote a Second Generation package (managed or unlocked).: Lists any 1GP dependencies that are detected, as well as any dependency packages that have not been promoted. Once promoted, the 2GP package can be installed into production orgs.

Command Syntax¶

$ cci task run promote_package_version

Options¶

--version_id VERSIONID

Optional

The SubscriberPackageVersion (04t) Id for the target package.

--promote_dependencies PROMOTEDEPENDENCIES

Optional

Automatically promote any unpromoted versions of dependency 2GP packages that are detected.

publish_community¶

Description: Publishes a Community in the target org using the Connect API

Class: cumulusci.tasks.salesforce.PublishCommunity

Publish a Salesforce Community via the Connect API. Warning: This does not work with the Community Template ‘VF Template’ due to an existing bug in the API.

Command Syntax¶

$ cci task run publish_community

Options¶

--name NAME

Optional

The name of the Community to publish.

--community_id COMMUNITYID

Optional

The id of the Community to publish.

push_all¶

Description: Schedules a push upgrade of a package version to all subscribers

Class: cumulusci.tasks.push.tasks.SchedulePushOrgQuery

Command Syntax¶

$ cci task run push_all

Options¶

--version VERSION

Required

The managed package version to push

--subscriber_where SUBSCRIBERWHERE

Optional

A SOQL style WHERE clause for filtering PackageSubscriber objects. Ex: OrgType = ‘Sandbox’

--min_version MINVERSION

Optional

If set, no subscriber with a version lower than min_version will be selected for push

--metadata_package_id METADATAPACKAGEID

Optional

The MetadataPackageId (ID prefix 033) to push.

--namespace NAMESPACE

Optional

The managed package namespace to push. Defaults to project__package__namespace.

--start_time STARTTIME

Optional

Set the start time (ISO-8601) to queue a future push. (Ex: 2021-01-01T06:00Z or 2021-01-01T06:00-08:00) Times with no timezone will be interpreted as UTC.

--dry_run DRYRUN

Optional

If True, log how many orgs were selected but skip creating a PackagePushRequest. Defaults to False

push_list¶

Description: Schedules a push upgrade of a package version to all orgs listed in the specified file

Class: cumulusci.tasks.push.tasks.SchedulePushOrgList

Command Syntax¶

$ cci task run push_list

Options¶

--csv CSV

Optional

The path to a CSV file to read.

--csv_field_name CSVFIELDNAME

Optional

The CSV field name that contains organization IDs. Defaults to ‘OrganizationID’

--orgs ORGS

Optional

The path to a file containing one OrgID per line.

--version VERSION

Optional

The managed package version to push

--version_id VERSIONID

Optional

The MetadataPackageVersionId (ID prefix 04t) to push

--metadata_package_id METADATAPACKAGEID

Optional

The MetadataPackageId (ID prefix 033) to push.

--namespace NAMESPACE

Optional

The managed package namespace to push. Defaults to project__package__namespace.

--start_time STARTTIME

Optional

Set the start time (ISO-8601) to queue a future push. (Ex: 2021-01-01T06:00Z or 2021-01-01T06:00-08:00) Times with no timezone will be interpreted as UTC.

--batch_size BATCHSIZE

Optional

Break pull requests into batches of this many orgs. Defaults to 200.

push_qa¶

Description: Schedules a push upgrade of a package version to all orgs listed in push/orgs_qa.txt

Class: cumulusci.tasks.push.tasks.SchedulePushOrgList

Command Syntax¶

$ cci task run push_qa

Options¶

--csv CSV

Optional

The path to a CSV file to read.

--csv_field_name CSVFIELDNAME

Optional

The CSV field name that contains organization IDs. Defaults to ‘OrganizationID’

--orgs ORGS

Optional

The path to a file containing one OrgID per line.

Default: push/orgs_qa.txt

--version VERSION

Optional

The managed package version to push

--version_id VERSIONID

Optional

The MetadataPackageVersionId (ID prefix 04t) to push

--metadata_package_id METADATAPACKAGEID

Optional

The MetadataPackageId (ID prefix 033) to push.

--namespace NAMESPACE

Optional

The managed package namespace to push. Defaults to project__package__namespace.

--start_time STARTTIME

Optional

Set the start time (ISO-8601) to queue a future push. (Ex: 2021-01-01T06:00Z or 2021-01-01T06:00-08:00) Times with no timezone will be interpreted as UTC.

--batch_size BATCHSIZE

Optional

Break pull requests into batches of this many orgs. Defaults to 200.

push_sandbox¶

Description: Schedules a push upgrade of a package version to sandbox orgs

Class: cumulusci.tasks.push.tasks.SchedulePushOrgQuery

Command Syntax¶

$ cci task run push_sandbox

Options¶

--version VERSION

Required

The managed package version to push

--subscriber_where SUBSCRIBERWHERE

Optional

A SOQL style WHERE clause for filtering PackageSubscriber objects. Ex: OrgType = ‘Sandbox’

Default: OrgType = ‘Sandbox’

--min_version MINVERSION

Optional

If set, no subscriber with a version lower than min_version will be selected for push

--metadata_package_id METADATAPACKAGEID

Optional

The MetadataPackageId (ID prefix 033) to push.

--namespace NAMESPACE

Optional

The managed package namespace to push. Defaults to project__package__namespace.

--start_time STARTTIME

Optional

Set the start time (ISO-8601) to queue a future push. (Ex: 2021-01-01T06:00Z or 2021-01-01T06:00-08:00) Times with no timezone will be interpreted as UTC.

--dry_run DRYRUN

Optional

If True, log how many orgs were selected but skip creating a PackagePushRequest. Defaults to False

push_trial¶

Description: Schedules a push upgrade of a package version to Trialforce Template orgs listed in push/orgs_trial.txt

Class: cumulusci.tasks.push.tasks.SchedulePushOrgList

Command Syntax¶

$ cci task run push_trial

Options¶

--csv CSV

Optional

The path to a CSV file to read.

--csv_field_name CSVFIELDNAME

Optional

The CSV field name that contains organization IDs. Defaults to ‘OrganizationID’

--orgs ORGS

Optional

The path to a file containing one OrgID per line.

Default: push/orgs_trial.txt

--version VERSION

Optional

The managed package version to push

--version_id VERSIONID

Optional

The MetadataPackageVersionId (ID prefix 04t) to push

--metadata_package_id METADATAPACKAGEID

Optional

The MetadataPackageId (ID prefix 033) to push.

--namespace NAMESPACE

Optional

The managed package namespace to push. Defaults to project__package__namespace.

--start_time STARTTIME

Optional

Set the start time (ISO-8601) to queue a future push. (Ex: 2021-01-01T06:00Z or 2021-01-01T06:00-08:00) Times with no timezone will be interpreted as UTC.

--batch_size BATCHSIZE

Optional

Break pull requests into batches of this many orgs. Defaults to 200.

push_failure_report¶

Description: Produce a CSV report of the failed and otherwise anomalous push jobs.

Class: cumulusci.tasks.push.pushfails.ReportPushFailures

Command Syntax¶

$ cci task run push_failure_report

Options¶

--request_id REQUESTID

Required

PackagePushRequest ID for the request you need to report on.

--result_file RESULTFILE

Optional

Path to write a CSV file with the results. Defaults to ‘push_fails.csv’.

--ignore_errors IGNOREERRORS

Optional

List of ErrorTitle and ErrorType values to omit from the report

Default: [‘Salesforce Subscription Expired’, ‘Package Uninstalled’]

query¶

Description: Queries the connected org

Class: cumulusci.tasks.salesforce.SOQLQuery

Command Syntax¶

$ cci task run query

Options¶

--object OBJECT

Required

The object to query

--query QUERY

Required

A valid bulk SOQL query for the object

--result_file RESULTFILE

Required

The name of the csv file to write the results to

retrieve_packaged¶

Description: Retrieves the packaged metadata from the org

Class: cumulusci.tasks.salesforce.RetrievePackaged

Command Syntax¶

$ cci task run retrieve_packaged

Options¶

--path PATH

Required

The path to write the retrieved metadata

Default: packaged

--package PACKAGE

Required

The package name to retrieve. Defaults to project__package__name

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--namespace_tokenize NAMESPACETOKENIZE

Optional

If set, all namespace prefixes for the namespace specified are replaced with tokens for use with namespace_inject

--namespaced_org NAMESPACEDORG

Optional

--api_version APIVERSION

Optional

Override the default api version for the retrieve. Defaults to project__package__api_version

retrieve_src¶

Description: Retrieves the packaged metadata into the src directory

Class: cumulusci.tasks.salesforce.RetrievePackaged

Command Syntax¶

$ cci task run retrieve_src

Options¶

--path PATH

Required

The path to write the retrieved metadata

Default: src

--package PACKAGE

Required

The package name to retrieve. Defaults to project__package__name

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--namespace_tokenize NAMESPACETOKENIZE

Optional

If set, all namespace prefixes for the namespace specified are replaced with tokens for use with namespace_inject

--namespaced_org NAMESPACEDORG

Optional

--api_version APIVERSION

Optional

Override the default api version for the retrieve. Defaults to project__package__api_version

retrieve_unpackaged¶

Description: Retrieve the contents of a package.xml file.

Class: cumulusci.tasks.salesforce.RetrieveUnpackaged

Command Syntax¶

$ cci task run retrieve_unpackaged

Options¶

--path PATH

Required

The path to write the retrieved metadata

--package_xml PACKAGEXML

Required

The path to a package.xml manifest to use for the retrieve.

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--namespace_tokenize NAMESPACETOKENIZE

Optional

If set, all namespace prefixes for the namespace specified are replaced with tokens for use with namespace_inject

--namespaced_org NAMESPACEDORG

Optional

--api_version APIVERSION

Optional

Override the default api version for the retrieve. Defaults to project__package__api_version

list_changes¶

Description: List the changes from a scratch org

Class: cumulusci.tasks.salesforce.sourcetracking.ListChanges

Command Syntax¶

$ cci task run list_changes

Options¶

--include INCLUDE

Optional

A comma-separated list of strings. Components will be included if one of these strings is part of either the metadata type or name. Example: -o include CustomField,Admin matches both CustomField: Favorite_Color__c and Profile: Admin

--types TYPES

Optional

A comma-separated list of metadata types to include.

--exclude EXCLUDE

Optional

Exclude changed components matching this string.

--snapshot SNAPSHOT

Optional

If True, all matching items will be set to be ignored at their current revision number. This will exclude them from the results unless a new edit is made.

retrieve_changes¶

Description: Retrieve changed components from a scratch org

Class: cumulusci.tasks.salesforce.sourcetracking.RetrieveChanges

Command Syntax¶

$ cci task run retrieve_changes

Options¶

--include INCLUDE

Optional

--types TYPES

Optional

A comma-separated list of metadata types to include.

--exclude EXCLUDE

Optional

Exclude changed components matching this string.

--snapshot SNAPSHOT

Optional

If True, all matching items will be set to be ignored at their current revision number. This will exclude them from the results unless a new edit is made.

--path PATH

Optional

The path to write the retrieved metadata

--api_version APIVERSION

Optional

Override the default api version for the retrieve. Defaults to project__package__api_version

--namespace_tokenize NAMESPACETOKENIZE

Optional

If set, all namespace prefixes for the namespace specified are replaced with tokens for use with namespace_inject

retrieve_qa_config¶

Description: Retrieves the current changes in the scratch org into unpackaged/config/qa

Class: cumulusci.tasks.salesforce.sourcetracking.RetrieveChanges

Command Syntax¶

$ cci task run retrieve_qa_config

Options¶

--include INCLUDE

Optional

--types TYPES

Optional

A comma-separated list of metadata types to include.

--exclude EXCLUDE

Optional

Exclude changed components matching this string.

--snapshot SNAPSHOT

Optional

If True, all matching items will be set to be ignored at their current revision number. This will exclude them from the results unless a new edit is made.

--path PATH

Optional

The path to write the retrieved metadata

Default: unpackaged/config/qa

--api_version APIVERSION

Optional

Override the default api version for the retrieve. Defaults to project__package__api_version

--namespace_tokenize NAMESPACETOKENIZE

Optional

If set, all namespace prefixes for the namespace specified are replaced with tokens for use with namespace_inject

Default: $project_config.project__package__namespace

set_field_help_text¶

Description: Sets specified fields’ Help Text values.

Class: cumulusci.tasks.metadata_etl.help_text.SetFieldHelpText

Command Syntax¶

$ cci task run set_field_help_text

Options¶

--fields FIELDS

Required

List of object fields to affect, in Object__c.Field__c form.

--overwrite OVERWRITE

Optional

If set to True, overwrite any differing Help Text found on the field. By default, Help Text is set only if it is blank.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

snapshot_changes¶

Description: Tell SFDX source tracking to ignore previous changes in a scratch org

Class: cumulusci.tasks.salesforce.sourcetracking.SnapshotChanges

Command Syntax¶

$ cci task run snapshot_changes

snowfakery¶

Description: Generate and load data from a Snowfakery recipe

Class: cumulusci.tasks.bulkdata.snowfakery.Snowfakery

Do a data load with Snowfakery.

All options are optional.

The most commonly supplied options are recipe and one of the three run_until_… options.

Command Syntax¶

$ cci task run snowfakery

Options¶

--recipe RECIPE

Required

Path to a Snowfakery recipe file determining what data to generate and load.

Default: datasets/recipe.yml

--run_until_records_in_org RUNUNTILRECORDSINORG

Optional

<sobject>:<count>

Run the recipe repeatedly until the count of <sobject> in the org matches the given <count>.

For example, –run_until_records_in_org Account:50_000 means:

Count the Account records in the org. Let’s say the number is 20,000. Thus, we must run the recipe over and over again until we generate 30,000 new Account records. If the recipe also generates e.g.Contacts, Opportunities or whatever else, it generates the appropriate number of them to match.

Underscores are allowed but optional in big numbers: 2000000 is the same as 2_000_000.

--run_until_records_loaded RUNUNTILRECORDSLOADED

Optional

<sobject>:<count>

Run the recipe repeatedly until the number of records of <sobject> uploaded in this task execution matches <count>.

For example, –run_until_records_loaded Account:50_000 means:

Run the recipe over and over again until we generate 50_000 new Account records. If the recipe also generates e.g. Contacts, Opportunities or whatever else, it generates the appropriate number of them to match.

--run_until_recipe_repeated RUNUNTILRECIPEREPEATED

Optional

Run the recipe <count> times,

no matter what data is already in the org.

For example, –run_until_recipe_repeated 50_000 means run the recipe 50_000 times.

--working_directory WORKINGDIRECTORY

Optional

Path for temporary / working files

--loading_rules LOADINGRULES

Optional

Path to .load.yml file containing rules to use to load the file. Defaults to <recipename>.load.yml. Multiple files can be comma separated.

--recipe_options RECIPEOPTIONS

Optional

Pass values to override options in the format VAR1:foo,VAR2:bar

Example: –recipe_options weight:10,color:purple

--bulk_mode BULKMODE

Optional

Set to Serial to serialize everything: data generation, data loading, data ingestion through bulk API. Parallel is the default.

--drop_missing_schema DROPMISSINGSCHEMA

--suites SUITES

Required

Paths to test case files/directories to be executed similarly as when running the robot command on the command line. Defaults to “tests” to run all tests in the tests directory

Default: tests

--test TEST

Optional

Run only tests matching name patterns. Can be comma separated and use robot wildcards like *

--include INCLUDE

Optional

Includes tests with a given tag pattern

--exclude EXCLUDE

Optional

Excludes tests with a given tag pattern. Excluded tests will not appear in the logs and reports.

--skip SKIP

Optional

Do not run tests with the given tag pattern. Similar to ‘exclude’, but skipped tests will appear in the logs and reports with the status of SKIP.

--vars VARS

Optional

Pass values to override variables in the format VAR1:foo,VAR2:bar

--xunit XUNIT

Optional

Set an XUnit format output file for test results

--sources SOURCES

Optional

List of sources defined in cumulusci.yml that are required by the robot task.

--options OPTIONS

Optional

A dictionary of options to robot.run method. In simple cases this can be specified on the comand line using name:value,name:value syntax. More complex cases can be specified in cumulusci.yml using YAML dictionary syntax.

--name NAME

Optional

Sets the name of the top level test suite

--pdb PDB

Optional

If true, run the Python debugger when tests fail.

--verbose VERBOSE

Optional

If true, log each keyword as it runs.

--robot_debug ROBOTDEBUG

Optional

If true, enable the breakpoint keyword to enable the robot debugger

--ordering ORDERING

Optional

Path to a file which defines the order in which parallel tests are run. This maps directly to the pabot option of the same name. It is ignored unless the processes argument is set to 2 or greater.

--processes PROCESSES

Optional

experimental Number of processes to use for running tests in parallel. If this value is set to a number larger than 1 the tests will run using the open source tool pabot rather than robotframework. For example, -o parallel 2 will run half of the tests in one process and half in another. If not provided, all tests will run in a single process using the standard robot test runner. See https://pabot.org/ for more information on pabot.

--testlevelsplit TESTLEVELSPLIT

Optional

If true, split parallel execution at the test level rather than the suite level. This option is ignored unless the processes option is set to 2 or greater. Note: this option requires a boolean value even though the pabot option of the same name does not.

robot_libdoc¶

Description: Generates documentation for project keyword files

Class: cumulusci.tasks.robotframework.RobotLibDoc

Command Syntax¶

$ cci task run robot_libdoc

Options¶

--path PATH

Required

The path to one or more keyword libraries to be documented. The path can be single a python file, a .robot file, a python module (eg: cumulusci.robotframework.Salesforce) or a comma separated list of any of those. Glob patterns are supported for filenames (eg: robot/SAL/doc/*PageObject.py). The order of the files will be preserved in the generated documentation. The result of pattern expansion will be sorted

--output OUTPUT

Required

The output file where the documentation will be written. Normally an HTML file will be generated. If the filename ends with ‘.csv’ then a csv file will be generated instead.

Default: Keywords.html

--title TITLE

Optional

A string to use as the title of the generated output

Default: $project_config.project__package__name

robot_lint¶

Description: Static analysis tool for robot framework files

Class: cumulusci.tasks.robotframework.RobotLint

The robot_lint task performs static analysis on one or more .robot and .resource files. Each line is parsed, and the result passed through a series of rules. Rules can issue warnings or errors about each line.

If any errors are reported, the task will exit with a non-zero status.

When a rule has been violated, a line will appear on the output in the following format:

<severity>: <line>, <character>: <description> (<name>)

<severity> will be either W for warning or E for error
<line> is the line number where the rule was triggered
<character> is the character where the rule was triggered, or 0 if the rule applies to the whole line
<description> is a short description of the issue
<name> is the name of the rule that raised the issue

Note: the rule name can be used with the ignore, warning, error, and configure options.

Some rules are configurable, and can be configured with the configure option. This option takes a list of values in the form <rule>:<value>,*<rule>*:<value>,etc. For example, to set the line length for the LineTooLong rule you can use ‘-o configure LineTooLong:80’. If a rule is configurable, it will show the configuration options in the documentation for that rule

The filename will be printed once before any errors or warnings for that file. The filename is preceeded by +

Example Output:

+ example.robot
W: 2, 0: No suite documentation (RequireSuiteDocumentation)
E: 30, 0: No testcase documentation (RequireTestDocumentation)

To see a list of all configured rules, set the ‘list’ option to True:

cci task run robot_lint -o list True

Command Syntax¶

$ cci task run robot_lint

Options¶

--configure CONFIGURE

Optional

List of rule configuration values, in the form of rule:args.

--ignore IGNORE

Optional

List of rules to ignore. Use ‘all’ to ignore all rules

--error ERROR

Optional

List of rules to treat as errors. Use ‘all’ to affect all rules.

--warning WARNING

Optional

List of rules to treat as warnings. Use ‘all’ to affect all rules.

--list LIST

Optional

If option is True, print a list of known rules instead of processing files.

--path PATH

Optional

The path to one or more files or folders. If the path includes wildcard characters, they will be expanded. If not provided, the default will be to process all files under robot/<project name>

robot_testdoc¶

Description: Generates html documentation of your Robot test suite and writes to tests/test_suite.

Class: cumulusci.tasks.robotframework.RobotTestDoc

Command Syntax¶

$ cci task run robot_testdoc

Options¶

--path PATH

Required

The path containing .robot test files

Default: tests

--output OUTPUT

Required

The output html file where the documentation will be written

Default: tests/test_suites.html

run_tests¶

Description: Runs all apex tests

Class: cumulusci.tasks.apex.testrunner.RunApexTests

Command Syntax¶

$ cci task run run_tests

Options¶

--test_name_match TESTNAMEMATCH

Required

Pattern to find Apex test classes to run (“%” is wildcard). Defaults to project__test__name_match from project config. Comma-separated list for multiple patterns.

--test_name_exclude TESTNAMEEXCLUDE

Optional

Query to find Apex test classes to exclude (“%” is wildcard). Defaults to project__test__name_exclude from project config. Comma-separated list for multiple patterns.

--namespace NAMESPACE

Optional

Salesforce project namespace. Defaults to project__package__namespace

--managed MANAGED

Optional

If True, search for tests in the namespace only. Defaults to False

--poll_interval POLLINTERVAL

Optional

Seconds to wait between polling for Apex test results.

--junit_output JUNITOUTPUT

Optional

File name for JUnit output. Defaults to test_results.xml

--json_output JSONOUTPUT

Optional

File name for json output. Defaults to test_results.json

--retry_failures RETRYFAILURES

Optional

A list of regular expression patterns to match against test failures. If failures match, the failing tests are retried in serial mode.

--retry_always RETRYALWAYS

Optional

By default, all failures must match retry_failures to perform a retry. Set retry_always to True to retry all failed tests if any failure matches.

-o required_org_code_coverage_percent PERCENTAGE

Optional

Require at least X percent code coverage across the org following the test run.

--verbose VERBOSE

Optional

By default, only failures get detailed output. Set verbose to True to see all passed test methods.

set_duplicate_rule_status¶

Description: Sets the active status of Duplicate Rules.

Class: cumulusci.tasks.metadata_etl.SetDuplicateRuleStatus

Command Syntax¶

$ cci task run set_duplicate_rule_status

Options¶

--active ACTIVE

Required

Boolean value, set the Duplicate Rule to either active or inactive

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

set_organization_wide_defaults¶

Description: Sets the Organization-Wide Defaults for specific sObjects, and waits for sharing recalculation to complete.

Class: cumulusci.tasks.metadata_etl.SetOrgWideDefaults

Command Syntax¶

$ cci task run set_organization_wide_defaults

Options¶

--org_wide_defaults ORGWIDEDEFAULTS

Required

The target Organization-Wide Defaults, organized as a list with each element containing the keys api_name, internal_sharing_model, and external_sharing_model. NOTE: you must have External Sharing Model turned on in Sharing Settings to use the latter feature.

--timeout TIMEOUT

Optional

The max amount of time to wait in seconds

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

uninstall_managed¶

Description: Uninstalls the managed version of the package

Class: cumulusci.tasks.salesforce.UninstallPackage

Command Syntax¶

$ cci task run uninstall_managed

Options¶

--namespace NAMESPACE

Required

The namespace of the package to uninstall. Defaults to project__package__namespace

--purge_on_delete PURGEONDELETE

Required

Sets the purgeOnDelete option for the deployment. Defaults to True

uninstall_packaged¶

Description: Uninstalls all deleteable metadata in the package in the target org

Class: cumulusci.tasks.salesforce.UninstallPackaged

Command Syntax¶

$ cci task run uninstall_packaged

Options¶

--package PACKAGE

Required

The package name to uninstall. All metadata from the package will be retrieved and a custom destructiveChanges.xml package will be constructed and deployed to delete all deleteable metadata from the package. Defaults to project__package__name

--purge_on_delete PURGEONDELETE

Required

Sets the purgeOnDelete option for the deployment. Defaults to True

--dry_run DRYRUN

Optional

Perform a dry run of the operation without actually deleting any components, and display the components that would be deleted.

uninstall_packaged_incremental¶

Description: Deletes any metadata from the package in the target org not in the local workspace

Class: cumulusci.tasks.salesforce.UninstallPackagedIncremental

Command Syntax¶

$ cci task run uninstall_packaged_incremental

Options¶

--path PATH

Required

The local path to compare to the retrieved packaged metadata from the org. Defaults to src

--package PACKAGE

Required

--purge_on_delete PURGEONDELETE

Required

Sets the purgeOnDelete option for the deployment. Defaults to True

--ignore IGNORE

Optional

Components to ignore in the org and not try to delete. Mapping of component type to a list of member names.

--ignore_types IGNORETYPES

Optional

List of component types to ignore in the org and not try to delete. Defaults to [‘RecordType’, ‘CustomObjectTranslation’]

--dry_run DRYRUN

Optional

Perform a dry run of the operation without actually deleting any components, and display the components that would be deleted.

uninstall_src¶

Description: Uninstalls all metadata in the local src directory

Class: cumulusci.tasks.salesforce.UninstallLocal

Command Syntax¶

$ cci task run uninstall_src

Options¶

--path PATH

Required

The path to the metadata source to be deployed

Default: src

--unmanaged UNMANAGED

Optional

If True, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--check_only CHECKONLY

Optional

If True, performs a test deployment (validation) of components without saving the components in the target org

--test_level TESTLEVEL

Optional

Specifies which tests are run as part of a deployment. Valid values: NoTestRun, RunLocalTests, RunAllTestsInOrg, RunSpecifiedTests.

--specified_tests SPECIFIEDTESTS

Optional

Comma-separated list of test classes to run upon deployment. Applies only with test_level set to RunSpecifiedTests.

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--namespaced_org NAMESPACEDORG

Optional

--clean_meta_xml CLEANMETAXML

Optional

--purge_on_delete PURGEONDELETE

Optional

Sets the purgeOnDelete option for the deployment. Defaults to True

--dry_run DRYRUN

Optional

Perform a dry run of the operation without actually deleting any components, and display the components that would be deleted.

uninstall_pre¶

Description: Uninstalls the unpackaged/pre bundles

Class: cumulusci.tasks.salesforce.UninstallLocalBundles

Command Syntax¶

$ cci task run uninstall_pre

Options¶

--path PATH

Required

The path to the metadata source to be deployed

Default: unpackaged/pre

--unmanaged UNMANAGED

Optional

If True, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

--namespace_strip NAMESPACESTRIP

Optional

If set, all namespace prefixes for the namespace specified are stripped from files and filenames

--check_only CHECKONLY

Optional

If True, performs a test deployment (validation) of components without saving the components in the target org

--test_level TESTLEVEL

Optional

Specifies which tests are run as part of a deployment. Valid values: NoTestRun, RunLocalTests, RunAllTestsInOrg, RunSpecifiedTests.

--specified_tests SPECIFIEDTESTS

Optional

Comma-separated list of test classes to run upon deployment. Applies only with test_level set to RunSpecifiedTests.

--static_resource_path STATICRESOURCEPATH

Optional

The path where decompressed static resources are stored. Any subdirectories found will be zipped and added to the staticresources directory of the build.

--namespaced_org NAMESPACEDORG

Optional

--clean_meta_xml CLEANMETAXML

Optional

--purge_on_delete PURGEONDELETE

Optional

Sets the purgeOnDelete option for the deployment. Defaults to True

--dry_run DRYRUN

Optional

Perform a dry run of the operation without actually deleting any components, and display the components that would be deleted.

uninstall_post¶

Description: Uninstalls the unpackaged/post bundles

Class: cumulusci.tasks.salesforce.UninstallLocalNamespacedBundles

Command Syntax¶

$ cci task run uninstall_post

Options¶

--path PATH

Required

The path to a directory containing the metadata bundles (subdirectories) to uninstall

Default: unpackaged/post

--filename_token FILENAMETOKEN

Required

The path to the parent directory containing the metadata bundles directories

Default: ___NAMESPACE___

--purge_on_delete PURGEONDELETE

Required

Sets the purgeOnDelete option for the deployment. Defaults to True

--managed MANAGED

Optional

If True, will insert the actual namespace prefix. Defaults to False or no namespace

--namespace NAMESPACE

Optional

The namespace to replace the token with if in managed mode. Defaults to project__package__namespace

unschedule_apex¶

Description: Unschedule all scheduled apex jobs (CronTriggers).

Class: cumulusci.tasks.apex.anon.AnonymousApexTask

Use the apex option to run a string of anonymous Apex. Use the path option to run anonymous Apex from a file. Or use both to concatenate the string to the file contents.

Command Syntax¶

$ cci task run unschedule_apex

Options¶

--path PATH

Optional

The path to an Apex file to run.

--apex APEX

Optional

A string of Apex to run (after the file, if specified).

Default: for (CronTrigger t : [SELECT Id FROM CronTrigger]) { System.abortJob(t.Id); }

--managed MANAGED

Optional

If True, will insert the project’s namespace prefix. Defaults to False or no namespace.

--namespaced NAMESPACED

Optional

If True, the tokens %%%NAMESPACED_RT%%% and %%%namespaced%%% will get replaced with the namespace prefix for Record Types.

--param1 PARAM1

Optional

Parameter to pass to the Apex. Use as %%%PARAM_1%%% in the Apex code. Defaults to an empty value.

--param2 PARAM2

Optional

Parameter to pass to the Apex. Use as %%%PARAM_2%%% in the Apex code. Defaults to an empty value.

update_admin_profile¶

Description: Retrieves, edits, and redeploys the Admin.profile with full FLS perms for all objects/fields

Class: cumulusci.tasks.salesforce.ProfileGrantAllAccess

Command Syntax¶

$ cci task run update_admin_profile

Options¶

--package_xml PACKAGEXML

Optional

Override the default package.xml file for retrieving the Admin.profile and all objects and classes that need to be included by providing a path to your custom package.xml

--record_types RECORDTYPES

Optional

A list of dictionaries containing the required key record_type with a value specifying the record type in format <object>.<developer_name>. Record type names can use the token strings {managed} and {namespaced_org} for namespace prefix injection as needed. By default, all listed record types will be set to visible and not default. Use the additional keys visible, default, and person_account_default set to true/false to override. NOTE: Setting record_types is only supported in cumulusci.yml, command line override is not supported.

--managed MANAGED

Optional

If True, uses the namespace prefix where appropriate. Use if running against an org with the managed package installed. Defaults to False

--namespaced_org NAMESPACEDORG

Optional

If True, attempts to prefix all unmanaged metadata references with the namespace prefix for deployment to the packaging org or a namespaced scratch org. Defaults to False

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix. Defaults to project__package__namespace

--profile_name PROFILENAME

Optional

Name of the Profile to target for updates (deprecated; use api_names to target multiple profiles).

--include_packaged_objects INCLUDEPACKAGEDOBJECTS

Optional

Automatically include objects from all installed managed packages. Defaults to True in projects that require CumulusCI 3.9.0 and greater that don’t use a custom package.xml, otherwise False.

--api_names APINAMES

Optional

List of API names of Profiles to affect

update_dependencies¶

Description: Installs all dependencies in project__dependencies into the target org

Class: cumulusci.tasks.salesforce.UpdateDependencies

Command Syntax¶

$ cci task run update_dependencies

Options¶

--dependencies DEPENDENCIES

Optional

List of dependencies to update. Defaults to project__dependencies. Each dependency is a dict with either ‘github’ set to a github repository URL or ‘namespace’ set to a Salesforce package namespace. GitHub dependencies may include ‘tag’ to install a particular git ref. Package dependencies may include ‘version’ to install a particular version.

--ignore_dependencies IGNOREDEPENDENCIES

Optional

List of dependencies to be ignored, including if they are present as transitive dependencies. Dependencies can be specified using the ‘github’ or ‘namespace’ keys (all other keys are not used). Note that this can cause installations to fail if required prerequisites are not available.

--purge_on_delete PURGEONDELETE

Optional

Sets the purgeOnDelete option for the deployment. Defaults to True

--include_beta INCLUDEBETA

Optional

Install the most recent release, even if beta. Defaults to False. This option is only supported for scratch orgs, to avoid installing a package that can’t be upgraded in persistent orgs.

--allow_newer ALLOWNEWER

Optional

Deprecated. This option has no effect.

--prefer_2gp_from_release_branch PREFER2GPFROMRELEASEBRANCH

Optional

If True and this build is on a release branch (feature/NNN, where NNN is an integer), or a child branch of a release branch, resolve GitHub managed package dependencies to 2GP builds present on a matching release branch on the dependency.

--resolution_strategy RESOLUTIONSTRATEGY

Optional

The name of a sequence of resolution_strategy (from project__dependency_resolutions) to apply to dynamic dependencies.

--packages_only PACKAGESONLY

Optional

Install only packaged dependencies. Ignore all unmanaged metadata. Defaults to False.

--security_type SECURITYTYPE

Optional

Which Profiles to install packages for (FULL = all profiles, NONE = admins only, PUSH = no profiles, CUSTOM = custom profiles). Defaults to FULL.

--name_conflict_resolution NAMECONFLICTRESOLUTION

Optional

Specify how to resolve name conflicts when installing an Unlocked Package. Available values are Block and RenameMetadata. Defaults to Block.

--activate_remote_site_settings ACTIVATEREMOTESITESETTINGS

Optional

Activate Remote Site Settings when installing a package. Defaults to True.

update_metadata_first_child_text¶

Description: Updates the text of the first child of Metadata with matching tag. Adds a child for tag if it does not exist.

Class: cumulusci.tasks.metadata_etl.UpdateMetadataFirstChildTextTask

Metadata ETL task to update a single child element’s text within metadata XML.

If the child doesn’t exist, the child is created and appended to the Metadata. Furthermore, the value option is namespaced injected if the task is properly configured.

Example: Assign a Custom Object’s Compact Layout¶

tasks:
    assign_compact_layout:
        class_path: cumulusci.tasks.metadata_etl.UpdateMetadataFirstChildTextTask
        options:
            managed: False
            namespace_inject: $project_config.project__package__namespace
            entity: CustomObject
            api_names: OurCustomObject__c
            tag: compactLayoutAssignment
            value: "%%%NAMESPACE%%%DifferentCompactLayout"
            # We include a namespace token so it's easy to use this task in a managed context.

Suppose the original CustomObject metadata XML looks like:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
    ...
    <label>Our Custom Object</label>
    <compactLayoutAssignment>OriginalCompactLayout</compactLayoutAssignment>
    ...
</CustomObject>

After running cci task run assign_compact_layout, the CustomObject metadata XML is deployed as:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
    ...
    <label>Our Custom Object</label>
    <compactLayoutAssignment>DifferentCompactLayout</compactLayoutAssignment>
    ...
</CustomObject>

Command Syntax¶

$ cci task run update_metadata_first_child_text

Options¶

--metadata_type METADATATYPE

Required

Metadata Type

--tag TAG

Required

Targeted tag. The text of the first instance of this tag within the metadata entity will be updated.

--value VALUE

Required

Desired value to set for the targeted tag’s text. This value is namespace-injected.

--api_names APINAMES

Optional

List of API names of entities to affect

--managed MANAGED

Optional

If False, changes namespace_inject to replace tokens with a blank string

--namespace_inject NAMESPACEINJECT

Optional

If set, the namespace tokens in files and filenames are replaced with the namespace’s prefix

Default: $project_config.project__package__namespace

--api_version APIVERSION

Optional

Metadata API version to use, if not project__package__api_version.

update_package_xml¶

Description: Updates src/package.xml with metadata in src/

Class: cumulusci.tasks.metadata.package.UpdatePackageXml

Command Syntax¶

$ cci task run update_package_xml

Options¶

--path PATH

Required

The path to a folder of metadata to build the package.xml from

Default: src

--output OUTPUT

Optional

The output file, defaults to <path>/package.xml

--package_name PACKAGENAME

Optional

If set, overrides the package name inserted into the <fullName> element

--managed MANAGED

Optional

If True, generate a package.xml for deployment to the managed package packaging org

--delete DELETE

Optional

If True, generate a package.xml for use as a destructiveChanges.xml file for deleting metadata

upload_beta¶

Description: Uploads a beta release of the metadata currently in the packaging org

Class: cumulusci.tasks.salesforce.PackageUpload

Command Syntax¶

$ cci task run upload_beta

Options¶

--name NAME

Required

The name of the package version.

--production PRODUCTION

Optional

If True, uploads a production release. Defaults to uploading a beta

--description DESCRIPTION

Optional

A description of the package and what this version contains.

--password PASSWORD

Optional

An optional password for sharing the package privately with anyone who has the password. Don’t enter a password if you want to make the package available to anyone on AppExchange and share your package publicly.

--post_install_url POSTINSTALLURL

Optional

The fully-qualified URL of the post-installation instructions. Instructions are shown as a link after installation and are available from the package detail view.

--release_notes_url RELEASENOTESURL

Optional

The fully-qualified URL of the package release notes. Release notes are shown as a link during the installation process and are available from the package detail view after installation.

--namespace NAMESPACE

Optional

The namespace of the package. Defaults to project__package__namespace

--resolution_strategy RESOLUTIONSTRATEGY

Optional

The name of a sequence of resolution_strategy (from project__dependency_resolutions) to apply to dynamic dependencies. Defaults to ‘production’.

upload_production¶

Description: Uploads a production release of the metadata currently in the packaging org

Class: cumulusci.tasks.salesforce.PackageUpload

Command Syntax¶

$ cci task run upload_production

Options¶

--name NAME

Required

The name of the package version.

Default: Release

--production PRODUCTION

Optional

If True, uploads a production release. Defaults to uploading a beta

Default: True

--description DESCRIPTION

Optional

A description of the package and what this version contains.

--password PASSWORD

Optional

--post_install_url POSTINSTALLURL

Optional

The fully-qualified URL of the post-installation instructions. Instructions are shown as a link after installation and are available from the package detail view.

--release_notes_url RELEASENOTESURL

Optional

The fully-qualified URL of the package release notes. Release notes are shown as a link during the installation process and are available from the package detail view after installation.

--namespace NAMESPACE

Optional

The namespace of the package. Defaults to project__package__namespace

--resolution_strategy RESOLUTIONSTRATEGY

Optional

The name of a sequence of resolution_strategy (from project__dependency_resolutions) to apply to dynamic dependencies. Defaults to ‘production’.

upload_user_profile_photo¶

Description: Uploads a profile photo for a specified or default User.

Class: cumulusci.tasks.salesforce.users.photos.UploadProfilePhoto

Uploads a profile photo for a specified or default User.

Examples¶

Upload a profile photo for the default user.

tasks:
    upload_profile_photo_default:
        group: Internal storytelling data
        class_path: cumulusci.tasks.salesforce.users.UploadProfilePhoto
        description: Uploads a profile photo for the default user.
        options:
            photo: storytelling/photos/default.png

Upload a profile photo for a user whose Alias equals grace or walker, is active, and created today.

tasks:
    upload_profile_photo_grace:
        group: Internal storytelling data
        class_path: cumulusci.tasks.salesforce.users.UploadProfilePhoto
        description: Uploads a profile photo for Grace.
        options:
            photo: storytelling/photos/grace.png
            where: (Alias = 'grace' OR Alias = 'walker') AND IsActive = true AND CreatedDate = TODAY

Command Syntax¶

$ cci task run upload_user_profile_photo

Options¶

--photo PHOTO

Required

Path to user’s profile photo.

--where WHERE

Optional

WHERE clause used querying for which User to upload the profile photo for.

No need to prefix with WHERE
The SOQL query must return one and only one User record.
If no “where” is supplied, uploads the photo for the org’s default User.

util_sleep¶

Description: Sleeps for N seconds

Class: cumulusci.tasks.util.Sleep

Command Syntax¶

$ cci task run util_sleep

Options¶

--seconds SECONDS

Required

The number of seconds to sleep

Default: 5

log¶

Description: Log a line at the info level.

Class: cumulusci.tasks.util.LogLine

Command Syntax¶

$ cci task run log

Options¶

--level LEVEL

Required

The logger level to use

Default: info

--line LINE

Required

A formatstring like line to log

--format_vars FORMATVARS

Optional

A Dict of format vars

generate_dataset_mapping¶

Description: Create a mapping for extracting data from an org.

Class: cumulusci.tasks.bulkdata.GenerateMapping

Generate a mapping file for use with the extract_dataset and load_dataset tasks. This task will examine the schema in the specified org and attempt to infer a mapping suitable for extracting data in packaged and custom objects as well as customized standard objects.

Mappings must be serializable, and hence must resolve reference cycles - situations where Object A refers to B, and B also refers to A. Mapping generation will stop and request user input to resolve such cycles by identifying the correct load order. If you would rather the mapping generator break such a cycle randomly, set the break_cycles option to auto.

Alternately, specify the ignore option with the name of one of the lookup fields to suppress it and break the cycle. ignore can be specified as a list in cumulusci.yml or as a comma-separated string at the command line.

In most cases, the mapping generated will need minor tweaking by the user. Note that the mapping omits features that are not currently well supported by the extract_dataset and load_dataset tasks, such as references to the User object.

Command Syntax¶

$ cci task run generate_dataset_mapping

Options¶

--path PATH

Required

Location to write the mapping file

Default: datasets/mapping.yml

--namespace_prefix NAMESPACEPREFIX

Optional

The namespace prefix to use

Default: $project_config.project__package__namespace

--ignore IGNORE

Optional

Object API names, or fields in Object.Field format, to ignore

--break_cycles BREAKCYCLES

Optional

If the generator is unsure of the order to load, what to do? Set to ask (the default) to allow the user to choose or auto to pick randomly.

--include INCLUDE

Optional

Object names to include even if they might not otherwise be included.

--strip_namespace STRIPNAMESPACE

Optional

If True, CumulusCI removes the project’s namespace where found in fields and objects to support automatic namespace injection. On by default.

extract_dataset¶

Description: Extract a sample dataset using the bulk API.

Class: cumulusci.tasks.bulkdata.ExtractData

Command Syntax¶

$ cci task run extract_dataset

Options¶

--mapping MAPPING

Required

The path to a yaml file containing mappings of the database fields to Salesforce object fields

Default: datasets/mapping.yml

--database_url DATABASEURL

Optional

A DATABASE_URL where the query output should be written

--sql_path SQLPATH

Optional

If set, an SQL script will be generated at the path provided This is useful for keeping data in the repository and allowing diffs.

Default: datasets/sample.sql

--inject_namespaces INJECTNAMESPACES

Optional

If True, the package namespace prefix will be automatically added to (or removed from) objects and fields based on the name used in the org. Defaults to True.

--drop_missing_schema DROPMISSINGSCHEMA

Optional

Set to True to skip any missing objects or fields instead of stopping with an error.

load_dataset¶

Description: Load a sample dataset using the bulk API.

Class: cumulusci.tasks.bulkdata.LoadData

Command Syntax¶

$ cci task run load_dataset

Options¶

--database_url DATABASEURL

Optional

The database url to a database containing the test data to load

--mapping MAPPING

Optional

The path to a yaml file containing mappings of the database fields to Salesforce object fields

Default: datasets/mapping.yml

--start_step STARTSTEP

Optional

If specified, skip steps before this one in the mapping

--sql_path SQLPATH

Optional

If specified, a database will be created from an SQL script at the provided path

Default: datasets/sample.sql

--ignore_row_errors IGNOREROWERRORS

Optional

If True, allow the load to continue even if individual rows fail to load.

--reset_oids RESETOIDS

Optional

If True (the default), and the _sf_ids tables exist, reset them before continuing.

--bulk_mode BULKMODE

Optional

Set to Serial to force serial mode on all jobs. Parallel is the default.

--inject_namespaces INJECTNAMESPACES

Optional

If True, the package namespace prefix will be automatically added to (or removed from) objects and fields based on the name used in the org. Defaults to True.

--drop_missing_schema DROPMISSINGSCHEMA

Optional

Set to True to skip any missing objects or fields instead of stopping with an error.

--set_recently_viewed SETRECENTLYVIEWED

Optional

load_custom_settings¶

Description: Load Custom Settings specified in a YAML file to the target org

Class: cumulusci.tasks.salesforce.LoadCustomSettings

Command Syntax¶

$ cci task run load_custom_settings

Options¶

--settings_path SETTINGSPATH

Required

The path to a YAML settings file

remove_metadata_xml_elements¶

Description: Remove specified XML elements from one or more metadata files

Class: cumulusci.tasks.metadata.modify.RemoveElementsXPath

Command Syntax¶

$ cci task run remove_metadata_xml_elements

Options¶

--xpath XPATH

Optional

An XPath specification of elements to remove. Supports the re: regexp function namespace. As in re:match(text(), ‘.*__c’)Use ns: to refer to the Salesforce namespace for metadata elements.for example: ./ns:Layout/ns:relatedLists (one-level) or //ns:relatedLists (recursive)Many advanced examples are available here: https://github.com/SalesforceFoundation/NPSP/blob/26b585409720e2004f5b7785a56e57498796619f/cumulusci.yml#L342

--path PATH

Optional

A path to the files to change. Supports wildcards including ** for directory recursion. More info on the details: https://www.poftut.com/python-glob-function-to-match-path-directory-file-names-with-examples/ https://www.tutorialspoint.com/How-to-use-Glob-function-to-find-files-recursively-in-Python

--elements ELEMENTS

Optional

A list of dictionaries containing path and xpath keys. Multiple dictionaries can be passed in the list to run multiple removal queries in the same task. This parameter is intended for usages invoked as part of a cumulusci.yml .

--chdir CHDIR

Optional

Change the current directory before running the replace

disable_tdtm_trigger_handlers¶

Description: Disable specified TDTM trigger handlers

Class: cumulusci.tasks.salesforce.trigger_handlers.SetTDTMHandlerStatus

Command Syntax¶

$ cci task run disable_tdtm_trigger_handlers

Options¶

--handlers HANDLERS

Optional

List of Trigger Handlers (by Class, Object, or ‘Class:Object’) to affect (defaults to all handlers).

--namespace NAMESPACE

Optional

The namespace of the Trigger Handler object (‘eda’ or ‘npsp’). The task will apply the namespace if needed.

--active ACTIVE

Optional

True or False to activate or deactivate trigger handlers.

--restore_file RESTOREFILE

Optional

Path to the state file to store or restore the current trigger handler state. Set to False to discard trigger state information. By default the state is cached in an org-specific directory for later restore.

--restore RESTORE

Optional

If True, restore the state of Trigger Handlers to that stored in the (specified or default) restore file.

restore_tdtm_trigger_handlers¶

Description: Restore status of TDTM trigger handlers

Class: cumulusci.tasks.salesforce.trigger_handlers.SetTDTMHandlerStatus

Command Syntax¶

$ cci task run restore_tdtm_trigger_handlers

Options¶

--handlers HANDLERS

Optional

List of Trigger Handlers (by Class, Object, or ‘Class:Object’) to affect (defaults to all handlers).

--namespace NAMESPACE

Optional

The namespace of the Trigger Handler object (‘eda’ or ‘npsp’). The task will apply the namespace if needed.

--active ACTIVE

Optional

True or False to activate or deactivate trigger handlers.

--restore_file RESTOREFILE

Optional

--restore RESTORE

Optional

If True, restore the state of Trigger Handlers to that stored in the (specified or default) restore file.

Default: True

Tasks Reference¶

activate_flow¶

Command Syntax¶

Options¶

add_page_layout_related_lists¶

Command Syntax¶

Options¶

add_page_layout_fields¶

Command Syntax¶

Options¶

add_standard_value_set_entries¶

Command Syntax¶

Options¶

add_picklist_entries¶

Command Syntax¶

Options¶

add_fields_to_field_set¶

Command Syntax¶

Options¶

add_permission_set_perms¶

Command Syntax¶

Options¶

add_record_action_list_item¶

Command Syntax¶

Options¶

assign_compact_layout¶

Example: Assign a Custom Object’s Compact Layout¶

Command Syntax¶

Options¶

assign_permission_sets¶

Command Syntax¶

Options¶

assign_permission_set_groups¶

Command Syntax¶

Options¶

assign_permission_set_licenses¶

Command Syntax¶

Options¶

batch_apex_wait¶

Command Syntax¶

Options¶

check_my_domain_active¶

Command Syntax¶

check_sobjects_available¶

Command Syntax¶

check_sobject_permissions¶

Command Syntax¶

Options¶

check_advanced_currency_management¶

Command Syntax¶

Options¶

check_org_wide_defaults¶

Command Syntax¶

Options¶

check_org_settings_value¶

Command Syntax¶

Options¶

check_chatter_enabled¶

Command Syntax¶

Options¶

check_enhanced_notes_enabled¶

Command Syntax¶

Options¶

custom_settings_value_wait¶

Command Syntax¶

Options¶

command¶

Command Syntax¶

Options¶

composite_request¶

Example Task Definition¶

Command Syntax¶

Options¶

create_community¶

Command Syntax¶

Options¶

connected_app¶

Command Syntax¶

Options¶

create_network_member_groups¶