Paris and Templates

[bammar]

Hello All,

I wanted to provide some insight on Templates within Paris. 

• Paris Version of ServiceNow not takes into account dependecies and respects available choice values. For instance a Person setting a template up previously was able to put a Value under Subcategory that either- A. didnt exist at all in the dictionary as a subcat OR B. was not an acceptable corresponding Subcat to the Category they also had in the template.
• After Upgrade users may complain that hey my template used to work but it stopped.  Well if a user can actually manually pick the values for Cat and Subcat or whatever else stopped then we must move forward with Technical troubleshooting. If they cant select it- you advise that what they had before is unnacceptable input that ServiceNow used to allow and they must pick values that they can actually manually create on a form because the functionality before is problematic and circumvents values and dependencies.
• To Troubleshoot a situation where the values in templates are correct and can be built manually and do respect dependencies-  the key I found here when you get the error Template Applied with X conflicts  - Go tot he dictionary for the Subcat for instance- you may find the the VALUE not the label - has special characters in it.  Now i know most admins will agree its ideal to set up the Value and Label the same but in this special case condense the value down to something very simple and unique sans the special characters.
• Go back to the template because maniupulatiing the dictionary may cause that field value in this case subcat to clear back to none- find your subcat again using the original label which you have not changed. Try the template- it should work.
• Considerations- sometimes we use client scripts in the catalog or in the incident form to show or hide certain subcats or field values, or even to display them in a different way, if this is applicable to the subcat value you manipulated make the updates accordingly...