MyLHP App & Self Serve Portal — Testing Guide¶
Environment Overview¶
| Environment | URL / Access | Purpose |
|---|---|---|
| SS Test (portal) | Web portal URL | Development testing — use this |
| SS Live (portal) | Web portal URL | Live tenant-facing — do not interact with live data |
| MyLHP app (live) | App stores (Android/iOS) | Live only — there is no test app |
There is no test MyLHP app. All app development testing must be done via the SS Test web portal. The live app can be used to view results (read-only) but do not submit or interact with live customer data through it.
Testing as a Tenant — Setup¶
Step 1: Find a valid test client¶
Use one of these queries to find a live tenant with an active repair:
-- Tenant with future appointment (best for SS repairs testing)
SELECT TOP 20
o.order_no, o.client_no, o.prty_id, o.targ_comp_dt, a.start_time, t.tency_seq_no
FROM hpmordhd o
INNER JOIN hpmaptmt a ON a.order_no = o.order_no
INNER JOIN hratency t ON t.prty_ref = o.prty_id AND t.comp_id = o.comp_id
WHERE o.ord_status = 'ISS'
AND (t.tency_end_dt IS NULL OR t.tency_end_dt > GETDATE())
ORDER BY a.start_time DESC
Known good test client: 944747 (confirmed working live account as of May 2026)
Avoid void/fake clients. Void clients exist so the system functions while a property is empty — they have no active tenancy. If you set your Person ID to a void client, the portal returns HTTP 500 ("The client_no set on your user is a void client, no active tenancy").
Step 2: Set your Person ID in Management Studio¶
- Management Studio → Users → find your user account
- Update Person ID to the
client_noof your chosen test tenant - Fully log out and back in to the portal to clear session cache
Step 3: Clear app cache if needed¶
After changing Person ID, if the app still shows the old tenant's data: - Android: Settings → Apps → MyLHP → Storage → Clear Cache - The app may flip between two dates/tenants if showing stale cached data — this is session caching, not a data bug
Active Tasks¶
If after changing Person ID you're still seeing the old tenant's data in the portal, check for active tasks: 1. Management Studio → Tasks → Active Tasks 2. Find any tasks belonging to your user account 3. Abandon them — they may be carrying the old tenant context
SS Live Deployment¶
SS Live runs an overnight job — changes deployed to SS Live may not reflect until the next morning. Do not expect immediate results after a Live deployment.
QL Database Names¶
| Environment | Database |
|---|---|
| SS Test | t_qlfdat |
| Dev / Acceptance | a_qlfdat |
| Live | QLFDAT |
When writing SQL to test SS scenarios, connect to t_qlfdat for SS Test environment queries.
Common Issues¶
| Issue | Cause | Fix |
|---|---|---|
| Portal HTTP 500 on login | Person ID set to a void/fake client | Find a live tenant via SQL and update Person ID |
| Still showing old tenant data after Person ID change | Session cache | Force close app + clear app cache (Android: Settings → Apps → MyLHP → Storage → Clear Cache) |
| App flips between two dates/tenants | Stale session data | Force close and clear cache |
| Changes not visible on SS Live | Overnight deployment job hasn't run | Wait until next morning |
| "No appointment date" on portal repair card | Aareon-side rendering — not LHP-controllable | Log with Aareon referencing ApptStartDate DataItem now exposed in workflow |