Скачать с ютуб Client scripts with practical examples в хорошем качестве

Client scripts with practical examples

Best practices of client scripts: 1. Avoid global client scripts 2. Avoid using DOM (Manipulating elements via the document object model) 3.Use UI policies for read only, visible, mandatory, and hide/show related list. 4. Use Asynchronous calls via g_form.getReference() or GlideAjax API. 5. Don't use GlideRecord API in client scripts. 6. Use the on change client script properly by keeping conditions. 7. Avoid creating variable outside the function otherwise they can be collide with variables of other client scripts. Reference: https://developer.servicenow.com/dev.... What is the purpose of Isolate script checkbox in client script? Answer: It manages whether DOM manipulation should be enabled/disabled for client script. If DOM manipulation code is not working then there is possibility that this checkbox is true which is forcing client script to run in strict mode. In this video tutorial I have covered these use cases: 1. onCellEdit Client Script USECASE I want only the assignment group members to be allowed for updating an incident state in list view. Limitation: If you are updating more than one records then you should be the member of all those records then only it should allow but not just for one record. Glide Modal Reference: https://davidmac.pro/posts/2022-02-08... 2. onLoad Client Script USECASE I want only the knowledge base managers, owners or an author of knowledge article can see the source task field of the kb_knowledge table. 3. onChange Client Script USECASE When I change the incident field in incident task then the configuration item should be populated automatically and it should be same as the incident record and incident info (custom field) should show auto updated content like this below. a. Caller name of the incident b. Manager of the caller c. Incident short description 4. onSubmit Client Script USECASE If the work start date is greater than the work end date and if the work end date is greater than the resloved date then it should not allow to submit the incident form and it should show error messages when state is resolved. HOME WORK ---------------------- a. If the story state changes to Ready for testing and if it's spike story then attachment should be mandatory unless the spike documentation checkbox field not checked.