- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi Team,
We are configuring virtual agent and we can see some users using vaVars, vaContext or vaSystem as some variables in scripting in Virtual agent. Where these functions are stored ??? and I can see some of them are using
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @geogeorge
These are predefined objects available in Virtual Agent topic scripting (in the Scripting blocks or Script actions).
They are not ServiceNow global objects, meaning you won’t find them in the system dictionary, business rules, or script includes. Instead, they are injected at runtime by the Virtual Agent framework.
- vaVars → Stores topic-level variables (the values captured or defined while the user interacts with the bot).
- vaContext → Holds contextual information about the current conversation (like channel, user, or conversation state).
- vaSystem → Contains system-level information used internally by the Virtual Agent (e.g., metadata about conversation flow, backend handling, etc.).
So, these aren’t “stored” in the DB as script includes. They are built-in objects provided by the Virtual Agent runtime engine.
See the reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @geogeorge
These are predefined objects available in Virtual Agent topic scripting (in the Scripting blocks or Script actions).
They are not ServiceNow global objects, meaning you won’t find them in the system dictionary, business rules, or script includes. Instead, they are injected at runtime by the Virtual Agent framework.
- vaVars → Stores topic-level variables (the values captured or defined while the user interacts with the bot).
- vaContext → Holds contextual information about the current conversation (like channel, user, or conversation state).
- vaSystem → Contains system-level information used internally by the Virtual Agent (e.g., metadata about conversation flow, backend handling, etc.).
So, these aren’t “stored” in the DB as script includes. They are built-in objects provided by the Virtual Agent runtime engine.
See the reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Rafael Batistot ,
I can see that vaVars have been used in some of my existing topics. Even though I couldn't identify where they are defined, what exactly do vaVars do? Is this something that we should define, or is it system-defined?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
No, you don’t need to define vaVars yourself — ServiceNow provides it automatically.
What you define are the properties inside vaVars, such as vaVars.ticketNumber or vaVars.preferredLanguage.
If you try to use vaVars.someKey without setting it first, it will just be undefined.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
So you are saying some of them are already defined right?
Can I see those oob defined vaVars values?