You are viewing limited content. For full access, please sign in.

Question

Question

Importing Template Security

asked on September 12, 2017

Does anyone have a good workaround for importing template security between environments?  If I put security on a template (by AD groups) in my Dev environment and I export the XML of the template, the security does not come with it.

When I import it into my Test environment, I have to reset all the security.  Then when the software admin moves it to the Production environment, they have to reset all the security again.

Any thoughts?

Thanks.

0 0

Replies

replied on September 13, 2017 Show version history

Hi Jennifer,

According to the Administration Guide:

Copying or Importing Fields, Templates, Tags, and Other Metadata Objects

You can create a copy of any metadata object -- templates, fields, tags, or document relationships -- in the same repository or in a different repository, either by copying and pasting the object or by exporting the object and importing it at a later time. The copy of the metadata object will retain the same settings as the original user or group with the following exceptions:

  • Only the metadata definition will be exported. The list of entries to which it was applied will not be included.  For example, a field will retain all of its properties, but will not retain a list of documents to which it was applied, or the values stored in it for those documents.
  • Security will not be included. For example, an exported template's template security will not be retained.

 

I hope this helps!

~Rob 

0 0
replied on September 13, 2017

Thanks.  I knew it doesn't come over.  Was hoping someone had a "hack" or work around.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.