upload document and run all activities around this upload takes time, so we use a larger timeout

erp5_officejs_support_request_ui_test: Add test to make sure we have all expected actions to access support request web site

* Check if each portal_type has the expected view action
* add test to cover all possible attachments in a Support Request

HACK erp5_officejs_support_request_ui: Simplify code to render the expected action to preview any attachement document

Some portal types don't have preview action reference. In such case, we get html_view

erp5_web_renderjs_ui: Refactor code to support more than option as page

Sometimes we can display "preview" or "html_view"

erp5_web_renderjs_ui: Small changes on router to follow latest erp5 master

This improve the compatibility with ERP5JS

This is something we can do in TALES, it was supported in the old UI, so
we keep compatibility in HAL JSON API.

Replace it by domsugar.

This speed up gadget class generation (handlebars template parsing is
slow).

Introduce the object_jio_jump action category to mark all compatible actions.

erp5_xhtml_style supports object_jio_jump.

A correct redirection is needed to jump in both UI.

ERP5JS will display modules on the current document context,
as if the jump was instead a object_view action.

erp5_officejs_support_request_ui: Add begin date to the query when user click on "Last Month Activity"

The filter when the user click on the "Last Month Activity" chart filter Support Request only by status (Submitted / Open / Suspended / Closed). So on the table "Recent updates", all the support request with the chosen status appear. There is no filter by "Begin Date" for the last 30 days, which is no coherent with the "Last Month Activity". => It should appear only the support request with the chosen status with a begin date < D - 30 days

Make sure we have gadget.state.form_id

It seems that with ${here/portal_url} returns the ERP5 url , for example http://nohost/erp5 instead of

http://nohost/erp5/web_site_module/renderjs_runner/

Table columns to be displayed by default in the following (from the left to the right of the screen) :

Title
Visa Files Reference
Type
Requester
Begin Date
Comment Date (with possibility to sort the table by this column desc and asc)
Comment Author
State

According to Google's branding guidelines [1], using zocial like we did is not
OK because the logo is different.

To comply with Google's branding guidelines, we simply use an image from
"Download files" section of the Sign-In Branding Guidelines page. Using a png
image is not really good, but a vector version would require to download a
font, so the image way is easier.

1: https://developers.google.com/identity/branding-guidelines

using the same "image button" approach as for erp5_xhtml_style

These authentications are using a different cookie.

ERP5JS web sites, when accessed with their full path, needs the trailing
slash, so add it before redirecting. This should not be a problem in the
case of xhtml style

For consistency with other ERP5JS dialogs

For consistency with xhtml style and other ERP5JS dialogs

This way, the padding between fields will be applied and the visual
result would be similar as on all other ERP5JS dialogs

This way we don't need to define absolute_url multiple times

CUSTOM erp5_officejs_support_request_ui: Change default data to be displayed in support request listboxes

Table columns to be displayed by default in the following (from the left to the right of the screen) :

Title
Visa Files Reference
Type
Requester
Begin Date
Comment Date (with possibility to sort the table by this column desc and asc)
Comment Author
State

HACK: erp5_officejs_support_request_ui: Pass vile file reference as parameter and store as causality

Allow to use it from erp5_xhtml_style.

update should still be usable in this case