Skip to content

Fix outdated Certinia PSA bundle production install link#96351

Merged
yuwenmemon merged 1 commit into
mainfrom
yuwen-certinia-psa-production-link-fix
Jul 16, 2026
Merged

Fix outdated Certinia PSA bundle production install link#96351
yuwenmemon merged 1 commit into
mainfrom
yuwen-certinia-psa-production-link-fix

Conversation

@yuwenmemon

Copy link
Copy Markdown
Contributor

Explanation of Change

Follow-up to #96340, which merged before its second commit landed. That PR's initial fix was wrong: it changed the "Version 1.3" copy to "1.2" to match what the production install link happened to download. The actual bug is the other way around - the link was outdated. CERTINIA_PSA_BUNDLE_INSTALL_URL.PRODUCTION pointed at the same Salesforce package ID as SANDBOX (04t2M000002J0BH), which installs an older package than the 1.3 the copy promises, causing a customer's install to fail. This reverts the version text to 1.3 and points the production link at the correct package (04t2M000002J0BM - the same one Expensify Classic's equivalent modal already uses).

Fixed Issues

$
PROPOSAL:

Tests

  1. Upgrade a workspace to the Control plan and open Workspace Settings > Accounting > Certinia > Connect.
  2. On the "Before you connect" step, verify the PSA/SRP bundle link reads "Install PSA/SRP Expensify Bundle (Version 1.3)".
  3. Inspect the link's href and confirm it points to .../installPackage.apexp?p0=04t2M000002J0BM.
  • Verify that no errors appear in the JS console

Offline tests

N/A - copy/link-only change, not network-dependent.

QA Steps

Same as tests.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Not tested - no device/emulator available in this environment. This is a one-line URL fix using a shared constant, so it's not platform-dependent.

Android: mWeb Chrome

Not tested - see above.

iOS: Native

Not tested - see above.

iOS: mWeb Safari

Not tested - see above.

MacOS: Chrome / Safari

Verified in a browser: the "Before you connect" step reads "Install PSA/SRP Expensify Bundle (Version 1.3)" and the link's href points to .../installPackage.apexp?p0=04t2M000002J0BM.

@yuwenmemon
yuwenmemon requested review from a team as code owners July 16, 2026 20:50
@melvin-bot
melvin-bot Bot requested review from JmillsExpensify and chuckdries and removed request for a team July 16, 2026 20:50
@melvin-bot

melvin-bot Bot commented Jul 16, 2026

Copy link
Copy Markdown

@chuckdries Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b15daa5b24

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/CONST/index.ts
},

CERTINIA_PSA_BUNDLE_VERSION: '1.2',
CERTINIA_PSA_BUNDLE_VERSION: '1.3',

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align sandbox package URL with displayed version

When the Certinia connection is opened in sandbox mode, CertiniaPrerequisitesStep still uses CERTINIA_PSA_BUNDLE_INSTALL_URL.SANDBOX while rendering this shared version constant. Since the sandbox URL remains 04t2M000002J0BH and this change's rationale says that package installs an older bundle than 1.3, sandbox users now see “Version 1.3” but are sent to the old package, reproducing the same misleading/install-failure path for isSandbox=true. Please either update the sandbox package ID to the 1.3 package as well or split the displayed version by environment.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems valid but I'm not sure if it's important

@yuwenmemon
yuwenmemon merged commit 01ca161 into main Jul 16, 2026
45 of 46 checks passed
@yuwenmemon
yuwenmemon deleted the yuwen-certinia-psa-production-link-fix branch July 16, 2026 22:15
@github-actions

Copy link
Copy Markdown
Contributor

🚧 yuwenmemon has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.4.36-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review — changes required, draft PR opened.

This PR corrected the Certinia PSA/SRP production install link in the app to package 04t2M000002J0BM and reverted the version copy to 1.3. The Certinia help articles still pointed at the old, incorrect package (04t2M000002J0BH) — the exact bug this PR fixed — and the link was additionally malformed with double-encoded query-string junk.

I opened a draft PR to correct the PSA/SRP installer link in both affected articles:

#96360 — Docs updates for E/A#96351 correct Certinia PSA/SRP install link

What changed
  • docs/articles/new-expensify/connections/certinia/Connect-To-Certinia.md — corrected PSA/SRP installer link
  • docs/articles/expensify-classic/connections/certinia/Connect-To-Certinia.md — corrected PSA/SRP installer link

Both now point at https://login.salesforce.com/packaging/installPackage.apexp?p0=04t2M000002J0BM.

The FFA and sandbox links were left unchanged (this PR only changed the PSA production package). The docs don't reference the bundle version number in text, so no version-copy change was needed there.

@yuwenmemon, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@kavimuru

Copy link
Copy Markdown

@yuwenmemon please help with the following steps:

On the "Before you connect" step, verify the PSA/SRP bundle link reads "Install PSA/SRP Expensify Bundle (Version 1.3)".
Inspect the link's href and confirm it points to .../installPackage.apexp?p0=04t2M000002J0BM.

@yuwenmemon

Copy link
Copy Markdown
Contributor Author

What's the issue exactly? You can find this under Workspace Settings > Accounting > Certinia > Connect as described in the first step

@kavimuru

Copy link
Copy Markdown

@yuwenmemon Sorry I misunderstood the steps. No issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants