Client Script vs UI Policy dans ServiceNow

 

Quand utiliser lequel (et éviter les problèmes de performance)

Beaucoup de débutants ServiceNow se demandent :

Dois-je utiliser un Client Script ou une UI Policy ?

Les deux peuvent :

  • rendre un champ obligatoire

  • afficher / masquer un champ

  • rendre un champ en lecture seule

  • contrôler le comportement d’un formulaire

Mais choisir le mauvais outil peut ralentir les formulaires et compliquer la maintenance.

Différence principale

UI Policy → Comportement basé sur la configuration (sans code)
Client Script → Logique basée sur du script (JavaScript)

Que fait une UI Policy ?

La UI Policy est utilisée pour des conditions simples.

Exemple :
Si Catégorie = Matériel → afficher le champ Numéro de série.

Aucun code nécessaire.

Avantages

  • Plus rapide

  • Plus propre

  • Facile à maintenir

  • Accessible aux administrateurs

Que fait un Client Script ?

Le Client Script est utilisé lorsque la logique est plus complexe.

Exemples :

  • Valider un format (ID employé)

  • Calculer automatiquement une valeur

  • Contrôler la soumission

Il nécessite du JavaScript.

Types de Client Script

  • onLoad

  • onChange

  • onSubmit

  • onCellEdit

Ils permettent des validations et traitements dynamiques.

Comparaison pratique

BesoinUI PolicyClient Script
Afficher / masquer✔✖
Champ obligatoire✔✖
Lecture seule✔✖
Condition simple✔✖
Validation complexe✖✔
Calcul automatique✖✔
Appel API✖✔

Impact sur la performance

Utiliser un Client Script inutilement peut ralentir le formulaire.

La UI Policy est plus rapide car elle utilise la logique native de la plateforme.

Règle importante :

Si la UI Policy peut le faire, n’utilisez pas de Client Script.

Erreur fréquente

Utiliser un Client Script pour simplement afficher ou masquer un champ.

Cela :

  • augmente le temps de chargement

  • complique le débogage

  • réduit la performance

Bonne pratique

UI Policy = Comportement du formulaire
Client Script = Intelligence du formulaire

Un bon développeur ServiceNow utilise d’abord la configuration, puis le script si nécessaire.

Conclusion

Les deux outils sont puissants mais ont des objectifs différents.

Les utiliser correctement améliore la performance, la lisibilité et la maintenance.


💼 Support professionnel disponible

Si vous rencontrez des problèmes sur des projets réels liés au développement backend d’entreprise ou à l’automatisation des workflows, je propose des services de conseil payants, de débogage en production, de support projet et de formations ciblées.

Les technologies couvertes incluent Java, Spring Boot, PL/SQL, Azure, CMS, ainsi que l’automatisation des workflows (jBPM, Camunda BPM, RHPAM), DMN/Drools.

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital lectern | Digital rostrum | Digital metal podium     

Comments

Post a Comment

Popular posts from this blog

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more