Subscriptions now include pivot and graph views, making it easier for teams to analyze subscription data visually. This helps business users spot trends and compare performance without relying on custom exports or technical reporting work.

Task: https://www.odoo.com/web?#id=21702&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
Pad: https://pad.odoo.com/p/r.PD1BJCCvjFgxSq3s

This change adds an embedded code-style editor for selected backend text fields, making it easier to view and edit structured text such as scripts or templates. The editor is loaded only when needed, helping provide the new editing experience without slowing down normal page use.

use with `widget="ace"` on text fields

This change adds an embedded code editor to the web module so users can edit technical text fields, such as Python or XML, with better formatting and readability. It loads the editor only when needed, helping support website and web editing without adding unnecessary overhead elsewhere.

…e are going to create ace editor widget for web module

Task: https://www.odoo.com/web?#id=12841&view_type=form&model=project.task&action=327
Pad: https://pad.odoo.com/p/r.FEH8ALWJdkNQniJU

Point of Sale users can no longer create orders or sessions directly from backend screens. This keeps POS activity managed through the dashboard, reducing confusing open payments and reconciliation issues.

Description of the issue/feature this PR addresses:
Task: https://www.odoo.com/web#id=27843&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
Pad: https://pad.odoo.com/p/r.6f4fa09d368b1fd17ed918cb64e6699f

Current behavior before PR:
User can create pos order from backend.

Desired behavior after PR is merged:
User shouldn't create pos order from backend.
## 

I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Links to business records shared in chatter now open with the correct form view, such as the right invoice type instead of always showing the vendor invoice layout. The update also preserves expected behavior when clicking followers, so users continue to open partner records directly from the followers list.

There already is a redirect implementation in the chat_manager
however the former has the advantage of calling get_formview_id
which closely matches the on_redirect implementation in chatter.js,
to ensure that the view is correct.

This fixes a faulty behaviour when some models are referenced from
chatter message using data attribute data-oe-model and data-oe-id.
For example, linking invoices in the chatter would always open them
with the 'vendor invoice' view; from this revision on the correct
view will be used (assuming get_formview_id is implemented on the
model).

The default behaviour of the chat_manager when a user clicks on a
partner record is to open a channel if the partner has a user then
return a callback passed as a parameter (usually to open the channel
as a popup or in the discuss app). To keep the old behaviour
of the chatter followers list widget (i.e. open the partner form
when clicking on a follower), a small change has to be made on the
redirect implementation: when no callback is provided, do not create
the channel (instead a returning an empty callback).