![]() What the ACE report doesn’t explain is that there’s a whole spectrum of risk associated with any configuration in ServiceNow. It is true that ‘gel’ (or any DOM manipulation) puts you at a higher risk of having an upgrade issue related to that particular configuration. □ Just be aware that it generally lacks the necessary context to really give you a good idea of whether or not a particular configuration should be in place. Don’t get me started on the SN ACE health check. This business rule will be an advanced reference qualifier for the ‘Template’ field. Var common = 'table=' + $", mTemplate) Ĭreate a business rule on the ‘Global’ table. Var tt = new GlideRecord('sys_template') Var templates_list = new GlideChoiceList() ![]() If (typeof GlideChoiceList != 'undefined') I used 3 client scripts with the ‘Inherited’ checkbox checked - one for ‘task’, ‘cmdb_ci’, and ‘kb_knowledge’. Again you’ll need a client script for each table that you will be using templates on. Here are the settings you’ll want for your client script. You’ll need an onChange client script that looks for a change to the ‘Template’ field and then applies the template record that gets populated. I created 3 UI Policies with the ‘Inherit’ checkbox selected - one for ‘task’, ‘cmdb_ci’, and ‘kb_knowledge’.Ĥ) Create an onChange client script to apply the template You can create a UI Policy to hide the field by creating a UI Policy on each table with settings as shown in the screen shot below. You probably won’t want your users to even see the ‘Template’ field, but it still needs to be on the form. 3) Create a UI Policy to hide the ‘Template’ field I purposely don’t modify any form or list layouts so that your current layouts don’t get completely overwritten. If you’re using the ‘Advanced Templates’ update set, you’ll still need to perform this manual step after applying the update set. There is a system property that you can change ( glide.ui.permitted_tables) to make this table visible, but I’ve found that it’s easier to simply create the dictionary entries directly rather than having to change the system property. In my setup, this requires the creation of a ‘Template’ field on the following 3 tables.īecause the ‘Template’ table is a system table it won’t display if you try to create the reference field from the ‘Personalize form’ or ‘Personalize list’ UI. The field needs to be a reference field that references the ‘Template (sys_template)’ table. You’ll need to create a field called ‘Template (u_template)’ on any table that you want to apply templates to. Users still access all template options from the ‘Templates’ context menu items on a form. The method of applying templates does not change after applying these modifications. The update set makes templates work for the task, cmdb_ci, and kb_knowledge tables (and their extended tables) as long as the ‘Template’ field has been added to the forms for those tables. It may also be necessary to flush your system cache after personalizing the forms so that the client scripts work properly. After applying the update set you will need to make sure to add the ‘Template’ field to any form that you want to use templates on. It’s probably best just to use the ‘Advanced Templates’ update set. This article is provided mostly for documentation purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |