Disable Inactive users in adobe campaign standard and its impact. | Community
Skip to main content
S
shubhamborse
Level 2
September 22, 2023
Question

Disable Inactive users in adobe campaign standard and its impact.

  • September 22, 2023
  • 2 replies
  • 2687 views

Hi ,

We have some users left the organization or inactive currently in Adobe campaign Standard. We need to disable or delete them from user group. On disabling the user, workflows created by the user failed and to restart the workflows we have to stop them unconditionally and restart. 

We have large number of workflows in our instance, so is there any better way than to manually check on every such workflow and restart. We also have noticed if any workflows are modified and restarted by disable user then also workflow failed ? So, what could be better solution to avoid such cases.

Also what could be other impacts on disabling or deleting such users?

 

Thank You!

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    Craig_Thonis
    Adobe Employee
    Craig_ThonisAdobe Employee
    Adobe Employee
    September 25, 2023

    Hi Shubhamborse,

    When workflows are created, their access to the data depends on the operator's permissions that last modified the workflow. This means that a dependency is created, which requires a workflow to have an active user to function.

    The only way to handle this in bulk would be to create a workflow that queries for all workflows last modified by the soon-to-be-deactivated operator. Once identified, you can use an update activity to associate the workflows with an active user by making them the last modified user.

    To your other question, there shouldn't be any other impact with disabling or deleting other operators.

     

    Regards,

    Craig

      S
      shubhamborse_tcs
      September 25, 2023

      Hello @craig_thonis ,

       

      Thank you for your solution, we tried updating the modifiedBy or createdBy field, but we are not able to update it. May be limitation in ACS but here is what all options we tried to update those fields

      1. By querying on workflow schema, bringing modifiedby and createdBy field in additional data and putting a hardcoded value in update activity.
      2. By enriching on output of queries, where primary set (query 1) is of workflow data with additional data as modifiedBy or createdBy and other dimension (query 2) of existing active user details. We tried it with 1 cardinality simple link.

              After that Update activity included with updating dimension as “workflow”

        1. tried updating label of the user
        2. tried updating emailId of the user
        3. tried updating AdobeId of the user

      We are not able to update the dimension with this efforts.

      Do you know what value is it requiring in createdBy or modifiedBy field of a workflow data schema?

       

      Thanks,

      Shubham

       

      T
      TristanBerthon
      Level 2
      September 27, 2023

      hi @shubhamborse @shubhamborse_tcs ,

       

      this is because the user is a "linked" resource to the workflow.

       

      To make it happen, I attached a screenshot and the details below:

      - In one query: you select the workflows to update (from the Workflow resource/table). In the additional data, you need to add the "createdby" link

      - In a second query: you select the user that will replace the inactive one.

      - Add an enrichment activity (the 2 queries need to be connected to it): In advanced relations, you create a new element (1 cardinality simple link). In additional data, add the "createdby" link from the previous query

      - Add a update activity: select the Workflows resource (not Profiles). In the source, use the additional data from the previous enrichment. In the destination, select the "createdby" link (not the field) - it should be at the bottom.

       

      By running it, it should work fine. You may have to consider updating the Orgunit of the workflow in the same approach before (if the new user is not in the same Orgunit of the inactive user) as this may create conflict

      S
      shubhamborseAuthor
      Level 2
      September 28, 2023

      Hello Tristan,

       

      Thanks for the solution. We do have some questions though highlighted below..

       

      - In one query: you select the workflows to update (from the Workflow resource/table). In the additional data, you need to add the "createdby" link
      Lets Say the WKF name is 'ABC' which I want to update and the createdBy link addition means I am bringing the createdBy name of existing user who created ABC, lets say 'Tom'

       

      - In a second query: you select the user that will replace the inactive one.

      Lets say the user I want to replace Tom with is 'Jerry' So I query on user schema and bring 'Jerry' profile

       

      - Add an enrichment activity (the 2 queries need to be connected to it): In advanced relations, you create a new element (1 cardinality simple link). In additional data, add the "createdby" link from the previous query

      After adding the additional data, the createdby link will again bring 'Tom'

       

      - Add a update activity: select the Workflows resource (not Profiles). In the source, use the additional data from the previous enrichment. In the destination, select the "createdby" link (not the field) - it should be at the bottom.

      This means Source = Tom  (Additional data)

                          Destination  =  CreatedBy link of the workflow ABC

       

      So it is trying to update the same createdBy user link again.

      Is my understanding wrong?????? Or is there anything I am missing???

       

      Thanks,

      shubham

      S
      shubhamborseAuthor
      Level 2
      October 12, 2023

      Hey,

       

      It says "XSV-350046 User 'Email ID' has no organizational unit. Unable to connect". Did you check that the new user has an orgunit (it should be the case). Is the new user has the same orgUnit than the workflow? 


      Hi @tristanberthon ,

       

      The "orgUnit" is definitely not the issue. Because we made sure the orgUnit of the workflow and the new admin user are exactly same. And also to restart the workflow manually new user has to "immediately stop" the workflow and then only can restart it. To directly restart the workflow is also not possible even manually.

       

      Regards,

      Shubham

      Terms & ConditionsAccessibility statement

      Loading footer...