7.6.0

[JoernBerkefeld]

Release details

Checklist

Before merge

• Wiki updated with info in ticket listed under Documentation
• ran npm run prepare-release (which runs npm audit fix, npm run lint-ts, npm run lint:fix, git add, git commit)
• pushed potential changes made by prepare-release

After merge

• merged all dependabot PRs that target main branch
• updated bug template to include the new version
• updated .mcdevrc for tests to the new version
• ran npm run version:major/minor/patch
• pushed version-prep commits
• merged main branch into develop branch
• closed GitHub milestone
• created new GitHub Release

Documentation

• [FEATURE] enhance pause and resume journey to support transactional send journeys #1746 / feature/1746 support pause and resume for transactional send journeys #1765
  no changes needed.

• [FEATURE] reroute stop journey to pause for transactional send journeys #1919 / feature/1919 reroute stop journey to pause journey for transactional send journeys #1920
  no changes needed.

• [FEATURE] support refresh for journeys (transactional + multi-step) #1921 / feature/1921 support refresh for journeys (transactional + multi-step) #1922

#1939 (comment)

• [FEATURE] stop all versions of a multi-step journey at once #1879 / feature/1879 Allow stopping all versions of a multi-step journey #1929

#1939 (comment)

Issues

• closes [FEATURE] enhance pause and resume journey to support transactional send journeys #1746
• closes [TASK] set journey + transactionalEmail maxKeyLength #1882
• closes [TASK] hint for --ignoreSfFields option if the corresponding error pops up #1880
• closes [BUG] gracefully handle journey-key-not-found #1881
• closes [BUG] Running mcdev build with just metadata type doesn't return anything #1774
• closes [BUG] throttle mcdev refresh to avoid timeouts #1889
• closes [BUG] trying to delete a dataExtension that doesn't exist returns ambiguous error #1914
• closes [BUG] deleting dataExtensionField with ":" in name does not work #1916
• closes [FEATURE] reroute stop journey to pause for transactional send journeys #1919
• closes [FEATURE] support refresh for journeys (transactional + multi-step) #1921
• closes [FEATURE] stop all versions of a multi-step journey at once #1879
• closes [BUG] transactional send journeys cannot be versioned or updated if active/published #1836
• closes [BUG] deleting transactional send journey only without version #1837

[github-actions]

Coverage Report

Commit:86606ea
Base: main@fefd959

Type	Base	This PR
Total Statements Coverage	69.73%	69.08%  (-0.65%)
Total Branches Coverage	68.98%	68.92%  (-0.06%)
Total Functions Coverage	81.87%	81.63%  (-0.24%)
Total Lines Coverage	69.73%	69.08%  (-0.65%)

Details (changed files):

File	Statements	Branches	Functions	Lines

[JoernBerkefeld]

• [FEATURE] support refresh for journeys (transactional + multi-step) #1921 / feature/1921 support refresh for journeys (transactional + multi-step) #1922
• https://github.com/Accenture/sfmc-devtools/wiki/06.b-~-Standard-Commands/_edit

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

[JoernBerkefeld]

• [FEATURE] stop all versions of a multi-step journey at once #1879 / feature/1879 Allow stopping all versions of a multi-step journey #1929

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/*