[18.0][MIG] mail_activity_portal: Migration to v18.0 (#228)

* [18.0][MIG] mail_activity_portal: Migration to v18.0

* Update website and author information in manifest

* [REM] Removed mail_activity_team and mail_activity_board modules from branch

* Update README with testing instructions

Added testing instructions for portal activity scheduling.

---------

Co-authored-by: jans23 <[email protected]>

Author: hitesh-erpharbor

mail_activity_portal/README.rst

@@ -0,0 +1,41 @@
+====================
+Mail Activity Portal
+====================
+This module adds an activity board with form, tree, kanban, calendar, pivot, graph and search views.
+
+
+Usage
+=====
+If a messages arrives over the portal an activity for a configured team is scheduled automatically to process the message.
+
+The configuration to add RMA and PO models (Settings --> Technical --> Activity Teams menu)
+
+
+Testing
+=======
+
+Step 1:
+
+1. Go to: "Settings" -> "Users & Companies" -> "Users" -> "+New" button
+2. In the "Access Rights" tab, set the "User types" to "Portal"
+3. Fill out all other necessary details to create a new testing account
+
+Step 2:
+
+1. Go to: "Settings" -> "Technical" -> "Activities" -> "Activity Teams" -> "+New"
+2. Add the "admin account" in the "Members" section
+3. Set the "Used models" at least to "Sales Order" (or any other portal-accessible models)
+4. Fill out all other necessary details
+
+Step 3:
+
+In this case we are gonna use "Sales Order" as an example.
+
+1. Open a browser window in incognito mode
+2. Log into the testing account
+3. Purchase an item in the online shop
+
+Step 4:
+
+1. Go back into the admin account and navigate to the "Sales Order" that was made with the testing account.
+2. In the chatter panel on the right there should be an automatically generated activity under "Planned Activities"

mail_activity_portal/__init__.py

@@ -0,0 +1,3 @@
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+from . import models

mail_activity_portal/__manifest__.py

@@ -0,0 +1,21 @@
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+{
+    "name": "Mail Activity on Messages over Portal",
+    "version": "18.0.1.0.0",
+    "category": "Social Network",
+    "author": "Nitrokey GmbH",
+    "website": "https://github.com/Nitrokey/odoo-modules",
+    "license": "AGPL-3",
+    "summary": """
+    * If a messages arrives over the portal an activity for a
+    configured team is scheduled automatically to process the message
+    * The configuration to add RMA and PO models
+    (Settings --> Technical --> Activity Teams menu)
+    """,
+    "depends": [
+        "mail_activity_team",
+        "portal",
+    ],
+    "installable": True,
+}

mail_activity_portal/models/__init__.py

@@ -0,0 +1,3 @@
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+from . import mail_thread

mail_activity_portal/models/mail_thread.py

@@ -0,0 +1,46 @@
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+from odoo import models
+
+
+class MailThread(models.AbstractModel):
+    _inherit = "mail.thread"
+
+    def message_post(self, **kwargs):
+        """create activity from portal message"""
+        msg = super().message_post(**kwargs)
+        # Call method if from portal
+        if not self.env.context.get("allowed_company_ids"):
+            self.schedule_email_activity()
+        return msg
+
+    def schedule_email_activity(self):
+        # Thread needs mail.activity.mixin
+        if not self or "activity_ids" not in self._fields:
+            return
+
+        # Skip if there is no team
+        domain = [("res_model_ids.model", "=", self._name)]
+        team = self.env["mail.activity.team"].sudo().search(domain, limit=1)
+        user = team.user_id or team.member_ids
+        if not team or not user:
+            return
+
+        activity_type = self.env.ref("mail.mail_activity_data_email")
+        for thread in self:
+            domain = [
+                ("res_model", "=", thread._name),
+                ("res_id", "=", thread.id),
+                ("automated", "=", True),
+                ("activity_type_id", "=", activity_type.id),
+            ]
+            if self.env["mail.activity"].search(domain):
+                continue
+
+            # Schedule the new email activity
+            thread.activity_schedule(
+                "mail.mail_activity_data_email",
+                user_id=user[0].id,
+                team_id=team.id,
+                automated=True,
+            )