[No QA] Docs updates for E/A#96351 correct Certinia PSA/SRP install link#96360
[No QA] Docs updates for E/A#96351 correct Certinia PSA/SRP install link#96360MelvinBot wants to merge 1 commit into
Conversation
Co-authored-by: Yuwen Memon <yuwenmemon@users.noreply.github.com>
|
A preview of your ExpensifyHelp changes have been deployed to https://0c393042.helpdot.pages.dev ⚡️ Updated articles: |
HelpDot Documentation ReviewOverall AssessmentThis PR makes a narrow, high-value correction: it fixes the PSA/SRP installer link in both the New Expensify and Expensify Classic Connect-To-Certinia articles. The old links pointed at an incorrect Salesforce package ID (04t2M000002J0BH) and were additionally malformed with double-encoded query-string junk (...J0BHD%252Fpackaging%253FinstallPackage.apexp%253Fp0%253D...). Both are replaced with a single clean, correct URL (p0=04t2M000002J0BM). This is purely a link correction; no prose, headings, metadata, or structure were touched. Scores Summary
Key Findings
Recommendations
Files Reviewed
Note: This PR is a targeted link fix; there were no substantive line-level issues warranting separate inline comments. |
Docs updates for E/A#96351
Explanation of Change
PR #96351 fixed the outdated Certinia PSA/SRP production bundle install link in the app, pointing it at the correct Salesforce package (
04t2M000002J0BM, the same package Expensify Classic's modal uses) and reverting the version copy back to 1.3.The Certinia help articles still pointed at the old, incorrect package ID (
04t2M000002J0BH) — the exact bug that PR fixed — and the URL was additionally malformed with double-encoded query-string junk. This PR corrects the PSA/SRP installer link in both articles to the clean, correct URL:https://login.salesforce.com/packaging/installPackage.apexp?p0=04t2M000002J0BMFiles changed
docs/articles/new-expensify/connections/certinia/Connect-To-Certinia.md— corrected the PSA/SRP installer link.docs/articles/expensify-classic/connections/certinia/Connect-To-Certinia.md— corrected the PSA/SRP installer link.The FFA installer link and the sandbox link were left unchanged (PR #96351 only changed the PSA production package). The docs do not reference the bundle version number in text, so no version copy change was needed there.
@yuwenmemon, please review the files changed and confirm they reflect the current behavior. Then mark this PR
Ready for review.