[Apex Launcher Classic Pro V3.3.8 Apk
Jamar Lizarraga
A few weeks ago we soft-launched a load_data feature that matched the dataset loaded to the org_shape. If you had discovered and used the load_data option called org_shape_match_only, you should switch to the new task because eventually we will remove the option and only use the new load_sample_data task. (#3455)
The retrieve_changes and list_changes tasks now properly exclude metadata types that SFDX is unable to process. These include: AuraDefinition, ExperienceResource, and LightningComponentResource by @jstvz in -Tooling/CumulusCI/pull/3443
Upgraded Robot Framework from version 4.1.3 to version 6. As with most Robot Framework updates, there are a host of new features and a few deprecated features and backwards incompatibilities. For a complete list consult the Robot Framework release notes in -Tooling/CumulusCI/pull/3417
There is a new Playwright-based keyword Wait until salesforce is ready. This keyword is automatically called by the Open Test Browser keyword in the SalesforcePlaywright library. In addition to waiting for the page to be rendered, it will auto attempt to detect a classic page on initial render, and automatically switch to a lightning page if one is detected.(#3387)
The following Robot Framework keywords now automatically generate screenshots on failure: Click related list button, Click related item popup link, Close modal, Current app should be, Field value should be, Get field value, Populate field, Populate lookup field, and Wait until modal is closed. (#3370)
Added new robot keywords available when using the SalesforcePlaywright library; get current record id, wait until loading is complete and go to record home. These keywords work in a similar fashion to the existing keywords of the same name that are based on Selenium - by @boakley in (#3310)
Robot framework API and performance keywords have been moved into separate libraries. They are still automatically imported when using Salesforce.robot so it is not necessary to modify any existing test files. (#3216)
There are new robot framework keyword libraries with limited support for Playwright _ via the robotframework-browser library _. To use, import the resource file cumulusci/robotframework/SalesforcePlaywright.robot instead of cumulusci/robotframework/Salesforce.robot. Note, Playwright is not yet supported by MetaCI. (#3216)
Fixed a regression relating to lookup of variables like $project_config.repo_branch. Identified as a problem in the github_automerge_main task, but potentially there might be other tasks that were broken and are fixed by this branch. (#3220)
CumulusCI now provides an option to verify server certificates usingroot CA certs loaded from the system, instead of the default set ofCA certs bundled with the Python requests library. This isconsidered experimental, so must be opted in by setting theCUMULUSCI_SYSTEM_CERTS environment variable to True (#3114)
Improvements to the custom locator strategy used by the RobotFramework keyword input form data to find form fields andlightning components based on label text. This locator strategy(label:) is now up to 10x faster at finding non-lightning formcomponents, and is able to find elements with more complicatedlabels (eg: labels with text inside of nested spans). (#3117)
Robot Framework tests can now pass a locator when callingGo To Page for one of our bulit-in page objects (Listing, Detail,Home), and the keyword will wait until that locator is visible. Thisis mostly useful for custom pages where you need to wait for aniframe or custom component to be available. (#3098)
CumulusCI now ships with Snowfakery 3.0. See the Snowfakery releasenotes.Snowfakery 3.0 ships with opt-in features that will become thedefault in June 2022; please test yourrecipesnow with snowfakery_version: 3 to ensure compatibility.
The marketing_cloud_create_user task now creates an unlockeduser with a notification email address so that it is possiblefor the user to log in. This task also has a new option,activate_if_existing, which can be set to true to ensurethat if the user already exists in an inactive state, it will beactivated. (#3040)
Fixed a bug that prevented Get webelements from returning an emptylist if the locator was a custom locator created via theregister_locators function ofcumulusci.robotframework.locator_manager. (#3004)
The dx_convert_from task now uses a custom Python task classinstead of cumulusci.tasks.sfdx.SFDXBaseTask. In most cases thiswill have no visible impact, but if you have customized this taskconfig to change the command option, make sure you have alsoexplicitly set its class_path tocumulusci.tasks.sfdx.SFDXBaseTask. (#2981)
We also fixed a minor inconsistency in defaulting theactivate_remote_site_settings (or formerly activateRSS) option.Projects that define custom tasks based on theInstallPackageVersion class should ensure they explicitly set theactivate_remote_site_settings option, or accept the new default ofTrue.
MetaDeploy install plans now do not freeze defaulted packageinstall options. If your install plans are dependent on specificinstall options, we recommend explicitly specifying them. Installplans without explicit options will use the defaults at the time ofexecution.
The sources feature, which allows CumulusCI projects to consumeautomation from other projects, now supports specifying aresolution_strategy, just like dependencies. Sources can nowresolve to the same GitHub refs as corresponding dependencies,including branch matching. The default behavior is to use theproduction resolution strategy. (#2807)
The uninstall_packaged_incremental task now defaults to ignoringnon-deletable CustomObjectTranslation metadata. If your projectcustomizes the ignore_types option onuninstall_packaged_incremental, we recommend you addCustomObjectTranslation to this option. (#2790)
The create_package_version task no longer creates UnlockedPackages from the unpackaged/pre and unpackaged/post directoriesof dependencies, or local unpackaged/pre directories by default.This behavior is now opt-in via thecreate_unlocked_dependency_packages option, which defaults toFalse. Projects using the old default behavior must explicitly setthis option. We believe the new behavior is a more sane default formost 2GP projects. (#2741)
Fixed an issue where CumulusCI did not grant permissions to CustomTabs when running update_admin_profile without a custompackage.xml. Projects that use a custom package.xml withupdate_admin_profile should update their manifest to include aCustomTab wildcard for the same outcome. (#2699)
The built-in connected app that CumulusCI uses by default is nowvisible in the output of the cci service list command. This makesit possible to switch back and forth between this connected app andanother one as the current default when multiple connected_appservices are configured. The built-in connected_app service has thename built-in and cannot be renamed or removed. (#2664)
The update_dependencies task now guarantees to resolve unpackagedmetadata directories (subdirectories of unpackaged/pre andunpackaged/post) in alphabetical order, matching the behavior ofdeploy_pre and deploy_post. unpackaged/pre/bar will deployprior to unpackaged/pre/foo. The previous behavior was undefined,which caused rare problems. This change is critical only forprojects that have deployment-order dependencies between unpackageddirectories located in upstream dependencies and rely on the currentundefined load order. (#2588)
The oauth2_client service takes information for an individualOAuth2 client which can then be used in place of the default client.This currently applies only to the marketing_cloud service. Tosetup a Marketing Cloud service with a specific OAuth2 client use:cci service connect marketing-cloud --oauth_client .(#2602)
CumulusCI has a new task: deploy_marketing_cloud_package. Thistask allows a user to pass the path to a .zip file to a MarketingCloud package (downloaded from the Marketing Cloud Package Manager)and deploy the package via a marketing_cloud service (see above).Note that successfully deploying a package using this task mayrequire permissions that are not generally available. (#2602)
The update_dependencies task now supports a packages_onlyoption, which suppresses the installation of unpackaged metadatadependencies. This option is intended to support buildingupdate-only or idempotent installers. (#2587)
Added an new option set_recently_viewed to the load_dataset taskthat sets newly inserted data as recently viewed. This changes thedefault behavior. By default (if you do not specify the option), thefirst 1000 records inserted via the Bulk API will be set as recentlyviewed. If fewer than 1000 records are inserted, existing objects ofthe same type being inserted will also be set as recently viewed.(#2578)
Improved logging of errors from sfdx while converting sfdx formatmetadata to deploy via the Metadata API, so that they are not lostwhen CumulusCI is embedded in another system like MetaCI or Metecho.(#2574)
would always deploy from the latest commit on the defaultbranch. Now, this dependency will be resolved to a GitHub commitjust like a dependency without a subfolder, selecting the latestbeta or production release as determined by the chosenresolution strategy.
CumulusCI now supports named services! This means you can configuremultiple services of the same type under different names. If yourun cci service list you will note that your existing globalservices will have the name global, and any project-specificservices will have the name project_name. (#2499)
The push_sandbox and push_all tasks now default to includingall orgs whose status is not Inactive, rather than only orgswith a status of Active. This means that sandboxes, scratchorgs, and Developer Edition orgs are included. (#2338)
The create_package_version task has a new option, version_base,which can be used to increment the package version from a differentbase version instead of from the highest existing version of the 2gppackage. The build_feature_test_package flow now uses this optionto create a package version with the minor version incremented fromthe most recent 1gp release published to github. ##2357
795a8134c1