---
title: "JavaScript Script Editor"
slug: "erp-primavera-template-1"
updated: 2026-10-27T16:16:42Z
published: 2026-10-27T16:16:42Z
canonical: "help.ila.cegid.com/erp-primavera-template-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.ila.cegid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# JavaScript Script Editor

- [x] PT
- [ ] ES
- [x] AO
- [x] CV
- [x] MZ

- [ ] Professional
- [ ] Executive
- [x] Public Sector
- [ ] Omnia
- [x] Evolution

---

> [!NOTE]
> Available with Service Release 6

You can **create and edit JavaScript scripts** in the ERP, with the goal of simplifying *script* editing for each organization's use.

The editor consists of **three sections** (code editor, context window, and Cegid Pulse) that **interact with each other** and let script editing be as simple as possible.

---

## Code Editor

The code editor is the main area of this feature. The first time you access the feature, this area **shows no data**, to let you **enter the script directly in the application.**

This editor **supports the IntelliSense feature,** which is essentially an **intelligent writing assistant** that **analyzes the code in real time** to predict what will be typed next. For a JavaScript developer, this assistant **acts as living documentation and an instant proofreader inside the editor**. To support this, the editor uses an internal feature to read and analyze the script:

- **Static Analysis**: the editor reads variables and functions;
- **Context Prediction**: when you type, or press Ctrl + Space, the editor filters only the options that are valid for that specific point in the code.

IntelliSense speeds up development through the following features:

- **Intelligent auto-complete**: avoids the need to memorize or type long function names, by listing the language's variables, methods, and keywords as soon as you start typing;
- **Parameter Information:** when you open a function's parentheses, the editor immediately shows the required arguments, the expected types, and what the function returns, reducing the need to check external documentation;
- **Quick Info (Hover)**: hovering the mouse cursor over any element of the code shows the method's signature details and the associated explanatory comments.

---

## Context Window

Organized as a tree, this window lets you **view the entities available** when the script is evaluated. At the top of this window, you can **search for objects or properties** matching specific text.

If an item in this window **has details**, an **indicator** is shown on the left side, so you can expand that item. To expand or collapse an item using the keyboard, you can press **+** or **-**, or use the mouse to click the indicator. When you select an item, the box at the bottom shows the information available for that item.

Double-clicking an item in the tree inserts the code to access that object, property, or method in the editor, at the cursor's current position.

---

## Cegid Pulse

The bottom section of the window is dedicated to Cegid Pulse, and includes the text box where you can specify a goal.

With this feature, you can ask an artificial intelligence agent for help to **quickly create a script**. This agent has information about the objects and their respective properties and methods. Whenever possible, it will generate a script that matches the instructions given.

To get the best possible results, we recommend that your request:

- be as clear and detailed as possible about the goal;
- direct the agent, for example by pointing out properties and/or the object you may need.

Clicking the **Pulse** option will ask Pulse to generate the code, and the result will be inserted into the editor, overwriting any existing code.

> [!WARNING]
> The code is automatically generated by an Artificial Intelligence tool. While the goal is to provide quick, functional solutions, **the code is provided as is** (*as-is*), without warranties of any kind, express or implied. Before using it, we recommend the following best practices:
> 
> - **Review**: analyze and understand the code line by line.
> - **Testing**: run the script first in a test environment, and never directly in a production company.
> 
> Using this code is entirely the user's responsibility; Cegid is not liable for any errors, data loss, or service interruptions resulting from its execution.