About


  Carlos Camacho Junior is a Sr. Technical Consultant with extensive experience and in the last years focused on everything ServiceNow.

  In the finance sector, Carlos created custom applications and improved complex infrastructure using ServiceNow technology as of 2021. He also led development teams on various projects and ensured that user stories were clear and solutions were a good fit and has a strong background in web development. Throughout the years he has also taken responsibility to enable his teams on agile practices and project standards.

  In his project at Roche he worked on the front and back-end of the portal to enhance User Experience as well as to automate processes. Worked on code refactoring, improving security and overall performance whilst keeping the technical debt under control and contributing to enhancing the QA processes.

  During his tenure at Convevo he has certified himself on CSM, Risk & Compliance and Custom App Development and updated his ITIL process knowledge (v4), as he is always eager to grow as a professional.

  As a Sr. Technical Consultant at Alpar, he is part of a talented team that helps companies towards digital transformation using the ServiceNow platform.

  As a Board Member for the Global SNUG Board of Directors, his focus is on helping to shape the future of engagement programs, have early access to innovation to provide feedback, and represent the voice of the broader community.


  

Popular posts from this blog

Hacktoberfest

Image
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...
Read more

VIDEO How to fix a reference to the Choice [sys_choice] table

Image
        The Choice table is used internally by the platform and depending on the payload of an operation, for performance reasons the platform can decide that it is better to drop the table and insert all the values instead of perform updates on specific records.       When we insert a new record in a table, a new sys_id is generated. If we have the Choice table as a reference to provide choices for a particular field in our table, these choices will be lost every time the platform decides to recreate the Choice table.       A simple way to avoid this problem is to create a field of  type Choice  which indirectly uses the Choice table but it is the right way, or we can create our own table to maintain the Application choices.       Recently I received the mission to do exactly this: create a private choice table for an Application.    ...
Read more

How to hide a Related List

Image
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...
Read more