[18.0][IMP] spreadsheet_oca: server-side pivot refresh, alerts, scenarios, writeback, subscriptions#98
[18.0][IMP] spreadsheet_oca: server-side pivot refresh, alerts, scenarios, writeback, subscriptions#98
Conversation
7552d40 to
bcc169b
Compare
|
Don, thanks for the improvements, but having all the changes in only big PR is unmanageable, for not saying all the AI related thing, that is still under discussion in OCA workgroup (attribution, copyright, etc). Please split at least each improvement in one PR. |
bcc169b to
bcfc627
Compare
thanks (AI) yeah I brought it up in a few groups but did not see any specific guidance. I had these all nicely split up in 5 feature commits and then got lost on the fixes squashing them to the right ones. will give it a go though! Are you suggesting 5 PRs and then linking the test decencies to those related? the server side export might be the only one needed on the subscriptions. |
bcfc627 to
2c38d82
Compare
…port, scenarios, writeback, subscriptions, and input parameters New features for the OCA spreadsheet module: - Scheduled data refresh with cron-based pivot re-computation and Chatter notifications (with input parameter substitution) - KPI alerts with configurable cell watches, threshold conditions, edge/level trigger modes, and partner notifications - What-if scenarios with cell overrides, base-case comparison, and export to new spreadsheet copies - Cell writeback allowing direct Odoo record edits from list-view cells with full audit logging and rollback capability - Email subscriptions for periodic digest emails (daily/weekly/monthly) with optional pivot data summaries - Input parameters for named cell references with automatic domain substitution during refresh cycles - XLSX export with dedicated pivot sheets and styled headers - QWeb email templates for alerts, digests, and refresh notifications (customisable via Settings > Technical > Views) - Demo data with pivot dashboard, KPI alerts, and guided feature tour - Record rules tying child model visibility to parent spreadsheet access Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2c38d82 to
6082310
Compare
|
Yes, splitting by feature, each PR can follow a specific path, being merged if clear, and discussed if not, but not having to approve or refuse everything in batch. |
|
oh just a note too. while I intend to use and verify everything on my internal instances. I have not yet done that. likely will come up with fixes/improvements in the process. Will work on splitting up the features into new PRs next. My goal is a reporting platform that supports investigation and addition of adhoc values in the planning process. |
|
@pedrobaeza Thanks for the guidance. I've started splitting — first feature PR is up at #99 (pivot engine + scheduled refresh). The structure is:
Each subsequent feature PR will rebase on commit 1 and add its own feature commit. This makes them independently reviewable and mergeable. I'll close this PR once all the split PRs are up. Let me know if the structure of #99 looks right before I continue with the rest. |
Summary
Adds server-side operational features to the OCA spreadsheet module:
%(token)sdomain substitution during refresh/alert cycles.xlsxdownload with dedicated pivot sheets and styled headersxpathinheritance)Also includes:
Technical details
_()calls use Odoo 18 named-keyword stylemarkupsafe.Markupused for safe HTML injection into QWeb templatescheck_access_rights/check_access_rulein controllers,sudo()only where justifiedTest plan
#ERRORpython -m pytest— all 148 tests pass🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com