NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
hoangvv 2025-02-28 02:54:43 +07:00
parent 6b0c648c8e
commit fb158c3b6d
10 changed files with 597 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Makefile
View File

@ -67,8 +67,8 @@ html: $(HTML_BUILD_DIR)/_static/style.css
$(SPHINX_BUILD) -q -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR) $(SPHINX_BUILD) -q -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR)
@echo "Build finished." @echo "Build finished."
livehtml: SPHINXOPTS += -A collapse_menu=True hot_reload: SPHINXOPTS += -A collapse_menu=True
livehtml: hot_reload:
@echo "Starting Live Server..." @echo "Starting Live Server..."
$(SPHINX_AUTO_BUILD) $(SOURCE_DIR) $(HTML_BUILD_DIR) \ $(SPHINX_AUTO_BUILD) $(SOURCE_DIR) $(HTML_BUILD_DIR) \
--port 8000 --host $(SERVER_IP) \ --port 8000 --host $(SERVER_IP) \

7
config.yaml
View File

@ -27,13 +27,14 @@
# -h, --help Show this message and exit. # -h, --help Show this message and exit.
language: en language: en
sphinx: true sphinx: true
default_conversion: parse_all
conversions:
docutils.parsers.rst.directives.images.image: parse_all
sphinx.directives.patches.ListTable: parse_all # For tables if needed
extensions: extensions:
- sphinx.ext.intersphinx - sphinx.ext.intersphinx
- sphinx.ext.todo - sphinx.ext.todo
- sphinx_tabs.tabs - sphinx_tabs.tabs
default_conversion: parse_all
conversions:
docutils.parsers.rst.directives.images.image: parse_content
default_domain: py default_domain: py
consecutive_numbering: true consecutive_numbering: true
colon_fences: true colon_fences: true

0
content/developer/reference/extract_api.md
View File

574
content/developer/reference/extract_api.rst Normal file
View File

@ -0,0 +1,574 @@
===========
Extract API
===========
Odoo provides a service to automate the processing of documents of type **invoices**, **bank statements**,
**expenses** or **resumes**.
The service scans documents using an :abbr:`OCR (Optical Character Recognition)` engine and then
uses :abbr:`AI(Artificial Intelligence)`-based algorithms to extract fields of interest such as the
total, due date, or invoice lines for *invoices*, the initial and final balances, the date for
*bank statements*, the total, date for *expenses*, or the name, email, phone number for *resumes*.
This service is a paid service. Each document processing will cost you one credit.
Credits can be bought on `iap.odoo.com <https://iap.odoo.com/iap/in-app-services/259?sortby=date>`_.
You can either use this service directly in the Accounting, Expense, or Recruitment App or through
the API. The Extract API, which is detailed in the next section, allows you to integrate our
service directly into your own projects.
Overview
========
The extract API uses the JSON-RPC2_ protocol; its endpoint routes are located at
`https://extract.api.odoo.com`.
.. _extract_api/version:
Version
-------
The version of the Extract API is specified in the route.
The latest versions are:
- invoices: 123
- bank statements: 100
- expenses: 132
- applicant: 102
Flow
----
The flow is the same for each document type.
#. | Call :ref:`/parse <extract_api/parse>` to submit your documents (one call for each
document). On success, you receive a `document_token` in the response.
#. | You then have to regularly poll :ref:`/get_result <extract_api/get_result>` to get the
document's parsing status.
| Alternatively, you can provide a `webhook_url` at the time of the call to
:ref:`/parse <extract_api/parse>` and you will be notified (via a POST request) when the
result is ready.
The HTTP POST method should be used for all of them. A python implementation of the full flow for
invoices can be found :download:`here <extract_api/implementation.py>` and a token for integration
testing is provided in the
:ref:`integration testing section <latestextract_api/integration_testing>`.
Parse
=====
Request the processing of a document from the OCR. The route will return a `document_token`,
you can use it to obtain the result of your request.
.. _extract_api/parse:
Routes
------
- /api/extract/invoice/2/parse
- /api/extract/bank_statement/1/parse
- /api/extract/expense/2/parse
- /api/extract/applicant/2/parse
Request
-------
.. rst-class:: o-definition-list
``jsonrpc`` (required)
see JSON-RPC2_
``method`` (required)
see JSON-RPC2_
``id`` (required)
see JSON-RPC2_
``params``
.. rst-class:: o-definition-list
``account_token`` (required)
The token of the account from which credits will be taken. Each successful call costs one
token.
``version`` (required)
The version will determine the format of your requests and the format of the server response.
You should use the :ref:`latest version available <extract_api/version>`.
``documents`` (required)
The document must be provided as a string in the ASCII encoding. The list should contain
only one string. If multiple strings are provided only the first string corresponding to a
pdf will be processed. If no pdf is found, the first string will be processed. This field
is a list only for legacy reasons. The supported extensions are *pdf*, *png*, *jpg* and
*bmp*.
``dbuuid`` (optional)
Unique identifier of the Odoo database.
``webhook_url`` (optional)
A webhook URL can be provided. An empty POST request will be sent to
``webhook_url/document_token`` when the result is ready.
``user_infos`` (optional)
Information concerning the person sending the document to the extract service. It can be
the client or the supplier (depending on the ``perspective``). This information is not
required in order for the service to work but it greatly improves the quality of the result.
.. rst-class:: o-definition-list
``user_company_vat`` (optional)
VAT number of the user.
``user_company_name`` (optional)
Name of the user’s company.
``user_company_country_code`` (optional)
Country code of the user. Format:
`ISO3166 alpha-2 <https://www.iban.com/country-codes>`_.
``user_lang`` (optional)
The user language. Format: *language_code + _ + locale* (e.g. fr_FR, en_US).
``user_email`` (optional)
The user email.
``purchase_order_regex`` (optional)
Regex for purchase order identification. Will default to Odoo PO format if not provided.
``perspective`` (optional)
.. rst-class:: o-definition-list
Can be ``client`` or ``supplier``. This field is useful for invoices only.
``client`` means that the user information provided are related to the client of the
invoice.
``supplier`` means that it's related to the supplier.
If not provided, client will be used.
.. code-block:: js
{
"jsonrpc": "2.0",
"method": "call",
"params": {
"account_token": string,
"version": int,
"documents": [string],
"dbuuid": string,
"webhook_url": string,
"user_infos": {
"user_company_vat": string,
"user_company_name": string,
"user_company_country_code": string,
"user_lang": string,
"user_email": string,
"purchase_order_regex": string,
"perspective": string,
},
},
"id": string,
}
.. note::
The ``user_infos`` parameter is optional but it greatly improves the quality of the result,
especially for invoices. The more information you can provide, the better.
Response
--------
.. rst-class:: o-definition-list
``jsonrpc``
see JSON-RPC2_
``id``
see JSON-RPC2_
``result``
.. rst-class:: o-definition-list
``status``
The code indicating the status of the request. See the table below.
``status_msg``
A string giving verbose details about the request status.
``document_token``
Only present if the request is successful.
=========================== ==============================================================
status status_msg
=========================== ==============================================================
`success` Success
`error_unsupported_version` Unsupported version
`error_internal` An error occurred
`error_no_credit` You don't have enough credit
`error_unsupported_format` Unsupported file format
`error_maintenance` Server is currently under maintenance, please try again later
=========================== ==============================================================
.. code-block:: js
{
"jsonrpc": "2.0",
"id": string,
"result": {
"status": string,
"status_msg": string,
"document_token": string,
}
}
.. note::
The API does not actually use the JSON-RPC error scheme. Instead the API has its own error
scheme bundled inside a successful JSON-RPC result.
Get results
===========
.. _extract_api/get_result:
Routes
------
- /api/extract/invoice/2/get_result
- /api/extract/bank_statement/1/get_result
- /api/extract/expense/2/get_result
- /api/extract/applicant/2/get_result
Request
-------
.. rst-class:: o-definition-list
``jsonrpc`` (required)
see JSON-RPC2_
``method`` (required)
see JSON-RPC2_
``id`` (required)
see JSON-RPC2_
``params``
.. rst-class:: o-definition-list
``version`` (required)
The version should match the version passed to the :ref:`/parse <extract_api/parse>` request.
``document_token`` (required)
The ``document_token`` for which you want to get the current parsing status.
``account_token`` (required)
The token of the account that was used to submit the document.
.. code-block:: js
{
"jsonrpc": "2.0",
"method": "call",
"params": {
"version": int,
"document_token": int,
"account_token": string,
},
"id": string,
}
Response
--------
When getting the results from the parse, the detected field vary a lot depending on the type of
document. Each response is a list of dictionaries, one for each document. The keys of the dictionary
are the name of the field and the value is the value of the field.
.. rst-class:: o-definition-list
``jsonrpc``
see JSON-RPC2_
``id``
see JSON-RPC2_
``result``
.. rst-class:: o-definition-list
``status``
The code indicating the status of the request. See the table below.
``status_msg``
A string giving verbose details about the request status.
``results``
Only present if the request is successful.
.. rst-class:: o-definition-list
``full_text_annotation``
Contains the unprocessed full result from the OCR for the document
================================ =============================================================
status status_msg
================================ =============================================================
`success` Success
`error_unsupported_version` Unsupported version
`error_internal` An error occurred
`error_maintenance` Server is currently under maintenance, please try again later
`error_document_not_found` The document could not be found
`error_unsupported_size` The document has been rejected because it is too small
`error_no_page_count` Unable to get page count of the PDF file
`error_pdf_conversion_to_images` Couldn't convert the PDF to images
`error_password_protected` The PDF file is protected by a password
`error_too_many_pages` The document contains too many pages
================================ =============================================================
.. code-block:: js
{
"jsonrpc": "2.0",
"id": string,
"result": {
"status": string,
"status_msg": string,
"results": [
{
"full_text_annotation": string,
"feature_1_name": feature_1_result,
"feature_2_name": feature_2_result,
...
},
...
]
}
}
Common fields
~~~~~~~~~~~~~
.. _latestextract_api/get_result/feature_result:
``feature_result``
******************
Each field of interest we want to extract from the document such as the total or the due date are
also called **features**. An exhaustive list of all the extracted features associated to a type of
document can be found in the sections below.
For each feature, we return a list of candidates and we spotlight the candidate our model predicts
to be the best fit for the feature.
.. rst-class:: o-definition-list
``selected_value`` (optional)
The best candidate for this feature.
``selected_values`` (optional)
The best candidates for this feature.
``candidates`` (optional)
List of all the candidates for this feature ordered by decreasing confidence score.
.. code-block:: js
"feature_name": {
"selected_value": candidate_12,
"candidates": [candidate_12, candidate_3, candidate_4, ...]
}
candidate
*********
For each candidate we give its representation and position in the document. Candidates are sorted
by decreasing order of suitability.
.. rst-class:: o-definition-list
``content``
Representation of the candidate.
``coords``
.. rst-class:: o-definition-list
``[center_x, center_y, width, height, rotation_angle]``. The position and dimensions are
relative to the size of the page and are therefore between 0 and 1.
The angle is a clockwise rotation measured in degrees.
``page``
Page of the original document on which the candidate is located (starts at 0).
.. code-block:: js
"candidate": [
{
"content": string|float,
"coords": [float, float, float, float, float],
"page": int
},
...
]
Invoices
~~~~~~~~
Invoices are complex and can have a lot of different fields. The following table gives an exhaustive
list of all the fields we can extract from an invoice.
+-------------------------+------------------------------------------------------------------------+
| Feature name | Specificities |
+=========================+========================================================================+
| ``SWIFT_code`` | ``content`` is a dictionary encoded as a string. |
| | |
| | It contains information about the detected SWIFT code |
| | (or `BIC <https://www.iso9362.org/isobic/overview.html>`_). |
| | |
| | Keys: |
| | |
| | .. rst-class:: o-definition-list |
| | |
| | ``bic`` |
| | detected BIC (string). |
| | ``name`` (optional) |
| | bank name (string). |
| | ``country_code`` |
| | ISO3166 alpha-2 country code of the bank (string). |
| | ``city`` (optional) |
| | city of the bank (string). |
| | ``verified_bic`` |
| | True if the BIC has been found in our DB (bool). |
| | |
| | Name and city are present only if verified_bic is true. |
+-------------------------+------------------------------------------------------------------------+
| ``iban`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``aba`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``VAT_Number`` | ``content`` is a string |
| | |
| | Depending on the value of perspective in the user_infos, this will be |
| | the VAT number of the supplier or the client. If perspective is |
| | client, it'll be the supplier's VAT number. If it's supplier, it's the |
| | client's VAT number. |
+-------------------------+------------------------------------------------------------------------+
| ``qr-bill`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``payment_ref`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``purchase_order`` | ``content`` is a string |
| | |
| | Uses ``selected_values`` instead of ``selected_value`` |
+-------------------------+------------------------------------------------------------------------+
| ``country`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``currency`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``date`` | ``content`` is a string |
| | |
| | Format : *YYYY-MM-DD* |
+-------------------------+------------------------------------------------------------------------+
| ``due_date`` | Same as for ``date`` |
+-------------------------+------------------------------------------------------------------------+
| ``total_tax_amount`` | ``content`` is a float |
+-------------------------+------------------------------------------------------------------------+
| ``invoice_id`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``subtotal`` | ``content`` is a float |
+-------------------------+------------------------------------------------------------------------+
| ``total`` | ``content`` is a float |
+-------------------------+------------------------------------------------------------------------+
| ``supplier`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``client`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``email`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``website`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
``invoice_lines`` feature
*************************
It is returned as a list of dictionaries where each dictionary represents an invoice line.
.. code-block:: js
"invoice_lines": [
{
"description": string,
"quantity": float,
"subtotal": float,
"total": float,
"taxes": list[float],
"total": float,
"unit_price": float
},
...
]
Bank statements
~~~~~~~~~~~~~~~
The following table gives a list of all the fields that are extracted from bank statements.
+-------------------------+------------------------------------------------------------------------+
| Feature name | Specificities |
+=========================+========================================================================+
| ``balance_start`` | ``content`` is a float |
+-------------------------+------------------------------------------------------------------------+
| ``balance_end`` | ``content`` is a float |
+-------------------------+------------------------------------------------------------------------+
| ``date`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
``bank_statement_lines`` feature
********************************
It is returned as a list of dictionaries where each dictionary represents a bank statement line.
.. code-block:: js
"bank_statement_lines": [
{
"amount": float,
"description": string,
"date": string,
},
...
]
Expense
~~~~~~~
The expenses are less complex than invoices. The following table gives an exhaustive list of all the
fields we can extract from an expense report.
+-------------------------+------------------------------------------------------------------------+
| Feature name | Specificities |
+=========================+========================================================================+
| ``description`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``country`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``date`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``total`` | ``content`` is a float |
+-------------------------+------------------------------------------------------------------------+
| ``currency`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
Applicant
~~~~~~~~~
This third type of document is meant for processing resumes. The following table gives an exhaustive
list of all the fields we can extract from a resume.
+-------------------------+------------------------------------------------------------------------+
| Feature name | Specificities |
+=========================+========================================================================+
| ``name`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``email`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``phone`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
| ``mobile`` | ``content`` is a string |
+-------------------------+------------------------------------------------------------------------+
.. _latestextract_api/integration_testing:
Integration Testing
===================
You can test your integration by using *integration_token* as ``account_token`` in the
:ref:`/parse <extract_api/parse>` request.
Using this token put you in test mode and allows you to simulate the entire flow without really
parsing a document and without being billed one credit for each successful **document** parsing.
The only technical differences in test mode is that the document you send is not parsed by the
system and that the response you get from
:ref:`/get_result <extract_api/get_result>` is a hard-coded one.
A python implementation of the full flow for invoices can be found
:download:`here <extract_api/implementation.py>`.
.. _JSON-RPC2: https://www.jsonrpc.org/specification
.. |ss| raw:: html
<strike>
.. |se| raw:: html
</strike>

24
content/developer/reference/user_interface/view_architectures.md
View File

@ -209,7 +209,7 @@ The `field` element can have the following attributes:
<field name="tag_ids" widget="many2many_tags" options="{'color_field': 'FIELD_NAME', 'no_quick_create': True}"/> <field name="tag_ids" widget="many2many_tags" options="{'color_field': 'FIELD_NAME', 'no_quick_create': True}"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `{}` :default: `{}`
``` ```
@ -242,7 +242,7 @@ The `field` element can have the following attributes:
<field name="fname" domain="[('fname_a', '=', parent.fname_b)]"/> <field name="fname" domain="[('fname_a', '=', parent.fname_b)]"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `[]` :default: `[]`
:scope: Relational fields :scope: Relational fields
``` ```
@ -269,7 +269,7 @@ The `field` element can have the following attributes:
}"/> }"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `{}` :default: `{}`
:scope: Relational fields :scope: Relational fields
``` ```
@ -1434,7 +1434,7 @@ Optional attributes can be added to the root element `list` to customize the vie
</list> </list>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `False` :default: `False`
``` ```
@ -1583,7 +1583,7 @@ The `field` element can have the following attributes:
<field name="quantity" decoration-info="state == 'draft'"/> <field name="quantity" decoration-info="state == 'draft'"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `False` :default: `False`
``` ```
@ -1909,7 +1909,7 @@ The `create` element can have the following attributes:
expression that evaluates to a dict. expression that evaluates to a dict.
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `{}` :default: `{}`
``` ```
@ -2046,7 +2046,7 @@ The `field` element can have the following attributes:
precedence. precedence.
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `[]` :default: `[]`
``` ```
@ -2060,7 +2060,7 @@ The `field` element can have the following attributes:
It can contain user-provided values, which are available under the `self` variable. It can contain user-provided values, which are available under the `self` variable.
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `{}` :default: `{}`
``` ```
@ -2072,7 +2072,7 @@ The `field` element can have the following attributes:
:class:`~odoo.fields.Many2one`). :class:`~odoo.fields.Many2one`).
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `[]` :default: `[]`
``` ```
@ -2159,7 +2159,7 @@ The `filter` element can have the following attributes:
The domain to append to the action's domain as part of the search domain. The domain to append to the action's domain as part of the search domain.
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `[]` :default: `[]`
``` ```
@ -2340,7 +2340,7 @@ The `filter` element can have the following attributes:
:class:`~odoo.fields.Field`. :class:`~odoo.fields.Field`.
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `{}` :default: `{}`
``` ```
@ -2580,7 +2580,7 @@ attributes:
</searchpanel> </searchpanel>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `[]` :default: `[]`
``` ```

2
content/developer/reference/user_interface/view_architectures/button_attribute_context.md
View File

@ -11,7 +11,7 @@
<button name="button_confirm" type="object" context="{'BUSINESS_KEY': ANY}" string="LABEL"/> <button name="button_confirm" type="object" context="{'BUSINESS_KEY': ANY}" string="LABEL"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `{}` :default: `{}`
``` ```

2
content/developer/reference/user_interface/view_architectures/field_attribute_readonly.md
View File

@ -12,7 +12,7 @@
<field name="fname_b" readonly="name_a in [fname_b, parent.fname_d]"/> <field name="fname_b" readonly="name_a in [fname_b, parent.fname_d]"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `False` :default: `False`
``` ```

2
content/developer/reference/user_interface/view_architectures/field_attribute_required.md
View File

@ -12,7 +12,7 @@
<field name="fname_b" required="fname_c != 3"/> <field name="fname_b" required="fname_c != 3"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `False` :default: `False`
``` ```

2
content/developer/reference/user_interface/view_architectures/generic_attribute_column_invisible.md
View File

@ -14,7 +14,7 @@
<button type="object" name="action_confirm" column_invisible="context.get('hide_confirm')"/> <button type="object" name="action_confirm" column_invisible="context.get('hide_confirm')"/>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `False` :default: `False`
``` ```

2
content/developer/reference/user_interface/view_architectures/generic_attribute_invisible.md
View File

@ -24,7 +24,7 @@
<group> <group>
:requirement: Optional :requirement: Optional
:type: :ref:`Python expression <reference/view_architectures/python_expression>` :type: :ref:`Python expression <reference-view-architectures-python-expression>`
:default: `False` :default: `False`
``` ```