Support in various channels Service Catalog variables are supported in various channels. The ServiceNow docs site contains more information about question types and subtypes in the "https://www.dell.com/downloads/global/products/precn/en/spec_precn_690_en.pdf". Step 3: Connection Settings. You may also consider the Locking down variables by role without a script method described above. The difference for the most recent poster was that the variables were to be shown on an Incident form (which had been generated by a record producer). Locking down variables by role without a script. item.hide(); Diversity, Inclusion, & Belonging Training, GlideDialogWindow: Advanced Popups Using UI Pages, Swapping Hardware Assets in ServiceNow with HAM Pro. Please let me know how it works. This was a great fix to making the variables read-only on my catalog tasks. However in IT7 Not sure what causes this, just thought Id let you know. Ive discovered g_form doesnt work like it does on the Reopen Incident in the incident form in the native view. In looking around I found posts around JavaScript that keeping a field as Disabled doesnt allow it to be submitted, so my theory is/was that since the value isnt being submitted, Service-Now is thinking that the field was changed to be a blank or default value. If youve set it up as described, you should end up with the value recorded in work notes. Attachment When submitting a catalog item request, this variable lets you upload an attachment for a question of the item. Thanks! How to rename "Submit" button for catalog items in Service Portal Procedure Navigate to Service Portal widget list 2. }); Hi, I need help, I have the following client script that I want to hide 3 options in the state field and the Resolve Incident button based on the severity field and if the person has the severity_manager role. Is u_review an actual form field or is it a variable as well? Double check the values and make sure they are correct and of the correct type. For example we can use syntax in client scripts such as: g_form.getValue("variable_name"); Basically from here we can select the catalog where we want to display respective catalog item. You would need to change that to loop through all of the targeted elements to remove the icons. g_form.setReadonly(variables.laptop_desktop, false); ServiceNow had a couple of bugs when setting fields read only that I had to account for in this code (one with no scrolling or copy/paste in multiline text variables and one with date variables being blanked out on save). This script looks for the Variables label on the variable formatter and disables the variables associated with it. . Thanks to the great pioneers! Ive used the client script code provided and it is still resetting my date variables. That just means the expression in your ng-hide is not returning true. We can fix our catalog items for future use but is there anything which can be done to resolve this issue on items submitted before the fix? Thanks Nathan this worked like a champ! }); If the variable is a radio button type, it is working fine and making the field editable. if(item.id != IncNoti && item.id != ){. Each of these statements will remove the first occurrence of that reference variable type in Calgary: $$(img[id=view.sys_user])[0].hide(); // reference variable to sys_user table We can create UI policies for the catalog item from here. } Thank you for the client script that makes the variables read only on the Request Item form. How to create RITM through the script?3.. BR helped me restrict write from the variables. Locking down variables via business rules, Probably the simplest way of locking down variables on a standard form via script is to create a business rule that checks to see if the variables have changed and then to abort the submission of the task record if they have changed. adsbygoogle = window.adsbygoogle || []; Maybe theres a way to do this from the workflow, but I havent been able to figure it out. Normally a script would do a direct assignment, for example, gr.category = value . I want a button which should send comments to the back end table. Using this approach, the possibilities are endless when designing catalog item forms. I recently came across another forum posting where the poster wanted to do something similar. Can someone please tell me why this is not working: i have used the script for setting the variables to read only. I dont have any sample code I can provide you for that. My work around was to add an additional onSubmit client script that sets Disabled to equal False instead of True, so the values are saved and seen the next time around. value ); //--classic UI alert ( g_form . They are best used when a user needs to see all options side by side when making their selection. Not immediately, but as soon as you make a change to a task with variables on it for example, all the disabled variables will be empty when you re-open the form. I want to remove the green arrow icon When i click the update button then all the data inthe form form should update in the service portal. In Record producer form I have made field readonly, but its still showing me the calendar option. We . The print icon (and others in the parent frame) can be hidden but they would use a different logic. function onSubmit () { alert ( g_form . A Catalog Item is a form used to submit information, a request, or to create a task. BACK button from my form You could try to include g_form.setMandatory in the client script to make each readonly variable not mandatory as well. Using these core activities we can design the workflow. i used ng-hide to hide button when state closed but when i reload the form Close button again appearing . Ive removed that section from my code above so you can give it a try. Below video will give you practical demonstration that how we can, Below are the steps to attach workflow in, There are lots of question comes in mind while creating. No way that I know of currently. Thanks you so much, Mark.. From what Im seeing, setting a variable to disabled in Calgary seems to behave differently than it did in Berlin and results in actually modifying the contents of the variable to be blank in the Options (sc_item_option) table. Also, it would be great if it could update the Work Notes or Additional comments that the user has resolved it! Should we be moving entries out of this table as requested items are closed? What must be modified specific to my instance to get this to populate correctly? Create custom action buttons in Service Portal - ServicePortal.io Create custom action buttons in Service Portal A common feature request for Service Portal is to be able to add custom buttons to the sc_request or ticket page similar to the way you could add UI actions to a form. Im trying to use the widget code that is in the following link, http://www.servicenowelite.com/blog/2017/5/12/service-portal-resolve-incident-button, but is not working. I have my html set to show / hide certain buttons: