Chatter Tools: Search, Pin & Bulk Messages

Chatter Tools: Search, Pin & Bulk Messages. Search every chatter at once, pin what matters, post a template onto hundreds of records, resend failed notifications and purge dead rows. Said before you buy, because it is the half that decides whether the app fits: In the next few minutes: chatter tools: search, pin & bulk messages, then search every chatter at once, then templates, then pinning, then resending what failed. Then what this app deliberately does not do, so you can tell before you buy whether it fits.

Everything lives under Failed Notifications then Search the Chatter then Templates then Cleanup Rules. 1. Copy bambooforge_chatter_tools into your addons path and update the app list, or install the ZIP from the Odoo Apps Store. 2.

Install Chatter Tools: Search, Pin & Bulk Messages. 3. Open Failed Notifications - its menus are Search the Chatter, Templates, Cleanup Rules. Chatter Tools: Search, Pin & Bulk Messages.

The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs. Search every chatter at once. Settings › Chatter Tools › Search the Chatter.

Every message on every record: by text, by author, by model, by type, by month, grouped however you like. The chatter itself can only be read one record at a time, which is no use at all when somebody asks "who told the customer that, and when?". Two filters do most of the work. Typed by a person keeps comment and email — what somebody wrote and what arrived — and gets the twenty million system rows out of the way.

Written by the system does the opposite, and is how you look at what a cleanup rule is about to throw away before you let it. Templates. The paragraph somebody types forty times a week — "rang them about the delay", "credit checked, on hold" — written once. Placeholders are the ones a mail template uses.

{{ object.name }} works in the rich-text box, because QWeb interpolates {{ }} in attributes but never in a text node — which is why a mail template writes {{ }} in the subject and <t t-out=""/> in the body — and the template is converted before rendering, exactly the way core converts it for its own preview. A t-out written by hand keeps working. Pinning. One message on a record that the next person has to read before they do anything.

One click in the message's hover menu; the pin records who did it and when, and pinned messages are never deleted by a cleanup rule. Odoo 20's chatter does not take extra actions in that menu, so pinning there is done from Search the Chatter instead. Everything else in this module is the same on 16.0 through 19.0; the 20.0 build differs only where Odoo 20 moved what it hangs off. Resending what failed.

A notification in exception is invisible: the record says the customer was told, and the customer was not. Settings › Chatter Tools › Failed Notifications lists them with the reason and the date, and puts the ones you tick back in the queue. A notification on a record you may not write to is left alone whatever is ticked, and the wizard says how many it skipped. Sending somebody's mail again is writing on their record.

Throwing the rest away. Every stage change and every tracked field writes a mail_message row. Nobody reads the ones from 2019 and everybody pays for them in backup time, in restore time and in the index. Notifications only — stage moves, tracking, "created by"; Everything the system wrote — the above plus automated comments and user notifications; Empty — a notification with no body and no file, which is the most common row of all.

A cleanup rule says: on this model, messages of this kind, older than this many months. The kinds are Who can do what. Every internal user is a Chatter Tools user: posts from a template, pins a message, sends a failed notification again — always on records they may already write to. A manager writes the templates everybody uses and the cleanup rules that throw chatter away.

What it needs. mail only. Community. No Enterprise module is required, and none is used.

How we make sure it works. Before every release, 65 automated checks run against this app on Odoo 16, 17, 18, 19 and 20. Among them: A note an email actually went out from is never deleted. A portal customer never sees a pinned internal note.

A template that is not offered cannot be posted. Records the caller cannot read are dropped. A broken placeholder shows in the preview not the chatter. The complete list is in the source you receive.

Questions people ask. Which Odoo versions does it run on? Odoo 16.0, 17.0, 18.0, 19.0, 20.0, on the series you buy it for; each series is its own listing. Community or Enterprise?

Both. It needs no Enterprise app. The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Chatter Tools: Search, Pin & Bulk Messages. Search every chatter at once, pin what matters, post a template onto hundreds of records, resend failed notifications and purge dead rows. The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs.

In the next few minutes: chatter tools: search, pin & bulk messages, then search every chatter at once, then templates, then pinning, then resending what failed. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Failed Notifications then Search the Chatter then Templates then Cleanup Rules. Chatter Tools: Search, Pin & Bulk Messages.

The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs. Search every chatter at once. Settings › Chatter Tools › Search the Chatter.

Every message on every record: by text, by author, by model, by type, by month, grouped however you like. The chatter itself can only be read one record at a time, which is no use at all when somebody asks "who told the customer that, and when?". Two filters do most of the work. Typed by a person keeps comment and email — what somebody wrote and what arrived — and gets the twenty million system rows out of the way.

Written by the system does the opposite, and is how you look at what a cleanup rule is about to throw away before you let it. Templates. The paragraph somebody types forty times a week — "rang them about the delay", "credit checked, on hold" — written once. Placeholders are the ones a mail template uses.

{{ object.name }} works in the rich-text box, because QWeb interpolates {{ }} in attributes but never in a text node — which is why a mail template writes {{ }} in the subject and <t t-out=""/> in the body — and the template is converted before rendering, exactly the way core converts it for its own preview. A t-out written by hand keeps working. Pinning. One message on a record that the next person has to read before they do anything.

One click in the message's hover menu; the pin records who did it and when, and pinned messages are never deleted by a cleanup rule. Odoo 19's chatter does not take extra actions in that menu, so pinning there is done from Search the Chatter instead. Everything else in this module is identical on all four series. Resending what failed.

A notification in exception is invisible: the record says the customer was told, and the customer was not. Settings › Chatter Tools › Failed Notifications lists them with the reason and the date, and puts the ones you tick back in the queue. A notification on a record you may not write to is left alone whatever is ticked, and the wizard says how many it skipped. Sending somebody's mail again is writing on their record.

Throwing the rest away. Every stage change and every tracked field writes a mail_message row. Nobody reads the ones from 2019 and everybody pays for them in backup time, in restore time and in the index. Notifications only — stage moves, tracking, "created by"; Everything the system wrote — the above plus automated comments and user notifications; Empty — a notification with no body and no file, which is the most common row of all.

A cleanup rule says: on this model, messages of this kind, older than this many months. The kinds are Who can do what. Every internal user is a Chatter Tools user: posts from a template, pins a message, sends a failed notification again — always on records they may already write to. A manager writes the templates everybody uses and the cleanup rules that throw chatter away.

What it needs. mail only. Community. No Enterprise module is required, and none is used.

The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Chatter Tools: Search, Pin & Bulk Messages. Search every chatter at once, pin what matters, post a template onto hundreds of records, resend failed notifications and purge dead rows. The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs.

In the next few minutes: chatter tools: search, pin & bulk messages, then search every chatter at once, then templates, then pinning, then resending what failed. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Failed Notifications then Search the Chatter then Templates then Cleanup Rules. Chatter Tools: Search, Pin & Bulk Messages.

The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs. Search every chatter at once. Settings › Chatter Tools › Search the Chatter.

Every message on every record: by text, by author, by model, by type, by month, grouped however you like. The chatter itself can only be read one record at a time, which is no use at all when somebody asks "who told the customer that, and when?". Two filters do most of the work. Typed by a person keeps comment and email — what somebody wrote and what arrived — and gets the twenty million system rows out of the way.

Written by the system does the opposite, and is how you look at what a cleanup rule is about to throw away before you let it. Templates. The paragraph somebody types forty times a week — "rang them about the delay", "credit checked, on hold" — written once. Placeholders are the ones a mail template uses.

{{ object.name }} works in the rich-text box, because QWeb interpolates {{ }} in attributes but never in a text node — which is why a mail template writes {{ }} in the subject and <t t-out=""/> in the body — and the template is converted before rendering, exactly the way core converts it for its own preview. A t-out written by hand keeps working. Pinning. One message on a record that the next person has to read before they do anything.

One click in the message's hover menu; the pin records who did it and when, and pinned messages are never deleted by a cleanup rule. Odoo 18's chatter does not take extra actions in that menu, so pinning there is done from Search the Chatter instead. Everything else in this module is identical on all four series. Resending what failed.

A notification in exception is invisible: the record says the customer was told, and the customer was not. Settings › Chatter Tools › Failed Notifications lists them with the reason and the date, and puts the ones you tick back in the queue. A notification on a record you may not write to is left alone whatever is ticked, and the wizard says how many it skipped. Sending somebody's mail again is writing on their record.

Throwing the rest away. Every stage change and every tracked field writes a mail_message row. Nobody reads the ones from 2019 and everybody pays for them in backup time, in restore time and in the index. Notifications only — stage moves, tracking, "created by"; Everything the system wrote — the above plus automated comments and user notifications; Empty — a notification with no body and no file, which is the most common row of all.

A cleanup rule says: on this model, messages of this kind, older than this many months. The kinds are Who can do what. Every internal user is a Chatter Tools user: posts from a template, pins a message, sends a failed notification again — always on records they may already write to. A manager writes the templates everybody uses and the cleanup rules that throw chatter away.

What it needs. mail only. Community. No Enterprise module is required, and none is used.

The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Chatter Tools: Search, Pin & Bulk Messages. Search every chatter at once, pin what matters, post a template onto hundreds of records, resend failed notifications and purge dead rows. The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs.

In the next few minutes: chatter tools: search, pin & bulk messages, then search every chatter at once, then templates, then pinning, then resending what failed. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Failed Notifications then Search the Chatter then Templates then Cleanup Rules. Chatter Tools: Search, Pin & Bulk Messages.

The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs. Search every chatter at once. Settings › Chatter Tools › Search the Chatter.

Every message on every record: by text, by author, by model, by type, by month, grouped however you like. The chatter itself can only be read one record at a time, which is no use at all when somebody asks "who told the customer that, and when?". Two filters do most of the work. Typed by a person keeps comment and email — what somebody wrote and what arrived — and gets the twenty million system rows out of the way.

Written by the system does the opposite, and is how you look at what a cleanup rule is about to throw away before you let it. Templates. The paragraph somebody types forty times a week — "rang them about the delay", "credit checked, on hold" — written once. Placeholders are the ones a mail template uses.

{{ object.name }} works in the rich-text box, because QWeb interpolates {{ }} in attributes but never in a text node — which is why a mail template writes {{ }} in the subject and <t t-out=""/> in the body — and the template is converted before rendering, exactly the way core converts it for its own preview. A t-out written by hand keeps working. Pinning. One message on a record that the next person has to read before they do anything.

One click in the message's hover menu; the pin records who did it and when, and pinned messages are never deleted by a cleanup rule. Odoo 16's chatter does not take extra actions in that menu, so pinning there is done from Search the Chatter instead. Everything else in this module is identical on all four series. Resending what failed.

A notification in exception is invisible: the record says the customer was told, and the customer was not. Settings › Chatter Tools › Failed Notifications lists them with the reason and the date, and puts the ones you tick back in the queue. A notification on a record you may not write to is left alone whatever is ticked, and the wizard says how many it skipped. Sending somebody's mail again is writing on their record.

Throwing the rest away. Every stage change and every tracked field writes a mail_message row. Nobody reads the ones from 2019 and everybody pays for them in backup time, in restore time and in the index. Notifications only — stage moves, tracking, "created by"; Everything the system wrote — the above plus automated comments and user notifications; Empty — a notification with no body and no file, which is the most common row of all.

A cleanup rule says: on this model, messages of this kind, older than this many months. The kinds are Who can do what. Every internal user is a Chatter Tools user: posts from a template, pins a message, sends a failed notification again — always on records they may already write to. A manager writes the templates everybody uses and the cleanup rules that throw chatter away.

What it needs. mail only. Community. No Enterprise module is required, and none is used.

The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Chatter Tools: Search, Pin & Bulk Messages. Search every chatter at once, pin what matters, post a template onto hundreds of records, resend failed notifications and purge dead rows. The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs.

In the next few minutes: chatter tools: search, pin & bulk messages, then search every chatter at once, then templates, then pinning, then resending what failed. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Failed Notifications then Search the Chatter then Templates then Cleanup Rules. Chatter Tools: Search, Pin & Bulk Messages.

The chatter is Odoo's best idea and its least maintained screen. Five things it cannot do, and every desk needs. Search every chatter at once. Settings › Chatter Tools › Search the Chatter.

Every message on every record: by text, by author, by model, by type, by month, grouped however you like. The chatter itself can only be read one record at a time, which is no use at all when somebody asks "who told the customer that, and when?". Two filters do most of the work. Typed by a person keeps comment and email — what somebody wrote and what arrived — and gets the twenty million system rows out of the way.

Written by the system does the opposite, and is how you look at what a cleanup rule is about to throw away before you let it. Templates. The paragraph somebody types forty times a week — "rang them about the delay", "credit checked, on hold" — written once. Placeholders are the ones a mail template uses.

{{ object.name }} works in the rich-text box, because QWeb interpolates {{ }} in attributes but never in a text node — which is why a mail template writes {{ }} in the subject and <t t-out=""/> in the body — and the template is converted before rendering, exactly the way core converts it for its own preview. A t-out written by hand keeps working. Pinning. One message on a record that the next person has to read before they do anything.

One click in the message's hover menu; the pin records who did it and when, and pinned messages are never deleted by a cleanup rule. Odoo 16's chatter does not take extra actions in that menu, so pinning there is done from Search the Chatter instead. Everything else in this module is identical on all four series. Resending what failed.

A notification in exception is invisible: the record says the customer was told, and the customer was not. Settings › Chatter Tools › Failed Notifications lists them with the reason and the date, and puts the ones you tick back in the queue. A notification on a record you may not write to is left alone whatever is ticked, and the wizard says how many it skipped. Sending somebody's mail again is writing on their record.

Throwing the rest away. Every stage change and every tracked field writes a mail_message row. Nobody reads the ones from 2019 and everybody pays for them in backup time, in restore time and in the index. Notifications only — stage moves, tracking, "created by"; Everything the system wrote — the above plus automated comments and user notifications; Empty — a notification with no body and no file, which is the most common row of all.

A cleanup rule says: on this model, messages of this kind, older than this many months. The kinds are Who can do what. Every internal user is a Chatter Tools user: posts from a template, pins a message, sends a failed notification again — always on records they may already write to. A manager writes the templates everybody uses and the cleanup rules that throw chatter away.

What it needs. mail only. Community. No Enterprise module is required, and none is used.

The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.