What are Global and Page Variables in Titan?

Global Variables persist across all pages in a Titan project. Page Variables exist only on the current page and reset on navigation. Both store data for dynamic content and logic.

When should you use Global vs Page Variables?

Use Global for data shared across pages (user info, selected records). Use Page for temporary data that only matters on one screen (form inputs, local calculations).

Titan Global and Page Variables

Titan Global and Page Variables: Mastering State Management in Titan Web

Variables are the nervous system of any Titan Web application. Understanding the difference between Global Variables and Page Variables – and knowing when to use each – is what separates a brittle proof-of-concept from a solid, maintainable enterprise implementation. This guide covers everything Titanixforce senior implementers apply in production deployments.

Page Variables

Page Variables exist within the scope of a single Titan page. They are created, read, and updated only within that page – they do not persist when the user navigates to a different page. Think of them as the local state of a single view in your application.

Page Variables are ideal for storing: form field values before submission, the result of a Get operation to display in the current page, toggle states (show/hide sections), loop counters, and temporary calculated values used in conditionals.

Global Variables

Global Variables persist across all pages within a Titan project during a single user session. Once set on Page 1, they are readable and writable on Page 3, Page 7, or any other page. This makes them the primary mechanism for passing data across a multi-page workflow.

Global Variables are ideal for storing: the authenticated user Salesforce ID (set on login, used throughout the session), a parent record ID created on an earlier page (used by later Push operations to create related records), user role or permission flags that drive conditional logic site-wide, and cart or selection state in multi-step ordering flows.

Variable Types

Both Page and Global Variables support multiple data types: Text, Number, Boolean, Date, DateTime, List (array), and Object (JSON). Choosing the correct type matters – using a Text variable to store a number that will be used in calculations leads to type-mismatch errors that are hard to debug.

URL Parameters as Variable Sources

One of the most powerful patterns in Titan is reading URL query parameters into variables on page load. This enables deep linking – passing a Salesforce record ID, a campaign source, or a session token in the URL and using it to pre-populate Get operations, personalize content, or route the user to the correct workflow branch.

Variables in Conditional Logic

Variables are the backbone of Titan conditional logic. Every visibility rule, required field condition, and Push/Get filter can reference a variable. The pattern is: Get data into a variable, evaluate the variable in a condition, show or hide elements accordingly. This creates dynamic, responsive interfaces that adapt to each user and context without hardcoded values.

Best Practices

Establish a naming convention before you start building – prefixing Global Variables with g_ and Page Variables with p_ prevents confusion in complex projects.
Initialize Global Variables with default values to prevent null-reference errors on first page load.
Audit variable usage before go-live – unused variables add noise and can cause unexpected behavior if accidentally referenced.
Document critical Global Variables in your project spec – what they store, where they are set, and where they are consumed.

Conclusion

Ready to go deeper? This article covers the foundations. For advanced patterns used in enterprise implementations, read our follow-up: Mastering State Management in Titan Web: A Senior Implementer’s Guide.

Mastering Titan variables is mastering Titan itself. When used strategically, Global and Page Variables make complex multi-page, multi-object Salesforce workflows feel effortless to the end user – while keeping the implementation clean and maintainable. At Titanixforce, variable architecture is part of every project discovery conversation we have. Talk to our team to see how we approach Titan implementation for enterprise Salesforce environments.

Need Expert Help?

With 12+ years of Salesforce and 7+ years of Titan implementation experience, Titanixforce delivers projects on time and on budget. Get in touch to discuss your project.