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

SOLVED

Hide OOTB Content Templates

jchapman-CC-82
Level 2
Level 2

We are working on finishing our setup for Adobe Campaign Standard, but cannot figure out how to hide/remove all of the OOTB templates that come with the system by default since they are all locked. Without having edit access to these templates, we cannot change them, remove them, or hide them through an Org Unit and security.

 

We were advised by our support team that we would need to write a workflow to force them in to an Org Unit and just make sure none of our users have access to that Org Unit. We set up an org unit of 'adobe_defaults' that we are trying to force them in to using a workflow, but no matter what we do, the workflow just errors out. 

 

Has anyone had to do this? If so, what is the best method to get rid of the OOTB content templates from our Production instance? We have a Dev instance where we will keep all of them so we have a base to work from if we ever need templates like the ones Adobe has already built.

 

To hopefully help, here's the workflow step to update the template and the error:

 

Screen Shot 2020-11-09 at 17.20.42.pngScreen Shot 2020-11-09 at 17.20.23.png

1 Accepted Solution
ramon_bisswanger
Correct answer by
Employee
Employee

Yes, using a technical workflow to assign them to another org unit would be an option to hide it.

Note: a new ACS release may revert this assignment, so you may need to rerun it from time to time or e.g. just schedule to run it once a week.

 

Workflow design:

  • Query which is fetching the content templates to hide
    • Resource = contentModel
    • Query
      • Org Unit = all
      • AND builtin = yes
    • Additional data
      • Add a constant field @orgUnitName with the name of the org unit
  • Reconiliation activity
    • Link to org unit
    • lookup @orgUnitName = name of the org unit
  • Update data
    • assign the orgUnit result from the reconiliation task to the orgUnit property of the contentModel resource

View solution in original post

7 Replies
shelly-goel
Community Advisor
Community Advisor

Hello @jchapman-CC-82 

Are you getting the same error everytime? Do you mind sharing the error you’re getting?

 

 

jchapman-CC-82
Level 2
Level 2
I just added screenshots to the post. I couldn't figure out how to add them when I posted the first time.
ramon_bisswanger
Correct answer by
Employee
Employee

Yes, using a technical workflow to assign them to another org unit would be an option to hide it.

Note: a new ACS release may revert this assignment, so you may need to rerun it from time to time or e.g. just schedule to run it once a week.

 

Workflow design:

  • Query which is fetching the content templates to hide
    • Resource = contentModel
    • Query
      • Org Unit = all
      • AND builtin = yes
    • Additional data
      • Add a constant field @orgUnitName with the name of the org unit
  • Reconiliation activity
    • Link to org unit
    • lookup @orgUnitName = name of the org unit
  • Update data
    • assign the orgUnit result from the reconiliation task to the orgUnit property of the contentModel resource

View solution in original post

shelly-goel
Community Advisor
Community Advisor

@ramon_bisswanger- I'm trying the steps provided, however getting below error in "Update Data" activity

error.png

I've set the source orgUnit with the orgUnit from reconciliation and destination orgUnit is in the contentModel

fieldToUpdate.png

 

When I check the data structure for these two orgUnit, there is a slight difference in parent field as see below. Can this be the reason for the error or am I missing something?

 

orgUnit structure

orgUnit-data-structure.png

structure of orgUnit within contentModel

orgUnit-in-contentModel-datastructure.png

 

 

 

jchapman-CC-82
Level 2
Level 2
@shelly-goel I am running in to the same issue you are. I did just try today to see if a delete works, which does not directly. But running a delete function through the workflow removed all the OOTB templates from the instance. Since I still have them in my lower environments, I have just removed them completely from our Production instance.
shelly-goel
Community Advisor
Community Advisor
@ramon_bisswanger - Got it, I left the selection as "Using Reconciliation Criteria". Changing it to "Directly using Targeting Dimension" works."