Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE] enable changeKeyVa and changeKeyField for journeys #1995

Open
JoernBerkefeld opened this issue Jan 17, 2025 · 0 comments
Open

[FEATURE] enable changeKeyVa and changeKeyField for journeys #1995

JoernBerkefeld opened this issue Jan 17, 2025 · 0 comments
Labels
c/event COMPONENT c/journey COMPONENT c/transactionalEmail enhancement New feature or request; requires increasing the minor version of mcdev. Jira issue-type "Story"
Milestone
7.7.0

Comments

@JoernBerkefeld
Copy link
Contributor

journeys cannot get a new key after creation - but we could ask the user to confirm that they want to create a duplicate journey instead with the new key. and then also ask if the old one shall be deleted.

that would make re-keying journeys a lot easier.

it should be blocked if the journey (in any version) is currently running. all journey versions should be in draft or stopped to be able to run this or else an error needs to be shown.
@JoernBerkefeld JoernBerkefeld added c/event COMPONENT c/journey COMPONENT c/transactionalEmail enhancement New feature or request; requires increasing the minor version of mcdev. Jira issue-type "Story" labels Jan 17, 2025
@JoernBerkefeld JoernBerkefeld added this to the 7.7.0 milestone Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c/event COMPONENT c/journey COMPONENT c/transactionalEmail enhancement New feature or request; requires increasing the minor version of mcdev. Jira issue-type "Story"
Projects
None yet
Milestone
7.7.0
Development

No branches or pull requests
1 participant
@JoernBerkefeld