- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 12:43 AM
Hi Experts,
I wonder why standard change templates are automatically added to an updateset. From my point of view this is not correct as they should be processed within the production environment .. . Any idea why this is set like this OOTB?
Solved! Go to Solution.
- Labels:
-
Best Practices
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 01:08 AM
It creates a configuration that requires approval. It is still configuration. i can see why people might want to be able to create a bunch of templates on dev and then move them to prod. The best way around this is to be aware of what update set you are in when you're working on dev!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 01:33 AM
Maybe its just the labelling that is confusing
If they called them Standard change record producers it might be closer to the mark. It's a new catalog item etc, You would expect that captured.
Imagine an email notification with a mail layout and an email template. You'd expect that in an update set etc
So I guess for me they go into an update set because they are legitimate configuration artefacts and should do so.
As a general rule of thumb I have the update set picker in my header bar and routine check what has gone into my update sets as I tend to be more worried about what hasn't gone into the update set. Scheduled jobs etc
