[16.0][MIG] pos_environment

[legalsylvain]

quite simple migration of pos_environment introduced here #27 in V12.

Description

This module extends the Odoo point of sale module to allow administrator to customize the bill printed by the point of sale, with a text depending on your environment. (Development, , Pre Production, Production, etc...)

The displayed and printed bill will display the custom message

This module is based on the mechanism introduced by the server_environment module.

Note

This module provides a feature that is legally required in some countries (such as France, under the law on accounting certification) where test receipts must be distinguishable.

Configure

• Open your module server_environment_files

• In each environment folder, create a new file named ``pos_environment.conf (for exemple)

• In each file, write a section like this one, depending on your environment

  [pos_environment_header]
  line_1 = ===============================
  line_2 = TICKET EDITED ON A TEST
  line_3 = ENVIRONMENT
  line_4 = ===============================

  [pos_environment_footer]
  line_1 = ===============================
  line_2 = THIS TICKET HAS BEEN EDITED
  line_3 = ON A TEST ENVIRONMENT
  line_4 = -------------------------------
  line_5 = IT CAN NOT BE CONSIDERED
  line_6 = AS A PROOF OF PURCHASE
  line_7 = ===============================

Internationalisation

If you deploy Odoo in a multi languages context, you can add a suffix __xx_xx in the name of each line, where xx_xx is the language.
The text will be displayed on the bill, depending of the language of the current user. Sample :

  line_1 = ===============================
  line_2__en_US = TICKET EDITED ON A TEST SERVER
  line_2__fr_FR = TICKET EDITE SUR SERVEUR DE TEST
  line_3 = -------------------------------

Note

To be sure that your server is correctly configured, you can check the settings
in the Point of Sale configuration.

[legalsylvain]

/ocabot migration pos_environment

[OCA-git-bot]

Sorry @legalsylvain you are not allowed to mark the addon tobe migrated.

To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons.

If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the maintainers key of its manifest.

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[legalsylvain]

/ocabot migration pos_environment

[legalsylvain]

/ocabot rebase

[OCA-git-bot]

Congratulations, PR rebased to 16.0.

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[legalsylvain]

/ocabot rebase

[OCA-git-bot]

Congratulations, PR rebased to 16.0.

[legalsylvain]

/ocabot merge nobump

[OCA-git-bot]

What a great day to merge this nice PR. Let's do it!
Prepared branch 16.0-ocabot-merge-pr-156-by-legalsylvain-bump-nobump, awaiting test results.

[OCA-git-bot]

Congratulations, your PR was merged at bdc10d2. Thanks a lot for contributing to OCA. ❤️