Add paymentTerms field when creating a cost center.

[rayssamfreitas]

What problem is this solving?

Adjusts to send the paymentTerms field when creating an organization.

How to test it?

You can test by creating an organization and also passing a paymentTerms.

Workspace

Screenshots or example usage:

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[github-actions]

	Messages
📖	❤️ Thanks!
📖	🎉 PR additions = 7, PR deletions = 0

Generated by 🚫 dangerJS against 9349f10

[Rudge]

Fails
🚫

We follow keepachangelog standards.

Please, change the file CHANGELOG.md adding a small summary of your changes under the [Unreleased] section. Example:

 ## [Unreleased]

+ ### Fixed
+ - Issue with image sizing in the SKU Selector.

Possible types of changes:

* `Added` for new features.

* `Changed` for changes in existing functionality.

* `Deprecated` for soon-to-be removed features.

* `Removed` for now removed features.

* `Fixed` for any bug fixes.

* `Security` in case of vulnerabilities.

Warnings
⚠️

package.json was changed, but not yarn.lock (vice-versa) [:bulb: are you sure this is right?]
Messages
📖 ❤️ Thanks!
📖

🎉 PR additions = 5, PR deletions = 2

Generated by 🚫 dangerJS against 28d5ad6

@rayssamfreitas Could you update the changelog, please?

[rayssamfreitas]

@Rudge , updated!

[enzomerca]

LGTM. We are going to merge/deploy it soon.

[enzomerca]

Upon further review, we believe this PR would cause the incorrect usage of a feature.

There is a feature that allows the Buyer Org Admin to enable/disable payment terms for a given cost center through the "My Account" section on the storefront. The cost center payment terms field, that can be updated through the updateCostCenter, should be used exclusively for that.
The misuse of this feature could cause unexpected behaviour when adding new payment terms to an existing buyer org through the Admin UI.

Could you please explain your use case so we can evaluate if this change makes sense or if there is an alternative way to achieve your needs?

[enzomerca]

Discussed offline, but it actually makes sense to add this parameter to the createCostCenter APIs.
The PR description/changelog info was saying organization but this change does not affect the createOrganization API.
I updated the PR description and changelog and I'm going to merge/deploy this change.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 0.52.0 → 0.53.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖