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

Like a real-world user.

If we have more than two options to project and resource

Also, remove the usage of document.getElementById because we should search only inside the current gadget

erp5_officejs_support_request_ui: 'Customer Support Dashboard' in 'Support Requests Dashboard' (in header)

- change the generate_rss_link action in Support Request Module, to directly call SupportRequestModule_generateRSSLinkUrl.py instead of the form.
- change SupportRequestModule_generateRSSLinkUrl to display the form at the end.
- Use Base_renderForm like for erp5_crm
- Put the RSS url in the REQUEST
- change the gadget field configuration to use the value from the REQUEST (if not found, put None)
- change the gadget implementation to display the URL in an html5 string field  + a button

In Support request test we trigger clipboard API to copy RSS Link

But, if you running tests manually in your browser, clipboard will fail.
For now, we guarantee that is not break tests on test node

erp5_officejs_support_request_ui: Search action dynamically according to the action category defined on web site

Hard coding to select action_object_view we will never use web site configuration.

If we always get links from action_object_view, Support Request will always break if we change View Action Category on web site.

Having a big "Generate RSS" button on the front page is strange, because the front page button are for common use cases that users are supposed to execute a lot.

For example, makes sense to have a "Submit new Support Request" button, because users are using this app to submit support requests, but generating RSS is very exceptional action, so we wanted to remove it from the front page.

According to Galien:

In the table, columns to be displayed by default in the following order are :
- Title
- Visa File Reference
- Type
- Requester
- Begin Date
- Comment Date (with possibility to sort the table by this column desc and asc)
- Comment Author
- State

With this, sort by reference will work properly

CUSTOM erp5_officejs_support_request: Add visa_file_reference as parameter and redirect to the expected view

In support request, we need to receive visa_file_reference and store it as causality. With this, we have the relation between Support Request and Visa File

Also, we change the action reference because the previous is not available in our scenario(Default View Action reference).

This will be used by Capago to assign a Support Request to Visa File

Requested in an email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison Interface Consulaire ERP5 .pdf". Suppression des boutons d’action : “Sort” / “Edit” / “Select” , section 4.1.4, item a, page 14

Requested in an email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison Interface Consulaire ERP5 .pdf" Suppression des boutons d’action : "Sort ", page 4.1.4 item A, page 14

> email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison
> Interface Consulaire ERP5 .pdf" Suppression des boutons d’action : ““Edit” / “Select”, page 4.1.4 item a page 14

Requested in an email from Galien Renault with title "Retour livraison
interface consulaire" document "Retour livraison Interface Consulaire
ERP5.pdf", section 4.1.4d page 16

Requested in an email from Galien Renault with title "Retour
livraison interface consulaire" document "Retour livraison Interface
Consulaire ERP5.pdf", part 3.2.2c page 10

- Il devrait être impossible de crée"New Event" pour un
ticket au statut "Closed"

This action is not suppose to work, because they should a new post in the Suppport Request instead of a new event directly.

Because this breaks the sort and filter buttons in the new ERP5 UI