<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by ENUGANDHULA NILESH on Medium]]></title>
        <description><![CDATA[Stories by ENUGANDHULA NILESH on Medium]]></description>
        <link>https://medium.com/@heynilesh05?source=rss-de53c73e1f89------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*U5TCm30qaahJOPL57TwS4w.jpeg</url>
            <title>Stories by ENUGANDHULA NILESH on Medium</title>
            <link>https://medium.com/@heynilesh05?source=rss-de53c73e1f89------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:20:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@heynilesh05/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Beyond the Form: Mastering ServiceNow UI and Data Policies.]]></title>
            <link>https://medium.com/@heynilesh05/beyond-the-form-mastering-servicenow-ui-and-data-policies-5a5b43c810fb?source=rss-de53c73e1f89------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a5b43c810fb</guid>
            <category><![CDATA[servicenow-training]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[data-policy]]></category>
            <category><![CDATA[ui-policy]]></category>
            <dc:creator><![CDATA[ENUGANDHULA NILESH]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 16:32:37 GMT</pubDate>
            <atom:updated>2026-06-30T16:32:37.316Z</atom:updated>
            <content:encoded><![CDATA[<h4>Stop Bypassing Forms: The Developer’s Guide to ServiceNow UI and Data Policies</h4><h3>Part 1: UI Policies in ServiceNow</h3><h3>What is a UI Policy?</h3><p>A <strong>UI Policy</strong> is a client-side logic rule that dynamically changes the behavior or appearance of fields on a ServiceNow form based on specific data conditions.</p><pre>[ Form Field Condition Met ] ──&gt; (Client-Side Execution) ──&gt; [ Set Field: Mandatory / Visible / Read Only ]</pre><h4>Why UI Policies Are Used</h4><p>Forms must remain clean and intuitive for end users. If an ITIL agent is looking at an Incident form, they shouldn’t see fields that are irrelevant to their current workflow step. UI Policies allow you to build smart forms that respond immediately to user input without requiring a round-trip server refresh.</p><h4>How They Work on Forms</h4><p>UI Policies execute strictly in the browser. When a form loads or a field value changes, the platform’s client-side engine evaluates the UI Policy condition. If the condition is met, the system modifies the DOM (Document Object Model) properties of the specified form fields instantly.</p><h4>Difference Between UI Policies and Client Scripts</h4><ul><li><strong>UI Policies:</strong> Are <strong>declarative configuration</strong>. You define conditions and check boxes (Mandatory, Visible, Read Only) using dropdown menus. No code is required for standard operations.</li><li><strong>Client Scripts:</strong> Are <strong>imperative customization</strong>. They require JavaScript code (g_form.setValue(), g_form.setMandatory()) and are used for complex computations, reference field filtering, or data validation.</li></ul><blockquote><em>🛠️ </em><strong><em>ServiceNow Best Practice:</em></strong><em> If you can achieve a form behavior using a UI Policy, </em><strong><em>never</em></strong><em> write a Client Script. Declarative configuration is faster to execute and significantly easier to maintain during platform upgrades.</em></blockquote><h4>Benefits of Using UI Policies</h4><ul><li><strong>No Code:</strong> Drastically reduces script bugs.</li><li><strong>Performance:</strong> Evaluated fast on the client side.</li><li><strong>Readability:</strong> Other developers can easily understand the logic by looking at the condition builder rather than reading lines of code.</li></ul><h3>UI Policy Components</h3><p>When you open a UI Policy (sys_ui_policy) record, you control its execution through these primary fields:</p><ul><li><strong>Conditions:</strong> The standard condition builder (e.g., [State] [is] [Resolved]). The policy only executes its actions when this evaluates to true.</li><li><strong>Reverse if False:</strong> A crucial checkbox. If checked, ServiceNow automatically undoes your actions when the condition becomes false. For example, if a field becomes visible when State = Active, it automatically hides itself when State changes to Closed.</li><li><strong>On Load:</strong> If checked, the policy evaluates the moment the form finishes loading in the browser. If unchecked, it waits until a user manually changes a field value on the form.</li><li><strong>Global:</strong> If checked, the UI Policy applies to all available <strong>Form Views</strong> for that table. If unchecked, you can isolate the behavior to a specific view (like the <em>Service Portal View</em> or <em>Mobile View</em>).</li><li><strong>Inherit:</strong> If checked, this policy automatically trickles down to any tables that extend the target table. For example, a UI Policy on task with <em>Inherit</em> turned on will automatically execute on incident, problem, and change_request.</li></ul><h3>UI Policy Actions</h3><p>A UI Policy is simply a shell containing conditions. The actual field modifications are defined in the <strong>UI Policy Actions</strong> (sys_ui_policy_action) related list. Each action targets a specific field and sets three attributes:</p><h4>1. Mandatory</h4><ul><li><strong>True:</strong> Forces a red asterisk next to the field. The user cannot save or update the form until this field contains a value.</li><li><strong>False:</strong> Removes the mandatory requirement.</li></ul><h4>2. Visible</h4><ul><li><strong>True:</strong> Displays the field on the form layout.</li><li><strong>False:</strong> Completely hides the field and its label from the user’s view.</li></ul><h4>3. Read Only</h4><ul><li><strong>True:</strong> Grays out the field, preventing users from clicking, typing, or changing its value.</li><li><strong>False:</strong> Opens the field for interactive editing.</li></ul><h3>Practical Demonstration: UI Policies</h3><p>Let’s configure three core scenarios in your Personal Developer Instance (PDI).</p><h4>Exercise 1: Conditional Mandatory Fields</h4><p><strong>Navigation Path:</strong> <strong>All</strong> $\rightarrow$ <strong>System Definition</strong> $\rightarrow$ <strong>UI Policies</strong></p><ul><li><strong>Configuration Steps:</strong></li><li>Click <strong>New</strong>.</li><li><strong>Table:</strong> Incident [incident]</li><li><strong>Short description:</strong> Make Resolution Notes Mandatory when Resolved</li><li><strong>Condition:</strong> [State] [is] [Resolved]</li><li>Ensure <strong>Reverse if False</strong> and <strong>On Load</strong> are checked.</li><li>Right-click the form header and click <strong>Save</strong>.</li><li>In the <strong>UI Policy Actions</strong> related list at the bottom, click <strong>New</strong>.</li><li><strong>Field name:</strong> Resolution notes (close_notes)</li><li><strong>Mandatory:</strong> True</li><li>Click <strong>Submit</strong>.</li><li><strong>Testing Steps:</strong> Open an active Incident form. Change the <strong>State</strong> dropdown to Resolved.</li><li><strong>Expected Results:</strong> The Resolution notes field immediately displays a red asterisk. Change the State back to New—the asterisk disappears.</li></ul><h4>Exercise 2: Conditional Visibility</h4><p><strong>Navigation Path:</strong> Go to the UI Policies list and click <strong>New</strong>.</p><ul><li><strong>Configuration &amp; Actions:</strong></li><li><strong>Table:</strong> Incident [incident]</li><li><strong>Short description:</strong> Show Asset on Hardware Category</li><li><strong>Condition:</strong> [Category] [is] [Hardware]</li><li>Save the header, then create a <strong>UI Policy Action</strong>:</li><li><strong>Field name:</strong> Asset (cmdb_ci) (or any reference asset field on your layout)</li><li><strong>Visible:</strong> True</li><li>Leave others as <em>Leave alone</em>. Click <strong>Submit</strong>.</li><li><strong>Testing Steps:</strong> Open an Incident where Category is Software. Look for the Asset field (it should be hidden). Change Category to Hardware.</li><li><strong>Expected Results:</strong> The Asset field instantly appears on the form layout.</li></ul><h4>Exercise 3: Conditional Read Only</h4><p><strong>Navigation Path:</strong> Create a third UI Policy record.</p><ul><li><strong>Configuration &amp; Actions:</strong></li><li><strong>Table:</strong> Incident [incident]</li><li><strong>Short description:</strong> Lock Assignment Group for Critical Incidents</li><li><strong>Condition:</strong> [Priority] [is] [1 - Critical]</li><li>Save the header, then create a <strong>UI Policy Action</strong>:</li><li><strong>Field name:</strong> Assignment group (assignment_group)</li><li><strong>Read Only:</strong> True</li><li>Click <strong>Submit</strong>.</li><li><strong>Testing Steps:</strong> Open an Incident with Priority 3. Notice you can change the group. Change Urgency and Impact to 1 so the system calculates a Priority of 1 - Critical.</li><li><strong>Expected Results:</strong> The Assignment group field immediately locks down and cannot be modified.</li></ul><h3>UI Policy Execution Mechanics</h3><h4>When They Run</h4><p>UI Policies run in the user’s browser during two specific triggers:</p><ul><li><strong>Form Load:</strong> If the <em>On Load</em> flag is true, the platform runs the check as soon as the client rendering engine loads the form fields.</li><li><strong>Field Value Change:</strong> As soon as a user clicks a dropdown, toggles a choice, or populates a reference field that matches the policy’s condition criteria.</li></ul><h4>Order of Execution</h4><p>If multiple UI Policies target the same field, their execution sequence is governed strictly by the <strong>Order</strong> field.</p><ul><li>UI Policies run from the <strong>lowest order number to the highest</strong> (e.g., an order of 100 runs before an order of 200).</li><li>The policy with the highest order number runs <em>last</em>, meaning its fields configurations win and overwrite any matching properties set by previous lower-order policies.</li></ul><h4>Interaction with Client Scripts</h4><p>ServiceNow executes client-side scripts and configurations in a definitive chronological sequence:</p><pre>1. Client Scripts (onLoad) ➔ 2. UI Policies (onLoad) ➔ 3. Client Scripts (onChange) ➔ 4. UI Policies (onChange)</pre><p>Because UI Policies execute <em>after</em> Client Scripts for both page loading and value changes, <strong>UI Policies will overwrite field properties (Mandatory, Visible, Read Only) set by a Client Script</strong> if they target the same field.</p><h3>Common Developer Mistakes (UI Policies)</h3><ul><li><strong>Conflicting “Reverse if False” Rules:</strong> Creating Policy A (Order 100) that makes a field visible if State=New, and Policy B (Order 200) that makes the same field hidden if State=New with <em>Reverse if False</em> enabled. They will fight each other, causing flickering forms or locking fields unexpectedly.</li><li><strong>Writing Scripts inside UI Policies for Simple Actions:</strong> UI Policies have an <em>Advanced</em> tab containing Execute if true and Execute if false script blocks. Writing JavaScript here to set visibility (g_form.setVisible) is a major anti-pattern. Only use the Advanced script block if you need to run complex client logic that cannot be handled by checkboxes.</li></ul><h3>Real ServiceNow Examples</h3><ul><li><strong>Incident Management:</strong> Hiding the Hold reason field unless the State field is explicitly set to On Hold.</li><li><strong>Change Management:</strong> Making the Risk evaluation field mandatory only if the Change type is chosen as Normal or Emergency.</li><li><strong>Service Catalog:</strong> Using <strong>Catalog UI Policies</strong> to reveal specific question variables dynamically as an end-user checks items in a catalog order item form.</li></ul><h3>Part 2: Data Policies in ServiceNow</h3><h3>What is a Data Policy?</h3><p>A <strong>Data Policy</strong> is a server-side enforcement rule that guarantees data integrity by making specified fields mandatory or read-only before any record is committed directly to the ServiceNow database.</p><pre>[ Target Data Layer ] &lt;──(Server Enforces Data Policy)── [ Form Submission / REST API / Import Set ]</pre><h4>Why Data Policies Are Used</h4><p>UI Policies are great, but they are easily bypassed. If a user utilizes a web integration, updates a record via a <strong>REST API</strong>, uploads data through an <strong>Import Set</strong>, or updates records using <strong>List Edit</strong> on a list view, they bypass the form entirely. Since the form never loads, client-side UI Policies never execute! Data Policies exist to secure the backend database layer regardless of how the data arrives.</p><h4>How They Enforce Data Integrity</h4><p>When any script, API, or user tries to save a record, the server-side transactional engine checks active Data Policies (sys_data_policy2). If the field values fail the conditions, the server halts the database transaction, rejects the insert or update operation, and returns an explicit error message back to the initiating interface.</p><h3>Data Policy Components</h3><ul><li><strong>Conditions:</strong> Server-side evaluation criteria (e.g., [State] [is] [Closed]).</li><li><strong>Apply to Import Sets:</strong> A checkbox ensuring that bulk data loads processed via staging tables must honor the mandatory and read-only field requirements.</li><li><strong>Apply to Web Services:</strong> A checkbox that applies constraints to incoming SOAP, REST, or Scripted Web Service integrations.</li><li><strong>Use as UI Policy on Client:</strong> A highly efficient checkbox. When enabled, ServiceNow automatically clones this server-side policy and injects it into the client-side UI engine as a UI Policy. This gives you form-level visual behavior and backend database security simultaneously from a single record definition!</li></ul><h3>Practical Demonstration: Data Policies</h3><h4>Exercise 1: Create a Data Policy</h4><p><strong>Navigation Path:</strong> <strong>All</strong> &gt; <strong>System Policy</strong> &gt; <strong>Rules</strong> &gt; <strong>Data Policies</strong></p><ul><li><strong>Configuration Steps:</strong></li><li>Click <strong>New</strong>.</li><li><strong>Table:</strong> Incident [incident]</li><li><strong>Short description:</strong> Backend Enforcement - Close Notes Required</li><li><strong>Condition:</strong> [State] [is] [Closed]</li><li>Check <strong>Apply to Import Sets</strong>, <strong>Apply to Web Services</strong>, and <strong>Use as UI Policy on Client</strong>.</li><li>Right-click the form header and click <strong>Save</strong>.</li><li>In the <strong>Data Policy Rules</strong> related list, click <strong>New</strong>.</li><li><strong>Field name:</strong> Close notes</li><li><strong>Type:</strong> Mandatory</li><li>Click <strong>Submit</strong>.</li></ul><h4>Exercise 2: Test the Integration Blockade (REST API)</h4><p>To demonstrate that a Data Policy works where a UI Policy cannot, we will simulate an external integration bypass attempt using the <strong>REST API Explorer</strong>.</p><p><strong>Navigation Path:</strong> <strong>All</strong> &gt; <strong>System Web Services &gt;</strong> <strong>REST API Explorer</strong></p><ul><li><strong>Configuration &amp; Testing Steps:</strong></li><li>Namespace: now, API Name: Table API.</li><li>Click <strong>Create a record (POST)</strong>.</li><li><strong>tableName:</strong> incident</li><li>Under <strong>Request Body</strong>, click <strong>Add field</strong> and add:</li><li>state = 7 (Value for Closed)</li><li>short_description = Testing Data Policy API Block</li><li><em>(Leave Close Notes entirely empty!)</em></li><li>Scroll to the bottom and click <strong>Send</strong>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a5b43c810fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Senior Developer’s Guide to ServiceNow Update Sets and Import Sets]]></title>
            <link>https://medium.com/@heynilesh05/the-senior-developers-guide-to-servicenow-update-sets-and-import-sets-52112aa4c4c1?source=rss-de53c73e1f89------2</link>
            <guid isPermaLink="false">https://medium.com/p/52112aa4c4c1</guid>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[update-sets]]></category>
            <category><![CDATA[import-sets]]></category>
            <category><![CDATA[servicenow-training]]></category>
            <dc:creator><![CDATA[ENUGANDHULA NILESH]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 13:08:23 GMT</pubDate>
            <atom:updated>2026-06-18T13:08:23.924Z</atom:updated>
            <content:encoded><![CDATA[<h4>Beyond sys_update_xml: Mastering ServiceNow Update Sets and Import Sets</h4><h3>Part 1: Update Sets in ServiceNow</h3><h3>What is an Update Set?</h3><p>An <strong>Update Set</strong> is a group of configuration changes moved from one instance to another. It acts as a point-in-time snapshot or “container” that tracks, packages, and exports customizations made by a developer.</p><pre>[ Dev Instance ] --(Export XML)--&gt; [ Test Instance ] --(Commit)--&gt; [ Prod Instance ]</pre><h4>Why Update Sets are Used</h4><p>ServiceNow development follows a strict multi-instance lifecycle: <strong>Development (Dev) → Test/QA → Production (Prod)</strong>. You never build or configure features directly in Production because a single broken script could halt business operations. Update Sets allow you to safely build and test features in Dev, then migrate those identical configurations across your landscape without manually recreating them.</p><h4>How ServiceNow Tracks Changes</h4><p>Every time you save a configuration change, a background engine checks if the table has the attribute update_synch=true. If it does, ServiceNow logs a record of that change into the <strong>Customer Update</strong> (sys_update_xml) table. This record links directly to your currently active Update Set.</p><h4>What Records Are Captured vs. NOT Captured</h4><p>The fundamental rule of ServiceNow migration is: <strong>Update Sets capture Configuration (Metadata), NOT Data.</strong></p><ul><li><strong>Captured (Metadata):</strong> Structural changes that alter <em>how the platform behaves</em>. Examples: Tables, Fields, Business Rules, Client Scripts, UI Policies, Workflows, Flow Designer flows, and Form Layouts.</li><li><strong>NOT Captured (Data):</strong> Operational records that users interact with daily. Examples: Incident records, User accounts (sys_user), Groups (sys_user_group), Assets, Attachments, and transactional logs.</li></ul><h3>Update Set Lifecycle</h3><p>The migration of configuration follows a linear, non-negotiable lifecycle:</p><pre>[ 1. Create ] ➔ [ 2. Make Changes ] ➔ [ 3. Close &amp; Complete ] ➔ [ 4. Retrieve &amp; Preview ] ➔ [ 5. Commit ]</pre><ul><li><strong>Create Update Set:</strong> The developer creates a new record in the local instance and sets it to <strong>In Progress</strong>. This makes it their active workspace.</li><li><strong>Make Changes:</strong> The developer builds tables, fields, and scripts. The platform automatically tracks these configurations as sys_update_xml entries.</li><li><strong>Close &amp; Complete:</strong> Once testing is successful in Dev, the developer changes the state to <strong>Complete</strong>. This locks the Update Set, preventing further changes from being added.</li><li><strong>Preview Update Set:</strong> The target instance (e.g., Test) retrieves the completed Update Set and runs a <strong>Preview</strong>. This is a validation scan where ServiceNow checks for collisions, missing dependencies, or newer versions of the same records.</li><li><strong>Commit Update Set:</strong> If the preview finishes with zero errors (or after all conflicts are explicitly resolved), the administrator clicks <strong>Commit</strong>. This applies the XML payloads directly into the target instance’s database, making the changes live.</li><li><strong>Verify Migration:</strong> The developer logs into the target instance to verify that forms, scripts, and layouts match the source instance precisely.</li></ul><h3>Practical Demonstration: Update Sets</h3><p>Let’s walk through an architectural exercise utilizing a Personal Developer Instance (PDI).</p><h4>Exercise 1: Create a New Update Set</h4><p><strong>Navigation Path:</strong> <strong>All</strong> &gt; <strong>System Update Sets</strong> &gt; <strong>Local Update Sets</strong></p><ul><li><strong>Configuration Steps:</strong></li><li>Click <strong>New</strong>.</li><li><strong>Name:</strong> Workspace Reservation - Core V1</li><li><strong>State:</strong> Leave as In Progress.</li><li>Click <strong>Submit and Make Current</strong>.</li></ul><p><strong>Expected Results:</strong> The Update Set is created. In your developer header bar (or inside the application picker Settings panel), Workspace Reservation - Core V1 is now shown as your active Update Set.</p><h4>Exercise 2: Create Configurations</h4><p><strong>Navigation Path 1 (Table):</strong> <strong>All</strong> &gt; <strong>System Definition</strong> &gt; <strong>Tables</strong></p><ul><li><em>Configuration:</em> Click <strong>New</strong>. Label: Workspace Reservation. Name: u_workspace_reservation. Click <strong>Submit</strong>.</li></ul><p><strong>Navigation Path 2 (Business Rule):</strong> <strong>All</strong> &gt; <strong>System Definition</strong> &gt; <strong>Business Rules</strong></p><ul><li><em>Configuration:</em> Click <strong>New</strong>. Table: Workspace Reservation. Name: Validate Reservation Dates. When: before (Insert/Update).</li><li><em>Script:</em> if (current.u_start_date &gt; current.u_end_date) { current.setAbortAction(true); }</li><li><em>Action:</em> Click <strong>Submit</strong>.</li></ul><p><strong>Navigation Path 3 (Client Script &amp; UI Policy):</strong> Create a basic Client Script making a field mandatory on load, and a UI Policy hiding a section.</p><p><strong>Expected Results:</strong> All four structural elements are live on your local instance.</p><h4>Exercise 3: Verify Captured Records</h4><p><strong>Navigation Path:</strong> <strong>All</strong> &gt; <strong>System Update Sets</strong> &gt; <strong>Local Update Sets</strong></p><ul><li><em>Configuration:</em> Open your active Workspace Reservation - Core V1 record. Scroll down to the <strong>Customer Updates</strong> related list.</li><li><strong>Expected Results:</strong> You will see multiple rows matching the configurations you made.</li><li><strong>What to Observe:</strong> Note the <strong>Type</strong> column. It contains explicit metadata types: Table, Business Rule, Client Script, and UI Policy.</li></ul><h4>Exercise 4: Move Update Set to Another Instance</h4><p><strong>Navigation Path (Source Instance):</strong> Open your Local Update Set Workspace Reservation - Core V1.</p><ul><li><strong>Configuration Steps:</strong></li><li>Change the <strong>State</strong> field from In Progress to <strong>Complete</strong>.</li><li>Click <strong>Save</strong>.</li><li>Click the <strong>Export to XML</strong> Related Link. Save the generated XML file locally.</li></ul><p><strong>Navigation Path (Target Instance):</strong> Log into your second PDI or target instance. Go to <strong>All</strong> &gt; <strong>System Update Sets</strong> &gt; <strong>Retrieved Update Sets</strong>.</p><ul><li>Click the Related Link <strong>Import Update Set from XML</strong>.</li><li>Upload the file saved in step 3.</li><li><strong>Expected Results:</strong> The Update Set is loaded into the target instance with a state of Loaded.</li></ul><h4>Exercise 5: Preview and Commit</h4><p><strong>Navigation Path:</strong> Inside <strong>Retrieved Update Sets</strong>, open the imported record.</p><ul><li><strong>Configuration Steps:</strong></li><li>Click <strong>Preview Update Set</strong>. Wait for the progress bar to complete.</li><li>Ensure the <strong>Update Set Preview Problems</strong> related list shows 0 errors. (If an error appears, select the row and choose <em>Accept Remote Update</em> or <em>Skip Remote Update</em>).</li><li>Click <strong>Commit Update Set</strong>.</li><li><strong>Expected Results:</strong> The state changes to Committed.</li><li><strong>Common Mistakes:</strong> Forgetting to change the state to <em>Complete</em> before exporting, or neglecting to review preview problems, which can result in broken, partially applied configurations on the target instance.</li></ul><h3>Update Set Best Practices</h3><ul><li><strong>Naming Conventions:</strong> Always use a predictable structure containing the application name, user story ID, and a clear description.</li><li><em>Good:</em> WORK-104_WorkspaceReservation_FormLayout_V1</li><li><em>Bad:</em> nilesh_changes_fix</li><li><strong>One Story = One Update Set:</strong> Never combine multiple unrelated features or user stories into a single Update Set. It breaks your ability to selectively deploy or hold back specific features.</li><li><strong>Parent and Child Update Sets (Batching):</strong> For large projects with multiple developers, link individual developer update sets to a single empty <strong>Parent Update Set</strong>. When migrating, you preview and commit the parent, and ServiceNow automatically processes all child updates in the correct chronological order.</li><li><strong>Troubleshooting Collisions:</strong> A collision occurs when two update sets modify the exact same record. If App A changes a Business Rule script and App B deletes it, previewing both in Test flags a conflict. <strong>Resolution:</strong> Evaluate the timestamps in the preview problem log and select the version that matches your final approved technical design.</li></ul><h3>Common Interview Questions (Update Sets)</h3><h4>Q: What is an Update Set?</h4><p><strong>A:</strong> An Update Set is a customized group of configuration records that tracks changes made to an instance, allowing developers to package metadata and migrate it seamlessly across separate development, testing, and production environments.</p><h4>Q: What is the difference between Preview and Commit?</h4><p><strong>A:</strong> <strong>Preview</strong> is a risk-free validation phase where ServiceNow scans the incoming XML changes against the local instance database to detect errors, collisions, or missing dependencies. <strong>Commit</strong> is the execution phase that applies those changes permanently to the database, making the configurations live.</p><h4>Q: What is an Update Set Collision?</h4><p><strong>A:</strong> A collision happens when an incoming Update Set contains a modification to a record that was changed more recently on the target instance than on the source instance. ServiceNow halts the deployment of that record and prompts the admin to manually choose which version to keep.</p><h4>Q: What is a Backout?</h4><p><strong>A:</strong> A <strong>Backout</strong> is a platform roll-back function. If a committed Update Set causes immediate issues in an instance, clicking <em>Backout</em> reverses the applied changes, restoring the tracked metadata records back to their exact state prior to the commit.</p><h3>Part 2: Import Sets in ServiceNow</h3><h3>What is an Import Set?</h3><p>An <strong>Import Set</strong> is a mechanism used to pull data from external data sources and transform that data into standard ServiceNow target tables.</p><pre>[ External Source ] ➔ [ Data Source ] ➔ [ Import Set Table ] ➔ [ Transform Map ] ➔ [ Target Table ]</pre><h4>Why Import Sets are Used</h4><p>Organizations do not start from scratch; they possess legacy databases, active identity systems, and third-party vendor files. Import Sets allow you to safely ingest thousands of external records (like assets, locations, or users) while mapping, cleaning, and validating the data before it hits your production tables.</p><h3>Import Set Architecture &amp; Process Flow</h3><p>The import engine contains four core architectural building blocks:</p><pre>+-------------------+      +----------------------+      +-------------------+      +----------------+<br>|  1. Data Source   | ---&gt; | 2. Import Set Table  | ---&gt; | 3. Transform Map  | ---&gt; |4. Target Table |<br>|  (Excel, REST...) |      |  (Staging Area)      |      | (Field Match / Co)|      | (sys_user, task|<br>+-------------------+      +----------------------+      +-------------------+      +----------------+</pre><ul><li><strong>Data Source (</strong><strong>sys_data_source):</strong> Defines where the raw data lives and how the platform accesses it. This could be a manually loaded file or an automated connection.</li><li><strong>Import Set Table / Staging Table:</strong> A temporary database table created by the platform to hold the raw, unfiltered incoming data exactly as it looks in the source. Every row here extends the base sys_import_set_row table.</li><li><strong>Transform Map (</strong><strong>sys_transform_map):</strong> The operational logic layer. It defines the relationships, rules, and field-to-field matching between the temporary staging table columns and your permanent target table columns.</li><li><strong>Target Table:</strong> The final destination table inside ServiceNow where the scrubbed, processed data is permanently saved (e.g., User, Location, or custom tables).</li></ul><h3>Data Sources Deep Dive</h3><p>ServiceNow supports several enterprise data source types:</p><ul><li><strong>Excel / CSV:</strong> Flat files uploaded manually by administrators or fetched from an external server.</li><li><strong>JDBC (Java Database Connectivity):</strong> Directly queries external relational databases like SQL Server, Oracle, or MySQL using an internal system or a <strong>MID Server</strong> (Management, Instrumentation, and Discovery).</li><li><strong>FTP / SFTP:</strong> Automatically downloads text or spreadsheet files from secure remote storage servers on a scheduled basis.</li><li><strong>REST / HTTP:</strong> Ingests payloads via web service API endpoints using JSON or XML structures.</li></ul><h3>Transform Maps &amp; Logic Control</h3><h4>Source vs. Target Fields</h4><p>During a transform, a source column header (e.g., emp_id in Excel) is systematically copied into a matching target column attribute (e.g., employee_id on the sys_user table).</p><h3>Field Mapping Methods</h3><p>When connecting your staging table to your target table, ServiceNow provides two primary declarative utilities on the <strong>Table Transform Map</strong> form:</p><h4>1. Auto-Map Matching Fields</h4><ul><li><strong>What it is:</strong> A one-click automated link.</li><li><strong>How it works:</strong> ServiceNow automatically matches source staging columns to target fields if their names or labels are identical, instantly creating the field map records.</li><li><strong>Best for:</strong> Clean data imports where source column headers perfectly match your ServiceNow field names.</li></ul><h4>2. Mapping Assist</h4><ul><li><strong>What it is:</strong> A visual, side-by-side workbench.</li><li><strong>How it works:</strong> It opens a dual-list layout where you manually pair source fields (left) with target fields (right) by dragging and dropping or using arrow buttons.</li><li><strong>Best for:</strong> Complex files where column headers do not match target field names (e.g., mapping an Excel column titled Room Code into a ServiceNow target field named u_location_id).</li></ul><h4>Transform Scripts</h4><p>When declarative mapping isn’t enough, you can inject server-side JavaScript scripts to clean data on the fly. These run at specific lifecycle points during processing:</p><ul><li>onStart: Runs once before any data row is evaluated. Used for global initializations.</li><li>onBefore: Runs for every single row, <em>before</em> data is copied from the source row to the target row. Excellent for field validations or aborting bad rows.</li><li>onAfter: Runs for every row, <em>after</em> the record has been saved to the database. Used to create related records or log specific details.</li><li>onEnd: Runs once after all rows have been fully processed.</li></ul><h3>Practical Demonstration: Import Sets</h3><p>Let’s look at an application example: Ingesting location seat limits into a custom <strong>Workspace Reservation</strong> application.</p><h4>Exercise 1: Create a Data Source</h4><p><strong>Navigation Path:</strong> <strong>All</strong> &gt; <strong>System Import Sets</strong> &gt; <strong>Data Sources</strong></p><ul><li><strong>Configuration Steps:</strong></li><li>Click <strong>New</strong>.</li><li><strong>Name:</strong> Legacy Office Workspaces</li><li><strong>Type:</strong> File</li><li><strong>Format:</strong> Excel</li><li><strong>File Attachment:</strong> Attach an Excel sheet containing three columns: Room Code, Floor, and Max Seats.</li><li>Click <strong>Submit</strong>.</li></ul><h4>Exercise 2: Load Excel Data &amp; Create Import Set Table</h4><p><strong>Navigation Path:</strong> Open your created Legacy Office Workspaces data source record.</p><ul><li><strong>Configuration Steps:</strong></li><li>Click the Related Link <strong>Load All Records</strong>.</li><li>Wait for the progress status screen to indicate Success.</li><li><strong>Expected Results:</strong> ServiceNow creates an internal, dynamic staging table named <strong>u_legacy_office_workspaces</strong> and populates it with raw rows from your spreadsheet.</li></ul><h4>Exercise 3: Create a Transform Map</h4><p><strong>Navigation Path:</strong> On the import success page (or via <strong>System Import Sets</strong> &gt; <strong>Create Transform Map</strong>).</p><ul><li><strong>Configuration Steps:</strong></li><li><strong>Name:</strong> Map Legacy Rooms to Workspaces</li><li><strong>Source table:</strong> u_legacy_office_workspaces</li><li><strong>Target table:</strong> Select your custom Workspace table (e.g., u_workspace_reservation or a custom Location table).</li><li>Click <strong>Save</strong>.</li></ul><h4>Exercise 4: Map Fields</h4><p><strong>Navigation Path:</strong> Scroll down to the Related Links of your new Transform Map record.</p><ul><li><strong>Configuration Steps:</strong></li><li>Click <strong>Mapping Assist</strong>.</li><li>Drag Room Code from the left column to match your target field (u_room_identifier) on the right.</li><li>Drag Max Seats to match your target capacity field (u_capacity).</li><li>Click <strong>Save</strong>.</li></ul><h4>Exercise 5: Run Transform</h4><p><strong>Navigation Path:</strong> Go back to your Transform Map form.</p><ul><li><strong>Configuration Steps:</strong></li><li>Click the <strong>Transform</strong> Related Link.</li><li>On the interceptor screen, select your map and click <strong>Transform</strong>.</li><li><strong>Expected Results:</strong> The status screen logs row processing statistics: <em>Inserts</em>, <em>Updates</em>, or <em>Errors</em>.</li><li><strong>Verification:</strong> Navigate directly to your target table to confirm that your records have populated with accurate data in each mapped field.</li></ul><h3>Coalesce Explained</h3><p><strong>Coalesce</strong> is a setting in a Field Map that turns that field into a unique key for matching incoming data to existing records.</p><pre>Is Coalesce Field Found in Target Table?<br>    ├── YES ➔ Update existing record<br>    └── NO  ➔ Insert new record</pre><h4>Insert vs. Update Behavior</h4><p>Without a coalesce field, running an Import Set twice with 500 rows will simply insert 500 brand-new records both times, resulting in <strong>1,000 records (500 duplicates)</strong>.</p><p>By marking a field like Room Code or Employee ID as <strong>Coalesce = true</strong>:</p><ul><li><strong>If a match is found:</strong> ServiceNow updates the existing record with the new values.</li><li><strong>If no match is found:</strong> ServiceNow creates a brand-new record.</li></ul><h4>Multi-Field Coalesce</h4><p>You can check the Coalesce box on multiple fields (e.g., checking both First Name and Last Name). ServiceNow will then require <em>both</em> values to match exactly before updating an existing record.</p><h3>Common Import Problems &amp; Troubleshooting</h3><ul><li><strong>Duplicate Records:</strong> Occurs when <strong>Coalesce</strong> is omitted or configured on a field that contains non-unique values from the source.</li><li><strong>Missing Mappings:</strong> Columns exist in the staging area but are left out of the field map, causing empty fields in the target table.</li><li><strong>Failed Transforms / Type Mismatches:</strong> Occurs when string values (e.g., &quot;Ten&quot;) are pushed into target fields configured as numeric types (e.g., <em>Integer</em>).</li><li><strong>Wrong Coalesce Configuration:</strong> If you coalesce on a field that changes frequently, ServiceNow won’t recognize the record and will generate unintended duplicates.</li></ul><h4>Step-by-Step Troubleshooting Checklist</h4><ul><li>Open <strong>System Import Sets</strong> &gt; <strong>Import Sets</strong> and open the specific execution record.</li><li>Scroll to the <strong>Import Set Rows</strong> related list and look for a state of <strong>Error</strong>.</li><li>Open the errored row and inspect the <strong>Log</strong> related list to view the precise database or JavaScript exception message.</li></ul><h3>Internal System Components</h3><p>ServiceNow runs imports using these core backend tables:</p><ul><li><strong>sys_data_source</strong>: Stores information about where your data comes from.</li><li><strong>sys_import_set</strong>: Manages the parent run execution state (e.g., Loading, Loaded, Processed).</li><li><strong>sys_import_set_row</strong>: The base class for all dynamically created staging tables.</li><li><strong>sys_transform_map</strong>: Stores the blueprint instructions for field mapping.</li><li><strong>sys_transform_entry</strong>: Individual records that map a single source field to a single target field.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52112aa4c4c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ServiceNow Scoped Applications: The Complete Beginner-to-Expert Developer Guide]]></title>
            <link>https://medium.com/@heynilesh05/beyond-u-the-developers-guide-to-servicenow-scoped-apps-87bd7c862a12?source=rss-de53c73e1f89------2</link>
            <guid isPermaLink="false">https://medium.com/p/87bd7c862a12</guid>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[global-scope]]></category>
            <category><![CDATA[application-scope]]></category>
            <category><![CDATA[scoped-application]]></category>
            <category><![CDATA[servicenow-training]]></category>
            <dc:creator><![CDATA[ENUGANDHULA NILESH]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 12:42:57 GMT</pubDate>
            <atom:updated>2026-06-18T12:44:31.617Z</atom:updated>
            <content:encoded><![CDATA[<h4>Beyond u_: The Developer&#39;s Guide to ServiceNow Scoped Apps</h4><h3>1. What is a Scoped Application?</h3><h3>Simple Definition</h3><p>In ServiceNow, a <strong>Scoped Application</strong> is a self-contained, sandboxed bundle of configuration records (like Tables, Business Rules, Client Scripts, and Flows) that fulfills a specific business outcome. Think of it as a protective container built around your custom application.</p><h3>Why ServiceNow Uses Scoped Applications</h3><p>Before scoping was introduced, every customization lived in one giant pool. If a developer accidentally wrote a broken, infinite-loop Business Rule, it could crash the entire instance. ServiceNow introduced application scoping to ensure <strong>application isolation, security, and easy deployment</strong>. It prevents custom applications from damaging the core system or interfering with each other.</p><h3>Real-World Example</h3><p>Consider <strong>HR Service Delivery (HRSD)</strong> or <strong>Customer Service Management (CSM)</strong>. These are scoped applications provided by ServiceNow. The HR tables, scripts, and security constraints are completely locked inside the HR scope. An ITIL agent working on an Incident cannot accidentally view or modify sensitive employee health records in the HR application because the application boundaries prevent it.</p><h3>How It Works in a ServiceNow Instance</h3><p>Every record in your instance has an sys_scope field. When you are inside a Scoped Application, ServiceNow wraps a unique namespace identifier around everything you create. The platform&#39;s runtime engine constantly checks this scope attribute before executing any script or granting table access.</p><h3>2. Global vs. Scoped Applications</h3><h3>What is the Global Application?</h3><p>The <strong>Global Application</strong> (global) is the default, baseline sandbox in ServiceNow. It contains core ITIL modules like <strong>Incident Management, Problem Management, and Change Management</strong>.</p><h3>What is a Scoped Application?</h3><p>A <strong>Scoped Application</strong> is a private, restricted workspace you explicitly create (often via <strong>Studio</strong> or <strong>App Engine Studio</strong>) that possesses its own distinct namespace and private API access.</p><h3>Why We Create Scoped Applications</h3><p>We build scoped applications so that our custom configurations can be safely developed, easily uninstalled without leaving “junk” records behind, and safely uploaded to the <strong>ServiceNow Application Repository</strong> or <strong>Store</strong> for deployment across Development, Test, and Production instances.</p><h3>Key Differences with Simple Examples</h3><ul><li><strong>Global:</strong> If you create a custom table named u_leave_request in the Global scope, <em>any</em> script anywhere in the instance can read, write, or delete its data by default.</li><li><strong>Scoped:</strong> If you create a custom application for facility tracking, ServiceNow prefixes the table name (e.g., x_12345_facility_request). No external script can touch this table unless you explicitly grant cross-scope permission.</li></ul><h3>Comparison Table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cM0bzT7JFrPLhMes6X_91w.png" /></figure><h3>When to Use Global vs. Scoped</h3><ul><li><strong>Use Global when:</strong> You are extending or modifying core out-of-the-box applications like adding a custom field to the incident or task table, or creating a UI Action on the Change Request form.</li><li><strong>Use Scoped when:</strong> You are building a brand-new application from scratch (e.g., a Team Onboarding App, a Parking Spot Booking App, or a Custom Innovation Tracker).</li></ul><h3>3. Application Scope</h3><h3>What Application Scope Means</h3><p>Application Scope acts as a virtual fence. When your developer session is set to a specific scope, your actions are confined to that sandbox.</p><h3>How ServiceNow Keeps Applications Separated</h3><p>ServiceNow enforces separation at the <strong>database level</strong> and the <strong>runtime script level</strong>:</p><ol><li><strong>Namespace Separation:</strong> Prevents name collisions. You can have a Script Include named Utils in five different scoped apps, and they won&#39;t conflict.</li><li><strong>Runtime Protection:</strong> The Glide system blocks unauthorized cross-scope CRUD (Create, Read, Update, Delete) execution.</li></ol><h3>Scope Names &amp; Anatomy</h3><p>When you create a scoped application, ServiceNow automatically generates a unique scope name based on your instance configuration properties and company code.</p><p>Let’s break down an example scope name: <strong>x_abc_team_sync</strong></p><ul><li><strong>x_</strong>: Identifies this as a custom, scoped application.</li><li><strong>abc_</strong>: Your unique <strong>Company Prefix</strong> (allotted by ServiceNow or derived from your PDI ID).</li><li><strong>team_sync</strong>: The clean string version of your Application Name.</li></ul><h3>What Records Belong to a Scope?</h3><p>Every metadata record created while that application is active belongs to it. This includes:</p><ul><li><strong>Tables and Fields</strong> (sys_db_object, sys_dictionary)</li><li><strong>Business Rules</strong> (sys_script)</li><li><strong>Client Scripts</strong> (sys_script_client)</li><li><strong>Flows and Actions</strong> (sys_hub_flow)</li><li><strong>Access Control Lists (ACLs)</strong> (sys_security_acl)</li></ul><h3>Practical Examples of Scope Enforcement</h3><ul><li><strong>Tables:</strong> A table created in scope x_abc_team_sync will automatically be named x_abc_team_sync_request.</li><li><strong>Script Includes:</strong> To call a Script Include from <em>outside</em> its own scope, you must prefix it with the scope name: new x_abc_team_sync.Utils().doSomething();.</li><li><strong>Business Rules:</strong> A Business Rule in a scoped app defaults to running <em>only</em> on tables within that same scope or tables explicitly configured to allow it.</li><li><strong>Client Scripts:</strong> Runs client-side on the scoped form. It cannot use legacy global APIs like g_form.getControl() if they are restricted in scoped execution.</li><li><strong>Flow Designer:</strong> Flows are bound to a scope. A scoped flow can trigger based on records in its own scope or global tables (like task), but its outputs and actions honor scoped boundaries.</li></ul><h3>4. Cross-Scope Access</h3><h3>What Cross-Scope Access Means</h3><p>Cross-Scope Access is the explicit bridge built over the fence separating two application scopes. It allows App A to interact with the data or logic inside App B.</p><h3>Why One Application May Need Access to Another</h3><p>Suppose you are building a custom <strong>Vehicle Booking App</strong> (Scoped). When a vehicle is booked, your app needs to look up employee details from the standard ServiceNow <strong>User (</strong><strong>sys_user)</strong> table, which lives in the <strong>Global</strong> scope. Your app is requesting cross-scope access to read the Global user table.</p><h3>What Happens When Access is Not Allowed?</h3><p>If a script in a scoped application tries to query a table in another scope without permission, the operation fails and throws an error in the System Log:</p><blockquote>Security restricted: Access to api [table_name] from scope [your_scope] is denied</blockquote><h3>Cross-Scope Privileges (sys_scope_privilege)</h3><p>When an application attempts an operation on an artifact outside its scope, ServiceNow evaluates the <strong>Cross-Scope Privileges</strong> table. If a record exists approving the relationship, the action proceeds. If not, it can either be blocked completely or tracked for administrator approval, depending on the application settings.</p><h3>Application Access Settings</h3><p>On every table record (sys_db_object), you control how other scopes interact with it via the <strong>Application Access</strong> tab:</p><ul><li><strong>Accessible from:</strong> Can be set to <em>“This application scope only”</em> or <em>“All application scopes”</em>.</li><li><strong>Can Read, Can Create, Can Update, Can Delete:</strong> Checkboxes that define exactly what CRUD actions external scopes can execute via scripts or web services.</li></ul><h3>5. Hands-On Practice in a PDI</h3><p>Follow these exact steps in your Personal Developer Instance (PDI) to master scoping hands-on.</p><h3>Exercise 1: Create a Scoped Application</h3><ul><li><strong>Navigation Path:</strong> <strong>All</strong> &gt; <strong>System Applications</strong> &gt; <strong>Studio</strong></li><li><strong>Configuration Steps:</strong></li></ul><ol><li>Click <strong>Create Application</strong>.</li><li>Name: Book Tracker</li><li>Scope: (Let ServiceNow auto-populate it, e.g., x_yourid_book_trac)</li><li>Click <strong>Create</strong>.</li><li>In the “Roles” screen and “Formats” screens, simply click <strong>Continue</strong> / <strong>Done</strong> to open the app in Studio.</li></ol><ul><li><strong>Expected Result:</strong> Studio opens a new tab dedicated entirely to your Book Tracker application.</li><li><strong>What to Observe:</strong> Look at the top right corner of the Studio interface. You will see your active application listed as Book Tracker.</li></ul><h3>Exercise 2: Create a Custom Table Inside the Application</h3><ul><li><strong>Navigation Path:</strong> Inside <strong>Studio</strong>, click <strong>Create Application File</strong>.</li><li><strong>Configuration Steps:</strong></li></ul><ol><li>Select <strong>Data Model</strong> &gt; <strong>Table</strong>, then click <strong>Create</strong>.</li><li>Label: Book</li><li>Notice the Name field automatically populates with something like x_yourid_book_trac_book.</li><li>Under the <strong>Application Access</strong> tab, ensure <strong>Accessible from</strong> is set to <strong>All application scopes</strong>, and check the <strong>Can read</strong> and <strong>Can create</strong> checkboxes.</li><li>Click <strong>Submit</strong>.</li></ol><ul><li><strong>Expected Result:</strong> The table is generated with baseline fields (Sys ID, Created, Updated, etc.).</li><li><strong>What to Observe:</strong> Look at the prefix of the table name. It enforces your application scope.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87bd7c862a12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Generative AI Apps Using Gemini and Streamlit: My Upskilling Journey with Google Cloud]]></title>
            <link>https://medium.com/@heynilesh05/building-generative-ai-apps-using-gemini-and-streamlit-my-upskilling-journey-with-google-cloud-0a4b00be7958?source=rss-de53c73e1f89------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a4b00be7958</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[gemini]]></category>
            <dc:creator><![CDATA[ENUGANDHULA NILESH]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 02:22:55 GMT</pubDate>
            <atom:updated>2025-08-04T02:22:55.677Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of the <strong>#GenAIExchange</strong> program by Google Cloud, I recently completed the course <strong>“Develop GenAI Apps with Gemini and Streamlit”</strong> and earned my skill badge.</p><p>This experience was not just educational, it was transformational. Here’s what I learned and built:</p><h3>Accessing Gemini Models via PaLM API</h3><p>Google’s <strong>Gemini</strong> models are powerful multimodal LLMs, and using the PaLM API, I learned how to:</p><ul><li>Send prompts to Gemini</li><li>Handle structured responses</li><li>Fine-tune the conversation flow for better app behavior</li></ul><h3>Building with Streamlit</h3><p>Streamlit allowed me to turn AI ideas into shareable web apps <strong>quickly and beautifully</strong>. Some of the things I built:</p><ul><li>A real-time chat interface with Gemini</li><li>A prompt experimentation tool</li><li>A text-to-insights summarizer using Gemini’s outputs</li></ul><h3>The Impact of This Learning</h3><p>This course showed me how <strong>accessible and impactful</strong> GenAI app development can be. Combining powerful models like <strong>Gemini</strong> with intuitive tools like <strong>Streamlit</strong> means anyone from developers to domain experts can create AI-powered applications in minutes.</p><h3>Takeaway</h3><p>This badge wasn’t just a checkbox , it’s a launchpad into building with <strong>cutting-edge GenAI</strong>. I look forward to applying this in real-world projects and contributing to the future of AI innovation.</p><p>👉 Want to try it yourself? Head over to <a href="https://www.cloudskillsboost.google/">https://www.cloudskillsboost.google</a></p><p>#GenAIExchange #GoogleCloud #GeminiAI #Streamlit #GenerativeAI #Upskilling #AIApps #PaLMAPI #FutureOfAI #AIForEveryone</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a4b00be7958" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>