Skip to content

Releases: Accenture/sfmc-devtools

v7.10.0

10 Mar 15:13
Compare
Choose a tag to compare

Feature / breaking change

The key field of verifications has been changed to a custom value that is dependent on the automation it belongs to. This move was necessary to enable easy deployment across BUs. Unfortunately, this metadata type does not have its own key.

Chores

Full Changelog: v7.9.0...v7.10.0

v7.9.0

07 Mar 13:37
Compare
Choose a tag to compare

Features

Bugfixes

Chores

Full Changelog: v7.8.0...v7.9.0

v7.8.0

04 Mar 17:42
Compare
Choose a tag to compare

Features

Dependencies

Full Changelog: v7.7.2...v7.8.0

v7.7.2

03 Mar 13:18
Compare
Choose a tag to compare

Bugfixes

Chores

Full Changelog: v7.7.1...v7.7.2

v7.7.1

20 Feb 18:02
Compare
Choose a tag to compare

Bugfixes

Chores

Full Changelog: v7.7.0...v7.7.1

v7.7.0

13 Feb 13:56
Compare
Choose a tag to compare

Features

  • #1918 extend createDeltaPkg-command logic to understand multiple key-value pairs in the source-target-mapping; enabling you to work with multiple source BUs in one CI/CD pipeline by @JoernBerkefeld in #2045
  • #2047 extend createDeltaPkg with options from build-command: --dependencies, --retrieve, --skipValidation and add new option --range for enhanced flexibility by @JoernBerkefeld in #2053
  • #1461 add new option --purge and --no-purge to createDeltaPkg, build, buildDefinition, buildDefinitionBulk that lets you pre-select if the deploy-folder should be emptied or not by @JoernBerkefeld and @LaurisBahs in #2023
  • #1678 add --fix option to deploy, build, buildDefinition, buildDefinitionBulk, createDeltaPkg which enables auto-fixing problems that were recognized by validation rules. This is dependent on the validation rule being able to apply a fix. by @JoernBerkefeld and @anasilva105 in #2077
  • #1467 create templates only temporarily when running build-command, instead of storing templates in template/ folder. To create permanent templates, you now have to use buildTemplate instead. by @JoernBerkefeld in #2024
  • #1703 add new clone-command to easily copy a component from one BU to another without making changes to it. It internally uses build-command to ensure consistency and to allow you to use build's options like --dependencies. Contrary to build it does not use markets / market lists. by @JoernBerkefeld in #2025
  • #1989 retrieve sendClassification by default from now on by @JoernBerkefeld in #2062
  • #2031 auto-pause & resume transactional journeys during deployments to allow updating them. Before this required manual pre- and post-deployment steps by @JoernBerkefeld in #2058
  • #2064 check and auto-create new type domainVerification (From Name Management) entries for senderProfiles. This programmatically clicks on the "Verify" button next to an email address in the Sender Profile, allowing you to actually use it. by @JoernBerkefeld in #2065
  • #2067 prevent CloudPage assets (asset-asset with assetType.name == 'webpage') from being created via mcdev because those couldn't be used. CloudPages need to be created by a manual pre-deployment step due to lack of API support. by @JoernBerkefeld and @Dipasree-ghosh #2068

Bugfixes

Chores

Dependencies

Special Thanks

We thank @LaurisBahs, @PriyajitGhosh1995, @Dipasree-ghosh and @anasilva105 for their contribution to this release.

Full Changelog: v7.6.3...v7.7.0

v7.6.3

23 Jan 11:11
Compare
Choose a tag to compare

Bugfixes

Chores

Dependencies

Full Changelog: v7.6.2...v7.6.3

v7.6.2 - journey patches

14 Jan 13:25
Compare
Choose a tag to compare

Bugfixes

Chores

Dependencies

Full Changelog: v7.6.1...v7.6.2

v7.6.1

20 Dec 14:44
Compare
Choose a tag to compare

Bugfixes

Chores

Full Changelog: v7.6.0...v7.6.1

v7.6.0

19 Dec 05:05
Compare
Choose a tag to compare

Features

Bugfixes

Chores

Dependencis

Full Changelog: v7.5.0...v7.6.0

Details

Standard Commands

refresh

Command: mcdev refresh <business unit> [type] [external key] [--metadata]

Alias: mcdev re

This command lets you refresh emails in journeys and triggeredSends to ensure that updates made to the email or loaded content blocks get reflected when the emails are send out. This is only relevant is your journey is already "running" / your triggeredSend is "active".

If you do not specify keys, for triggeredSend, it will refresh all running ("Active") triggered sends on the given BU. It will also check if all dependencies for that triggered send are available to ensure it can be published & restarted after it was paused. However, if you made changes to the email that caused issues, you might still get an error, which prevents you from restarting it.

Currently supported types:

Name CLI Argument Effect
Triggered Send triggeredSend Refreshes emails in active triggeredSends and, thereby, any emails in Journeys.
Journey journey Refreshes emails in multi-step journeys (by refreshing associated triggered sends) and transactional send journeys.

Refreshing a multi-step journey will not be reflected in the journey's 'json. However, if you refresh a transactional send journey, it will affect the last modified date.

Example:

mcdev refresh MyProject/_ParentBU_ -m triggeredSend
mcdev refresh MyProject/_ParentBU_ -m triggeredSend:myTsKey

mcdev refresh MyProject/_ParentBU_ -m journey:key1 journey:key2

stop

Command: mcdev stop <business unit> [type] [key] [--like] [--metadata]

Alias: -

This command lets you stop metadata of a given type and key.

Currently supported types:

Name CLI Argument Effect
Journey journey stops running journey

For journeys you can choose to specify a specific version to stop by appending "/4" (to stop version 4). If you do not append a version, mcdev will attempt to stop the latest version. Alternatively, you can stop all versions by appending "/*".

Example (stopping highest version):

mcdev stop MyProject/DEV -m journey:keyA journey:keyB journey:keyC

Example (stopping specific version):

mcdev stop MyProject/DEV -m journey:keyA/3 journey:keyB/2

Example (stopping all versions):

mcdev stop MyProject/DEV -m journey:keyC/*

stop with --like operator:

Instead of specifying a key, you can use the --like option to find your target. This is equal to not specifying a version and will default to the highest version.

mcdev stop MyProject/DEV -m journey --like.key "myprefix_%"
mcdev stop MyProject/DEV -m journey --like.key "myprefix_%" --like.r__folder_Path "my Journeys/Testing%"

stop on all BUs:

This variation of the stop command allows you to stop specified items on all BUs. mcdev will look for the items of defined types and keys on all BUs and stop them.

Example:

mcdev stop MyProject/* -m journey:keyA journey:keyB
mcdev stop MyProject/* -m journey:keyA/2 journey:keyB/3
mcdev stop MyProject/* -m journey:keyA/* journey:keyB/*