File Management

LMDA Composer supports working with local files on your computer, allowing you to develop scripts outside of LogicModules and manage your own script library.

File Types

Supported Extensions

Extension	Language	Notes
.groovy	Groovy	Groovy scripts
.ps1	PowerShell	PowerShell scripts
.txt	Plain text	Uses tab language setting

When you open a file, the extension determines the language, syntax highlighting applies automatically, and execution mode defaults to Freeform.

---

Opening Files

Method	Action
Welcome Screen	Click Open File and select from the system dialog
Keyboard	Press Ctrl+K, O / Cmd+K, O
Drag and Drop	Drag a file onto the LMDA Composer window
Recent Files	Click a file from the recent files list on the welcome screen

---

Open Module Directory

Open a saved module folder to restore a previously saved LogicModule with its metadata and portal binding intact.

What It Does

• Restore Module Binding — Automatically reconnects to the original portal and module from saved metadata
• Enable Commit Workflow — Push changes back to LogicMonitor just like a freshly loaded module
• Load All Scripts — Opens the main script plus any AD scripts or pre-scripts in the folder

How to Access

Method	Action
Keyboard	Press Cmd+K, F to open directly
Actions Menu	Click Actions → Open Module Folder in the toolbar
Welcome Screen	Click Open Module Folder on the welcome screen

Module Directory Structure

When you save a portal-bound module to disk, LMDA Composer creates a folder with the following structure:

my-datasource/
├── script.groovy          # Main collection script
├── ad-script.groovy       # Active Discovery script (if applicable)
├── pre-script.groovy      # Pre-script (if applicable)
└── module.json            # Module metadata + portal binding

The module.json file contains:

• Module ID and name
• Portal hostname and module type
• Script type mappings
• Original module metadata for diffing

Use Cases

Version Control

Track module changes with Git:

1. Save module to a local folder
2. Initialize a Git repository: git init
3. Commit changes as you develop
4. Push to GitHub/GitLab for backup and collaboration

This provides full version history that LogicMonitor doesn’t offer natively.

Team Collaboration

Share module development:

1. Save module to a shared repository
2. Team members clone the repo
3. Each developer opens the module directory
4. Changes can be reviewed via pull requests
5. One person commits approved changes to LM

Backup & Restore

Keep local copies of important modules:

1. Save critical modules to disk as backups
2. Store in cloud-synced folder (Dropbox, OneDrive)
3. Restore anytime by opening the module directory
4. Compare local vs portal versions before committing

Offline Development

Work without portal connection:

1. Save module while connected
2. Develop offline with full editor features
3. Reconnect to portal when ready
4. Open module directory and commit changes

Workflow Example

1. Load module from portal using the LogicModule Browser

2. Save to disk via Actions → Save As or Cmd+K, Shift+S

3. Initialize Git in the module folder for version tracking

4. Make changes and commit locally with descriptive messages

5. Later, open module directory with Cmd+K, F

6. Push changes back to portal using the Commit button

Module Binding Persistence

The module.json file stores all the information needed to reconnect to your portal. As long as this file exists and the module still exists in your portal, you can restore the full commit workflow.

---

Creating New Files

1. Click New File on welcome screen, or click + in the tab bar, or press Ctrl+K, N

2. File opens with your default language setting

3. Start writing your script (or insert a template from Snippets)

4. Save with Ctrl+S when ready

---

Saving Files

Save

Keyboard: Ctrl+S / Cmd+S

First save: Opens a dialog to choose location and filename.

Subsequent saves: File updates in place, no dialog appears, dirty indicator clears.

Save As

Keyboard: Ctrl+K, Shift+S / Cmd+K, Shift+S

Creates a copy at a new location. Original file remains unchanged.

---

File System Access API

LMDA Composer uses the modern File System Access API for seamless file operations.

Browser Compatibility

Browser	Support	Notes
Chrome	Full Support	Direct file reading/writing, file handles persist across sessions
Edge	Full Support	Same capabilities as Chrome
Brave/Vivaldi	Requires Setup	May need to enable the File System Access API flag

Brave Browser Setup

If File System Access is not available in Brave:

1. Open brave://flags in a new tab

2. Search for “File System Access API”

3. Set it to Enabled

4. Restart your browser

Vivaldi Setup

For Vivaldi browser:

1. Open vivaldi://extensions

2. Select “LMDA Composer”

3. Enable “Allow access to file URLs”

---

Auto-Save Drafts

LMDA Composer automatically saves drafts to protect your work.

Feature	Description
How It Works	Drafts saved every 30 seconds to browser local storage. Recovered on next session.
Draft Recovery	If browser closes unexpectedly, draft recovery dialog appears on next open. Click Restore or Discard.

Draft Limitations

• Only unsaved changes are drafted
• Very large files may not draft completely
• Drafts are per-browser, not synced across devices

---

File Handles

Persistent Handles

For supported browsers:

• File handles saved to session
• Reopening restores handles
• Continue editing from where you left off

Handle Expiration

Handles expire when:

• Browser is fully closed
• Permissions are revoked
• File is moved or deleted

Refreshing Handles

If a handle expires:

1. File shows as “Unconnected”
2. Click Reconnect in tab
3. Select the file again

---

Tabs and Files

Tab Names

• Local files show the filename
• Unsaved files show “Untitled”
• Module tabs show module name with link icon

Dirty State

The dirty dot (•) indicates:

• Unsaved changes to disk
• Modified since last save
• Will prompt on close

Close Confirmation

Closing a dirty tab shows options:

• Save & Close
• Discard
• Cancel

---

Recent Files

Viewing Recent Files

The welcome screen shows recent files with:

• File name and path
• Last opened date
• Language indicator

Managing Recent Files

• Click to open a recent file
• Use the remove button to clear items from the list
• List auto-cleans invalid entries

Recent Files Limit

Configure in Settings:

• Default: 10 files
• Range: 5-50 files

---

Best Practices

• Organize Your Scripts — Create a folder structure like scripts/production/datasources/ for easy navigation
• Backup Important Scripts — Save to cloud-synced folders (Dropbox, OneDrive) or use version control (Git)
• Use Naming Conventions — Use clear names like DS_Linux_CPU_Usage.groovy or PS_Windows_Services.ps1

Local Development Workflow

1. Create local file

2. Develop and test script

3. When ready, copy to module or import as new

4. Keep local copy as backup

---

Next Steps

Snippets Library Use built-in and custom code snippets to speed up development.