Versaa Platform Overview¶
Versaa is Aareon's mobile workflow and forms platform. Legacy brand names: 1st Touch, Aareon Mobile.
- Forms — XML-based data capture screens, displayed in the Aareon Mobile app on mobile devices.
- Workflows — BPMN diagrams built in Management Studio. Triggered by form submission message events. Handle data writes, CRM classifications, raising repairs, generating documents, sending emails.
- Backend — SQL Server database. Form data is stored as XML in
Task.Task.TaskXml. - Interfaces with — Aareon QL (housing management system).
Environments¶
| Environment | Name | Purpose |
|---|---|---|
| Development | TcyDev / PrtyDev |
All development work happens here |
| Test | PrtyTest |
Business testing and sign-off |
| Live | PrtyLive |
Production |
NEVER develop in Test or Live. Changes flow strictly: Dev → Test → Live.
Servers¶
| Role | Server |
|---|---|
| App server (Live) | AAREON-TCH01 |
| App server (Test/Dev) | AAREON-TCH02 |
| Database server | aareon-sql01.lincolnshirehp.com |
Login format: lincolnshirehp\<username> — e.g. lincolnshirehp\SALEEI
The PCA Process¶
PCA (Property Create and Access) is the standard pattern for forms that work against a property in QL. When a user searches for a property and taps a form button, all property data is automatically pushed to the form via mapped fields.
A PCA form fires [FormName].PCACompletion on completion, which triggers:
1. The form-specific workflow (if one exists)
2. The Generic Task Completion Workflow (handles document generation, email)
Key Conventions¶
- z_ prefix — form items prefixed
z_are temporary/working fields not saved to the Data Warehouse. - Standard form items — every form should include: Debugger element, Testing button, Bypass Validation button, Abandon Form button.
- Standard blocks — property-based forms use:
Contact,PK,Email,DocEx,PCA Type Form,Safeguarding,Insights,GenBPI. - Test property —
D6621 = 7 Abbey Rd / Dorothy Stocks in Dev. Peter has pre-loaded all red flags, insights and alerts here.
QL Integration¶
- QL data is surfaced in Versaa forms via pre-configured queries.
- CRM contacts can only be raised against people, not properties — tenancy and rent account data links through to the client number in QL.
- Versaa writes to HPM First Touch staging tables; QL processes these every ~2–5 minutes.
Key staging tables:
- HGMCNTCT — CRM contact creation staging
- HGMCLIENT — client update staging
- hgm1stup — property data
- hpm1stoa — order tracking (appointments come from here)
- hpm1stnt — notes
QL Environment Mapping¶
There is no "Dev" environment in QL. Versaa Dev (PrtyDev) connects to QL Acceptance. The mapping is:
| Versaa | QL environment | QL database |
|---|---|---|
Dev (PrtyDev) |
Acceptance | a_qlfdat ← confirm via workflow variable |
Test (PrtyTest) |
Test | t_qlfdat |
Live (PrtyLive) |
Live | qlfdat (no prefix) |
Dev could also point to u_qlfdat (User Training) depending on config. To confirm which QL database Versaa Dev is connected to: Management Studio → Workflow Variables → QL → look for DB connection string.
QL also has a "Config" environment — never go into it.
Accessing QL Non-Live Environments¶
Via Citrix → Apps → "QL non-live environments" → select Acceptance, Test, User Training, or Config from the popup. Do not use Remote Desktop names.
QL CRM Classifications¶
QL CRM Classifications define: "when a contact arrives with these class levels, fire this action code." Configured at: QL Housing → Maintenance → HGM Contact Management → HGM CRM Classifications.
Key gotcha: a row can exist with the correct class levels but no action code — contacts matching that row will be silently discarded (no action, no error). Always verify the action code field is populated.
Changes to CRM Classifications must be manually replicated across all three QL environments (Acceptance, Test, Live).
RT0016 — Rent Statement Request Action¶
Action code RT0016 = "Rent statement request" workflow task routed to the Income Officer for that property. The Income Officer is the responsible person recorded against the property in QL Property Maintenance (HGMPRT1-4).
Self-serve rent statement contacts from the MyLHP portal arrive with:
- class_level1 = RENTS, class_level2 = BALANCE, class_level3 = STATEMENT, class_level4 = SELFSERVE
- contact_source = W
Officer/arrears-automated contacts use class_level4 = OFFICE and contact_source = L.
Workflow Instances¶
Every workflow trigger creates a workflow instance. To inspect: 1. Management Studio → Workflows → Search Instances 2. Find instance, click ellipsis → View Workflow Instance 3. Click ellipsis on any step → View XML to see data at that point
Instances can be retried without re-submitting the form from a device.