I just completed the #ServiceNowHacktoberfest by having 4 contributions accepted! - Service Portal is a single place for everyone to access information, services and different applications. For my first contribution (1068) I shared a use case to get a parameter from the URL and use it into an Ajax call, recovering information from the database to show within the User Interface. - For my second pull request (1069) I talked about best practices, explaining how to safely update a record. If we're not cautious with this kind of programming we can accidentally insert records instead of updating them. - For my third contribution (1085) I explained how to validate a field provided within a Catalog Item/Record Producer so that the date can't be in the past. - The last one (1093) was about fixing a direct reference to the Choice table. This is an internal table and it is not best practice to reference that table directly when you are crea...
It is been an exciting adventure working as a ServiceNow professional for the past four years. I was studying about Cloud Computing long ago and when the chance to work with the platform emerged in 2021, I grabbed it with both hands. My previous experience as a software developer was good and bad at the same time. I'll try to explain what happened about my coding skills when applied to the development process. 2021 - The 1st year : At first I started coding everything. Record Producer logic & validation was in Client Scripts and all back-end logic in Script Includes. After many NowLearning courses and navigating the community I understood how to use UI Policies to do things (Mandatory, Read-Only, Show/Hide fields) instead of putting everything on Client Scripts. Besides that my understanding of Business Rules reached a decent level. 2022 - The 2nd year : I invested time learning about ITIL and it was a game changer. Before every deployment to the test instanc...
Do you know about the Related List that displays people who can approve or reject a document? Recently a scenario came up where the developer needed to prevent the employee who created a record from approving that document. It wasn't common because usually the operational level creates the document while a manager approves it. Leaving this question of personas aside and focusing on the problem, what would be a possible solution? The first workaround that came to my mind was to hide the Approval list if the user who registered was viewing his own record. A workaround is not the ultimate solution. Just a palliative fix while we find time to think about the ideal one. The action plan 1) Every record has a field called sys_created_by; 2) On the front-end (client side) we have access to an API called Glide User that has some information about the logged in user. Among them is the name in the userName property. What if we create a...
Comments
Post a Comment