Crops Farm — SaaS Tier Limits
Optional bridge addon (task CF-SA-1) connecting grev_od_crops_farm to the SaaS entitlement foundation grev_od_saas_base_ent. Mirrors grev_od_livestock_farm_saas's own LF-SA-1 shape exactly.
Why a separate addon
grev_od_crops_farm must stay installable and fully functional with no SaaS module present at all (user directive, 2026-08-01, and X-17's own bridge-addon rule). So the farm module itself carries no SaaS dependency and no SaaS code; everything lives here, reaching into the farm models via _inherit.
Provides
- Three tenant entitlement axes registered as grev.saas.usage.counter rows -- cf_crop_type_count, cf_plot_count, cf_location_count -- each backed by a counting method added to grev.saas.tenant via _inherit.
- create() overrides on grev.crop.farm.crop.type / .plot / .location that call tenant._grev_check_limit(code) before the records exist, so exceeding a tier ceiling is refused with a message naming the plan, the axis and the ceiling. .plot resolves its own tenant company through location_id (its own company_id is a related field, not directly writable).
CF-WF-3's own seeded crop-type workflow library (data/ crop_type_data.xml, company_id = False) are template rows, not tenant usage, and are exempt from the crop-type ceiling.
Enforcement is a no-op unless the grev_saas.saas_mode system parameter is on -- installing this addon on a non-SaaS database changes nothing.
Requires Odoo Enterprise transitively (via grev_od_saas_base_ent -> sale_subscription).
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Discuss (mail) • Employees (hr) • Fleet (fleet) • Inventory (stock) • Invoicing (account) • Project (project) • Purchase (purchase) • Calendar (calendar) • Contacts (contacts) • Subscriptions (sale_subscription) • Sales (sale_management) |
| Community Apps Dependencies | Show |
| Lines of code | 15626 |
| Technical Name |
grev_od_crops_farm_saas |
| License | OPL-1 |
| Website | https://grevlin.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module