Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Simplify the flow for deleting rules/data elements/extensions in Launch

Avatar

Avatar
Validate 1
MVP
Jennifer_Kunz
MVP

Likes

313 likes

Total Posts

85 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Contributor
Seeker
Shape 10
Shape 1
View profile

Avatar
Validate 1
MVP
Jennifer_Kunz
MVP

Likes

313 likes

Total Posts

85 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Contributor
Seeker
Shape 10
Shape 1
View profile
Jennifer_Kunz
MVP

04-06-2018

The flow for deleting changes in Launch feels a bit overly complicated, especially for changes that only currently exist in one dev library.

First, I get this prompt:

1501496_pastedImage_2.png

But if I say yes, I then get this prompt:

1501497_pastedImage_3.png

Then I have to go to the library, find that specific change/revision, and unselect it.

At bare minimum, it'd be nice to not get the first prompt asking if I want to delete it if, in fact, I can't delete it. Or, if I get the "delete failed prompt" instead of sending me along to the library to find the change, it gave me the option to disable and delete it right there.
But generally, if I am trying to delete something, it's because I want it to be disabled and removed. I know it's in use by a library, that's what I'm trying to solve for. It would be great if the deletion flow more closely resembled DTM- a deletion counts as a change that needs approval, etc, just like addition/editing changes.

icebox
3 Comments

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

142 likes

Total Posts

317 posts

Correct Reply

83 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

142 likes

Total Posts

317 posts

Correct Reply

83 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

22-10-2018

I agree that having a deletion be a change that needs to be published like any other change would be the simplest way to manage that.  The technical guts of accomplishing that (states of being marked for deletion without actually being deleted) is more than what we wanted to take on for a first phase.  There are a lot of these workflows that are functional, but could be made a lot better when we can make the time.

Avatar

Avatar
Level 1
benjamina971369
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
benjamina971369
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
benjamina971369
Level 1

10-10-2019

I agree with Jenn. It would be nice if the deleted rules showed up in a library as well rather than just have the deleted rule disappear from Launch with no trace of when it was deleted. This would make troubleshooting much easier. Often in DTM we will use the publishing history to track down exactly when a certain rule deletion was published and this is something that you cannot currently do in Launch.

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

142 likes

Total Posts

317 posts

Correct Reply

83 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

142 likes

Total Posts

317 posts

Correct Reply

83 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

24-09-2020

 
Status changed to: Accepted