For same reasons as on Web Sections: clicking the Contents tab search
for all documents

The accessor was added in 99cd5823 (erp5_property_sheets: Add
Predicate/empty_criterion_valid_property ., 2013-11-20) it's been
long enough to assume that every site have this property now.

This was something supported only in ClockServer. Zope's ZServer had an
API to control the shutdown sequence, by allowing servers to implement a
clean_shutdown_control method that was be called at every phase of the
shutdown:

https://github.com/zopefoundation/ZServer/blob/0259e288/src/Lifetime/__init__.py#L20-L38

ClockServer was implementing clean_shutdown_control method:
https://lab.nexedi.com/nexedi/erp5/blob/07a136ec3/product/ClockServer/ClockServer.py#L57

and as described in the README ( https://lab.nexedi.com/nexedi/erp5/blob/07a136ec3/product/ClockServer/README#L32 ),
it was expected to be configured to call TimerService's process_shutdown.

It seems we were using a mix of ClockServer + TimerService at the time,
but this was maybe never used.

In 49400d40 (we don't use ClockServer. we use TimerService instead.,
2013-10-07) we removed ClockServer. Since this day this code is not used.

In WSGI mode, there's no "clean_shutdown_control" API, so this

We don't even use the new updateLocalRolesOnSecurityGroups instead,
because roles are supposed to be applied by an interaction workflow.

With this, we accept users with permission to Modify portal content or Associate role

🚧 also fix transition text

f0808ac6 (workflow: add workflow transition guard for non-user
actions as well., 2015-11-18) broke some custom security
configurations where doing an action on a document would modify an
accounting transaction - but the user doing this action does not have
access to accounting.

This repairs a little part of the situation (the part we are currently
using in a project), by using the Associate role. The idea is that
for such patterns where users "do something which will interact with
accounting", the users also need an Associate role on accounting
transaction portal types, which is in line with the meaning of
Associate.

With this, change we accept users with permission to Modify portal content or Associate role

This makes this index usable in queries involving flows of movements a resource
on a node at a given date, and still usable for movements of a resource on a
node.

This reverts commit 50133064d632a3c3774c2714193c47c76d3e7fe6.

This was just a proof of concept, it breaks when the
PDF_getTravellerDataEncryptionPassword script is not present (and for now it's
not - and also it seems a bit misnamed this is not limited to "Traveller")

The gadget will build a string query from these, so depending on the
translation, this may not work (for example if the translation of a state was
"O\" OR 1=1", but that should be good enough for English and french

This workflow is used only with portal types translated to french feminine noun (
Campaign, Meeting, Support Request, Software Publication).

XXX but if we consider "${portal_type} à l'état ${state}" then state does not
need to be accordé... maybe this is not a good idea.

We don't want to include a full build of locales, so for now since we
needs it only for french, we include the localization inline here.

HACK: This needs more thinking about what is the right way. This way
works for now.

This is done using the obsolete/slow translate/translateHtml because we
needed this for a customer project where we are not yet using the new
techniques for translation.

HACK because we'll probably do this with domsugar in erp5 master

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

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 visa file reference as parameter and store as causality

( Also, remove the usage of document.getElementById because we should search only inside the current gadget )
( Jérome: the getElementById thing was lost in rebase. It is not critical in my understanding )

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

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.

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