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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Allow existing admin / user deletion without stopping the associated running workflows

Avatar

Avatar
Affirm 1
Level 4
ihm185
Level 4

Likes

24 likes

Total Posts

52 posts

Correct reply

1 solution
Top badges earned
Affirm 1
Give Back 25
Ignite 10
Give Back 10
Ignite 5
View profile

Avatar
Affirm 1
Level 4
ihm185
Level 4

Likes

24 likes

Total Posts

52 posts

Correct reply

1 solution
Top badges earned
Affirm 1
Give Back 25
Ignite 10
Give Back 10
Ignite 5
View profile
ihm185
Level 4

11-07-2019

Hi Adobe Team,

this is a recurring issue which we face in our Adobe Campaign Classic instance. Whenever a user or admin leaves our organization, as per the standard protocol we have to restrict all access of that user. This applies to ACC access as well. Hence we are required to delete ACC account of that user. But in case of ACC we are unable to do that. During the tenure of any ACC user or admin there are a couple of workflows which has their ownership. So, when we delete that user, all the workflows associated with that user halt making our BAU activities very difficult. It's a hard procedure to find and fix.

If we can assign a default admin who will be assigned all the workflows which have a dependency on the deleted users. In this way, we can delete users without crippling the running workflows. This will ease the process a lot.

Thank you for reading.

Kind regards,

Imran

4 Comments

Avatar

Avatar
Give Back
Level 2
jaxtr
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
Boost 1
View profile

Avatar
Give Back
Level 2
jaxtr
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
Boost 1
View profile
jaxtr
Level 2

30-07-2019

Alternatively, Moving forward you can set a process in your organization to use a AdminGroup as a supervisor of all the workflows/campaigns.

This should solve the problem. Or when a user is leaving the organization just ask them to update the supervisor.

Thanks

Avatar

Avatar
Ignite 10
Level 3
yetanother_andrey
Level 3

Likes

18 likes

Total Posts

31 posts

Correct reply

1 solution
Top badges earned
Ignite 10
Give Back 10
Ignite 5
Ignite 3
Give Back 5
View profile

Avatar
Ignite 10
Level 3
yetanother_andrey
Level 3

Likes

18 likes

Total Posts

31 posts

Correct reply

1 solution
Top badges earned
Ignite 10
Give Back 10
Ignite 5
Ignite 3
Give Back 5
View profile
yetanother_andrey
Level 3

06-08-2019

Could this work (hadn't tested yet): SetLogin ?

Avatar

Avatar
Ignite 10
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Ignite 10
Give Back 10
Ignite 5
Validate 1
Ignite 3
View profile

Avatar
Ignite 10
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Ignite 10
Give Back 10
Ignite 5
Validate 1
Ignite 3
View profile
subhajit9830660
Level 3

06-08-2019

For running workflows (mainly the scheduled ones, with external signals) the corresponding operator relation is stored in the table xtk:workflowLogin. Whenever an operator needs to to be deleted, you can just run a query on this table for any references of this operator and then update the record with a different one.

Avatar

Avatar
Affirm 1
Level 4
ihm185
Level 4

Likes

24 likes

Total Posts

52 posts

Correct reply

1 solution
Top badges earned
Affirm 1
Give Back 25
Ignite 10
Give Back 10
Ignite 5
View profile

Avatar
Affirm 1
Level 4
ihm185
Level 4

Likes

24 likes

Total Posts

52 posts

Correct reply

1 solution
Top badges earned
Affirm 1
Give Back 25
Ignite 10
Give Back 10
Ignite 5
View profile
ihm185
Level 4

13-08-2019

Thank you Subhojit. I ll try that.