Update 01. Predefined Contact Variables in Glific.md

[SangeetaMishr]

added a line for limit

Summary by CodeRabbit

• Documentation
  • Updated timestamps and refreshed flow-variable docs.
  • Expanded guidance distinguishing Flow Variables and Contact Variables, including usage scenarios, naming conventions, and when to choose each.
  • Clarified that unlimited contact variables are supported and added tips for organizing variables to avoid complexity.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated two Flow Variables docs: changed Last Updated timestamps and expanded guidance distinguishing Flow Variables (@results) from Contact Variables (@contact), adding advice on unlimited custom contact variables, organization, usage scenarios, and naming conventions.

Changes

Cohort / File(s)	Summary
Predefined contact variables doc docs/4. Product Features/03. Flows/3. Flow Variables/01. Predefined Contact Variables in Glific.md	Updated "Last Updated" timestamp to December 2025.
Flow vs Contact variables guidance docs/4. Product Features/03. Flows/3. Flow Variables/02. Flow variables vs Contact variables.md	Updated "Last Updated" timestamp to December 2025 and expanded content with: introduction clarifying unlimited contact variables, distinction between Flow Variables (@results) and Contact Variables (@contact), usage scenarios, organization guidance, and naming conventions.

Sequence Diagram(s)

(omitted — changes are documentation only)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update 02. Flow variables vs Contact variables.md #430: Edits the same "02. Flow variables vs Contact variables.md" content; likely overlapping explanatory changes.
• Update 01. Predefined Contact Variables in Glific.md #429: Related timestamp/content updates to "Predefined Contact Variables" doc.
• Update 09. Update the contact.md #439: Adds related guidance and links within the flow vs contact variables documentation area.

Suggested reviewers

• Fawas003

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title only references updating file 01, but the changeset actually includes substantial updates to both file 01 and file 02 with new content added to file 02.	Update the title to reflect both files being changed, such as 'Update contact and flow variable documentation' or include file 02 in the title.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Predefined-Contact-Variables-in-Glific.md

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7467b2e and c277bef.

📒 Files selected for processing (2)

• docs/4. Product Features/03. Flows/3. Flow Variables/01. Predefined Contact Variables in Glific.md
• docs/4. Product Features/03. Flows/3. Flow Variables/02. Flow variables vs Contact variables.md

✅ Files skipped from review due to trivial changes (1)

• docs/4. Product Features/03. Flows/3. Flow Variables/01. Predefined Contact Variables in Glific.md

🔇 Additional comments (2)

docs/4. Product Features/03. Flows/3. Flow Variables/02. Flow variables vs Contact variables.md (2)

7-7: ✓ Timestamp updated appropriately.

The last updated timestamp has been correctly updated from October 2025 to December 2025.

---

14-15: Introductory guidance effectively enhances clarity.

The expanded introduction successfully:

• Communicates the capacity for contact variables upfront
• Provides practical guidance on organizing variables
• Introduces the two-variable-type framework

The flow into the existing variable types is natural. The "unlimited number of contact variables" claim aligns with Glific's design, which supports dynamic custom field creation without documented constraints.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Deployed on https://deploy-preview-531--glific-docs.netlify.app

[tanuprasad530]

Shouldn't this come in the next page, with title "Flow variables vs Contact variables"? Right it is added under pre-defined variables and that is limited or rather that cannot be created/modifies by the user at all. I would suggest to move it in the subsection "Using Contact Variables" in the page - "Flow variables vs Contact variables"

[SangeetaMishr]

@tanuprasad530 will move it to that page