Skip to content

@szymczak/sage intacct import page#44166

Merged
yuwenmemon merged 43 commits into
Expensify:mainfrom
software-mansion-labs:@szymczak/sage-intacct-import-page
Jul 9, 2024
Merged

@szymczak/sage intacct import page#44166
yuwenmemon merged 43 commits into
Expensify:mainfrom
software-mansion-labs:@szymczak/sage-intacct-import-page

Conversation

@SzymczakJ

@SzymczakJ SzymczakJ commented Jun 21, 2024

Copy link
Copy Markdown
Contributor

Details

Fixed Issues

$ #43533
PROPOSAL:

Tests

  1. With account connected to Sage Intacct.
  2. Go to Import page and make sure Import page looks like this(mobile and web):
Screenshot 2024-07-02 at 17 25 59 Screenshot 2024-07-02 at 17 26 10
  1. Try switching on and off "Billable" toggle and "Tax" toggle.
  2. Go to Departments subpage and make sure it looks like this:
Screenshot 2024-07-02 at 17 28 56 5. Go to "Displayed as" and make sure it looks like this: Screenshot 2024-07-02 at 17 36 01
  1. Switch to "Tags" or "Report Field" and make sure Import and Departments pages get updated:
Screenshot 2024-07-02 at 17 42 03 Screenshot 2024-07-02 at 17 42 24
  1. Turn off Import toggle on Departments page and make sure it page looks like this
Screenshot 2024-07-02 at 17 30 48

and Import page looks like this (Departments Menu Item changed to "Departments")
Screenshot 2024-07-02 at 17 32 41

  1. Go to User-defined dimensions page and make sure it looks like this, when it's empty:
Screenshot 2024-07-02 at 17 44 53
  1. Go to Add user-defined dimension page and make sure it looks like this:
Screenshot 2024-07-02 at 17 45 40
  1. Make sure "Itegration name" and "Displayed as" entry fields are required
Screenshot 2024-07-02 at 17 46 39
  1. Try add int user-defined dimension and make sure it gets added to User-defined dimensions page:
Screenshot 2024-07-02 at 17 47 51 12. Make sure editing the created user dimension looks like this: Screenshot 2024-07-03 at 16 12 21
  1. Make sure editing and removing User defined dimension works.
  2. Turn on Simulate failing network request and make sure error states look like this(screenshot presents situation when everything that could fail failed):
Screenshot 2024-07-02 at 18 02 02 Screenshot 2024-07-02 at 18 05 16 Screenshot 2024-07-02 at 18 06 01
  1. Turn on Offline mode and make sure offline states look like this
Screenshot 2024-07-02 at 18 11 43 Screenshot 2024-07-02 at 18 11 06 Screenshot 2024-07-02 at 18 12 03

Offline tests

QA Steps

  • 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
    • MacOS: Desktop
  • 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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
android.mov
Android: mWeb Chrome
androidweb.mov
iOS: Native
ios.mov
iOS: mWeb Safari
iosweb.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

intacct: {
config: {
mappings: {
[mappingName]: mappingValue,

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.

Should we set mappings to some values on success? 🤔 I think it should be handled by the data returned from the backend

Comment thread src/components/SelectionList/BaseSelectionList.tsx Outdated
Comment thread src/languages/en.ts Outdated
Comment thread src/languages/en.ts Outdated
Comment thread src/pages/workspace/accounting/intacct/import/SageIntacctAddUserDimensionPage.tsx Outdated
Comment thread src/pages/workspace/accounting/intacct/import/SageIntacctImportPage.tsx Outdated
Comment thread src/types/onyx/Policy.ts
@melvin-bot

melvin-bot Bot commented Jul 2, 2024

Copy link
Copy Markdown

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@SzymczakJ SzymczakJ marked this pull request as ready for review July 2, 2024 16:16
@SzymczakJ SzymczakJ requested review from a team as code owners July 2, 2024 16:16
@melvin-bot melvin-bot Bot requested review from hungvu193 and removed request for a team July 2, 2024 16:16

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.

cc @mananjadhav I believe this is the same as the file here if you want to consolidate around this name: https://expensify.slack.com/archives/C06ML6X0W9L/p1719967769151569?thread_ts=1719965572.991699&cid=C06ML6X0W9L

(I feel like folder-with-papers is a more descriptive and appropriate file name)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I'll update the name.

Comment thread src/CONST.ts Outdated
Comment thread src/ONYXKEYS.ts Outdated
Comment thread src/languages/en.ts Outdated
Comment thread src/languages/en.ts Outdated
Comment thread src/languages/en.ts Outdated
Comment thread src/languages/es.ts Outdated
Comment thread src/libs/API/parameters/UpdateSageIntacctImportBooleanValues.ts Outdated
function addSageIntacctUserDimensions(
policyID: string,
name: string,
mapping: typeof CONST.SAGE_INTACCT_CONFIG.MAPPING_VALUE.TAG | typeof CONST.SAGE_INTACCT_CONFIG.MAPPING_VALUE.REPORT_FIELD,

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.

return {optimisticData, failureData, successData};
}

function addSageIntacctUserDimensions(

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.

cc @NikkiWines on this function to make sure your API lines up with what's being sent here and below, or if @SzymczakJ needs to tweak things.

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.

Sounds like you guys have this one sorted based on this discussion

Comment thread src/types/form/SageIntacctDimensionsForm.ts Outdated
Comment thread src/types/form/index.ts
@yuwenmemon

Copy link
Copy Markdown
Contributor

@SzymczakJ Some more conflicts :(

yuwenmemon
yuwenmemon previously approved these changes Jul 9, 2024

@yuwenmemon yuwenmemon left a comment

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.

Looking good!

Comment thread src/pages/workspace/accounting/intacct/IntacctPrerequisitesPage.tsx Outdated
Comment thread src/pages/workspace/accounting/intacct/import/SageIntacctImportPage.tsx Outdated
Comment thread src/pages/workspace/accounting/intacct/import/SageIntacctToggleMappingsPage.tsx Outdated
@yuwenmemon yuwenmemon merged commit 932e657 into Expensify:main Jul 9, 2024
@OSBotify

OSBotify commented Jul 9, 2024

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

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

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 failure ❌
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 9.0.6-1 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 failure ❌
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 9.0.6-1 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.7-8 🚀

platform result
🤖 android 🤖 failure ❌
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅

Comment thread src/languages/en.ts
addAUserDefinedDimension: 'Add a user-defined dimension',
detailedInstructionsLink: 'View detailed instructions',
detailedInstructionsRestOfSentence: ' on adding user-defined dimensions.',
userDimensionsAdded: (dimensionsCount: number) => `${dimensionsCount} ${Str.pluralize('UDD', `UDDs`, dimensionsCount)} added`,

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.

Just stumbled into this. UDD is a user facing term?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I believe so. Here's screenshot from Figma:
Screenshot 2024-09-27 at 15 37 41

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.

Ah ok, thanks! Seemed weird

@SzymczakJ SzymczakJ deleted the @szymczak/sage-intacct-import-page branch April 8, 2025 09:10
Comment on lines +76 to +77
title={translate('workspace.intacct.expenseTypes')}
subtitle={translate('workspace.intacct.expenseTypesDescription')}

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.

Case was missed where import type should be dynamic based on export type: #59670

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.