Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[14.0][REF+IMP] l10n_br_account_payment_order, l10n_br_account_payment_brcobranca: Adaptando o código para atender o Santander 240 e 400 #2925

Merged

Commits on Feb 28, 2024

  1. [IMP] l10n_br_account_payment_order: Allow inform Comments or Observa…

    …tions in the CNAB Return Move Code.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    1524e6d View commit details
    Browse the repository at this point in the history
  2. [IMP+REF] l10n_br_account_payment_order: Included Comments in Instruc…

    …tions and Return Move Codes for Santander Bank CNAB 400 and 240, changed the file for using four spaces as the standard for XML files.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    5c92b98 View commit details
    Browse the repository at this point in the history
  3. [REF] l10n_br_account_payment_order: Moved validation of length of th…

    …e codes from abstract model to specific ones to allow using this model for other cases.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    fb9e877 View commit details
    Browse the repository at this point in the history
  4. [FIX+IMP] l10n_br_account_payment_order: In Santander case there is n…

    …o 'Wallet to print in Boleto' in this case for both 240 and 400 there is a Wallet Code, and also for Bradesco 240, for now there this three cases mapped, by this reason the better form to solve seems to be the creation of a new object Boleto Wallet Code that allow attend this cases and, if exist, others.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    5410134 View commit details
    Browse the repository at this point in the history
  5. [FIX] l10n_br_account_payment_brcobranca: In Santander case there is …

    …no 'Wallet to print in Boleto' in this case for both 240 and 400 there is a Wallet Code, and also for Bradesco 240, for now there this three cases mapped, by this reason the better form to solve seems to be the creation of a new object Boleto Wallet Code that allow attend this cases and, if exist, others.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    0190b4d View commit details
    Browse the repository at this point in the history
  6. [REF] l10n_br_account_payment_brcobranca: Santander 400 case in BRCob…

    …ranca need to send 'Nosso Numero + DV', the solution is a different approuch of what was made in v12 because it's seems specific case, Santander 240 don't need, by this reason the calculation are made only for this case during the creation of File.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    9bdc0d6 View commit details
    Browse the repository at this point in the history
  7. [REF] l10n_br_account_payment_order: Rename fields code_covention to …

    …cnab_company_bank_code and code_convenio_lider to convention_code in order to avoid duplication of Fields because CNAB has no standards for the Name of the Fields.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    fdb18a1 View commit details
    Browse the repository at this point in the history
  8. [REF+IMP] l10n_br_account_payment_brcobranca: Rename fields code_cove…

    …ntion to cnab_company_bank_code and code_convenio_lider to convention_code in order to avoid duplication of Fields because CNAB has no standards for the Name of the Fields, changed the method to generate CNAB file to avoid duplicate methods when the case 240 is similar with 400 and update the module to use the case of Santander 240.
    mbcosta committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    05a9bee View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    f9608ba View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    36d9e5e View commit details
    Browse the repository at this point in the history
  11. Configuration menu
    Copy the full SHA
    535060d View commit details
    Browse the repository at this point in the history
  12. Configuration menu
    Copy the full SHA
    8c01913 View commit details
    Browse the repository at this point in the history
  13. Configuration menu
    Copy the full SHA
    4e4ffc5 View commit details
    Browse the repository at this point in the history