sn-scripting

Name: sn-scripting
Author: guilhermebatista-gbs

15stars9forks

How to install sn-scripting?

guilhermebatista-gbs/servicenow-architect/sn-scripting

$npx -y skills add guilhermebatista-gbs/servicenow-architect --skill sn-scripting

Installs into the current project.

Summary

Generates GlideRecord queries, Script Include classes, and client scripts for ServiceNow scripting. Use for Business Rules, Scheduled Jobs, server-side Script Includes, and client-side g_form/g_user scripts — including the script bodies inside Fluent SDK metadata definitions. Met

Files · 1

View on GitHub

SKILL.md

1	# ServiceNow Legacy Scripting
2
3	ServiceNow legacy scripting uses the GlideRecord API for server-side data access, Script Include classes for reusable server-side logic, Business Rules for server-side automation, and g_form/g_user/g_list for client-side form manipulation. All APIs are described in the reference files below.
4
5	## References
6
7	Read these files when you need them — do not pre-load all references at session start. Paths are relative to the skill root (the directory containing this file).
8
9	\| File \| When to Read \|
10	\|------\|-------------\|
11	\| `references/gliderecord.md` \| Generating or reviewing GlideRecord queries, CRUD operations, or addQuery/getValue patterns \|
12	\| `references/server-side.md` \| Generating Script Includes, Business Rules, or using GlideSystem (gs.*) logging \|
13	\| `references/client-side.md` \| Generating Client Scripts using g_form, g_user, or g_list; or any client-side form manipulation \|
14	\| `references/gotchas.md` \| Before generating or reviewing any ServiceNow script — check for hallucination traps \|
15
16	## Scripts
17
18	\| Script \| When to use \|
19	\|--------\|------------\|
20	\| `scripts/validate-script.sh` \| When validating a ServiceNow script file for common issues before deploying \|
21
22	## Examples
23
24	Use these as structural templates — only read the example that matches your target type, do not pre-load all examples:
25
26	\| File \| Demonstrates \|
27	\|------\|-------------\|
28	\| `assets/examples/gliderecord-crud.js` \| Complete GlideRecord CREATE, READ (single and multi), UPDATE, DELETE with correct getValue() usage \|
29	\| `assets/examples/script-include-class.js` \| Script Include using Class.create() pattern with initialize(), utility methods, and type property \|
30	\| `assets/examples/client-script-gform.js` \| Client Script onLoad/onChange handlers using g_form.getValue(), g_form.setMandatory(), g_user.hasRole() \|
31
32	## Hard Rules
33
34	1. In a Fluent SDK project, know which layer you're on.
35	If the workspace contains `now.config.json`, `.now.ts` files, or imports from `@servicenow/sdk/core`,
36	the developer is working in a Fluent SDK application. Two different layers apply:
37	- Metadata definition (creating tables, ACLs, Business Rules, Script Includes as objects) →
38	that is Fluent's job. Redirect to `../sn-sdk-fluent/` (read its main file) instead of writing
39	GlideRecord "setup scripts" or standalone legacy artifacts.
40	- Script bodies (the logic inside a `script` property, a `Now.include()` file, or `src/server/`
41	modules) → that is exactly this sub-skill. Those bodies are standard Glide server-side JS —
42	apply this file's rules and references to them.
43
44	2. GlideRecord is server-side only — never generate GlideRecord in a Client Script. Use GlideAjax.
45
46	3. Always call query() before next() — while(gr.next()) without gr.query() never executes.
47
48	4. Use getValue() in loops — gr.field_name returns a pointer; gr.getValue('field_name') returns the string value.
49
50	5. Never invent method names — no gr.getField(), gr.setQuery(), gr.addOrder(). Prefer the methods documented in `references/gliderecord.md`; it is a curated subset, not the whole platform API. If a real, commonly used method isn't listed (check the official ServiceNow API docs), you may use it — say explicitly that it's outside the local reference and worth verifying. What is never acceptable is guessing a plausible-sounding name.
51
52	## Behavior by Task Type
53
54	### Generating
55
56	1. Check for Fluent SDK signals first (Hard Rule 1) — if detected, decide the layer: metadata definition goes to `../sn-sdk-fluent/`; script bodies stay here.
57	2. Identify the script context: server-side (Business Rule, Script Include) or client-side (Client Script).
58	3. For server-side: read `references/gliderecord.md` for CRUD patterns, `references/server-side.md` for Script Include structure and Business Rule context variables.
59	4. For client-side: read `references/client-side.md` for g_form/g_user/g_list APIs. Never generate GlideRecord in a client script (Hard Rule 2).
60	5. Use example files in `assets/examples/` as working templates.
61
62	### Reviewing
63
64	1. Check Hard Rules 3 and 4: query() before next(), getValue() in loops.
65	2. Verify no GlideRecord in client-side code (Hard Rule 2).
66	3. Verify no invented methods — compare against `references/gliderecord.md` documented API (Hard Rule 5).
67	4. Run `scripts/validate-script.sh <file>` to check for GlideRecord in client scripts, bare setAbortAction, and g_form misuse.
68
69	### Explaining
70
71	1. Route the developer to the rele

People who liked this also viewed

6 picks

Type

sn-scripting

15stars9forks

View on GitHub

How to install sn-scripting?

guilhermebatista-gbs/servicenow-architect/sn-scripting

$npx -y skills add guilhermebatista-gbs/servicenow-architect --skill sn-scripting

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# ServiceNow Legacy Scripting
2
3	ServiceNow legacy scripting uses the GlideRecord API for server-side data access, Script Include classes for reusable server-side logic, Business Rules for server-side automation, and g_form/g_user/g_list for client-side form manipulation. All APIs are described in the reference files below.
4
5	## References
6
7	Read these files when you need them — do not pre-load all references at session start. Paths are relative to the skill root (the directory containing this file).
8
9	\| File \| When to Read \|
10	\|------\|-------------\|
11	\| `references/gliderecord.md` \| Generating or reviewing GlideRecord queries, CRUD operations, or addQuery/getValue patterns \|
12	\| `references/server-side.md` \| Generating Script Includes, Business Rules, or using GlideSystem (gs.*) logging \|
13	\| `references/client-side.md` \| Generating Client Scripts using g_form, g_user, or g_list; or any client-side form manipulation \|
14	\| `references/gotchas.md` \| Before generating or reviewing any ServiceNow script — check for hallucination traps \|
15
16	## Scripts
17
18	\| Script \| When to use \|
19	\|--------\|------------\|
20	\| `scripts/validate-script.sh` \| When validating a ServiceNow script file for common issues before deploying \|
21
22	## Examples
23
24	Use these as structural templates — only read the example that matches your target type, do not pre-load all examples:
25
26	\| File \| Demonstrates \|
27	\|------\|-------------\|
28	\| `assets/examples/gliderecord-crud.js` \| Complete GlideRecord CREATE, READ (single and multi), UPDATE, DELETE with correct getValue() usage \|
29	\| `assets/examples/script-include-class.js` \| Script Include using Class.create() pattern with initialize(), utility methods, and type property \|
30	\| `assets/examples/client-script-gform.js` \| Client Script onLoad/onChange handlers using g_form.getValue(), g_form.setMandatory(), g_user.hasRole() \|
31
32	## Hard Rules
33
34	1. In a Fluent SDK project, know which layer you're on.
35	If the workspace contains `now.config.json`, `.now.ts` files, or imports from `@servicenow/sdk/core`,
36	the developer is working in a Fluent SDK application. Two different layers apply:
37	- Metadata definition (creating tables, ACLs, Business Rules, Script Includes as objects) →
38	that is Fluent's job. Redirect to `../sn-sdk-fluent/` (read its main file) instead of writing
39	GlideRecord "setup scripts" or standalone legacy artifacts.
40	- Script bodies (the logic inside a `script` property, a `Now.include()` file, or `src/server/`
41	modules) → that is exactly this sub-skill. Those bodies are standard Glide server-side JS —
42	apply this file's rules and references to them.
43
44	2. GlideRecord is server-side only — never generate GlideRecord in a Client Script. Use GlideAjax.
45
46	3. Always call query() before next() — while(gr.next()) without gr.query() never executes.
47
48	4. Use getValue() in loops — gr.field_name returns a pointer; gr.getValue('field_name') returns the string value.
49
50	5. Never invent method names — no gr.getField(), gr.setQuery(), gr.addOrder(). Prefer the methods documented in `references/gliderecord.md`; it is a curated subset, not the whole platform API. If a real, commonly used method isn't listed (check the official ServiceNow API docs), you may use it — say explicitly that it's outside the local reference and worth verifying. What is never acceptable is guessing a plausible-sounding name.
51
52	## Behavior by Task Type
53
54	### Generating
55
56	1. Check for Fluent SDK signals first (Hard Rule 1) — if detected, decide the layer: metadata definition goes to `../sn-sdk-fluent/`; script bodies stay here.
57	2. Identify the script context: server-side (Business Rule, Script Include) or client-side (Client Script).
58	3. For server-side: read `references/gliderecord.md` for CRUD patterns, `references/server-side.md` for Script Include structure and Business Rule context variables.
59	4. For client-side: read `references/client-side.md` for g_form/g_user/g_list APIs. Never generate GlideRecord in a client script (Hard Rule 2).
60	5. Use example files in `assets/examples/` as working templates.
61
62	### Reviewing
63
64	1. Check Hard Rules 3 and 4: query() before next(), getValue() in loops.
65	2. Verify no GlideRecord in client-side code (Hard Rule 2).
66	3. Verify no invented methods — compare against `references/gliderecord.md` documented API (Hard Rule 5).
67	4. Run `scripts/validate-script.sh <file>` to check for GlideRecord in client scripts, bare setAbortAction, and g_form misuse.
68
69	### Explaining
70
71	1. Route the developer to the rele

People who liked this also viewed

6 picks

Type