General

The following overviews will have the attribute "client":

• task overview
• user management
• language resources overview

Migration

In the migration to the new feature it is ensured, that in every instance without existing clients a default client is created and all existing tasks, users and language resources are associated to this client, if they are not associated with a client so far.

Renaming of "end customer" to "client"

All existing GUI texts that contain the word "end customer" or "customer" are renamed to the more generic "client".

General switch of client

A drop-down "Switch client" is implemented in the head area of translate5 that allows to select one of the existing clients.

By default nothing is selected and no overview is filtered.

If a client is selected,

• the list filter of task overview, user management and match resources overview is set accordingly.
• If the setting of one of these filters is changed manually (and thus the different filters of the different grids are not consistent any more) the client that is currently selected in the "Switch client" drop-down is automatically deselected.  Changed: synchronized, not deselected
• this client is preselected when adding tasks, users and languageresources.

This switch should only be visible for users with a specific right.

Task overview

Add task

In the "Add task" window a drop-down "clients" is added, if there is more than one client defined. Changed for new concept (show ALL customers that exist)

If there is only one client defined, this client is automatically associated and the drop-down is ommitted. Changed for new concept (if one customer is selected by filtering: set this one as selected already).

Language resources that are assigned as default language resource for a client, are associated automatically with tasks for this client. (But only if the language combination matches.)

Task listing

A new column "client" is added right to the column "Status".

It has a string filter and is visible by default.

Task properties

• Match resource association: Only match resources can be associated to a task, that are associated to the same client as the task is.
• Properties: show client, too (but not editable!).

User management

Client functionality is already implemented into the user management. It needs to be checked and adjusted regarding its dependencies with the client functionality in the overall application and the other overviews.

Match resources management

Client functionality is currently being implemented into the match resources management (in the future called language resources management) via the coming InstantTranslate feature. It needs to be checked and adjusted regarding its dependencies with the client functionality in the overall application and the other overviews.

Open Issues as of 12.12.2018

• setzen der Auswahl zurück auf "all clients" entfernt den Filter im taskgrid nicht
• setzen der Auswahl zurück auf "all clients" entfernt den Filter im taskgrid nicht
• defaultcustomer ist bei task-anlage nicht auswählbar (hatten wir glaube ich mal so besprochen, macht aber keinen Sinn, wenn wir das Feld als Pflichtfeld haben und alle Tasks zu einem Kunden gehören müssen)
• Der Kunde wird im Tab "Eigenschaften" der task-properties nicht angezeigt.

Open Issues as of 18.12.2018

• bei task anlegen: customer ist Pflichtfeld, auch so anzeigen (Fußnoten-1) + ALLE customer anzeigen (IMMER; wenn gefilert von CustomerSwitch: wie bisher als Voreintrag nehmen)
• user anlegen: ALLE customer anbieten, customer ist KEIN Pfilchtfeld (unabh. von Vorhandensein und evtl. Auswahl v. CustomerSwitch und unabh. davon, ob/welche customer dem eingeloggten user zugewiesen sind)
• synchronize filtering by CustomerSwitch and by GridFilter (= other than originally: when a user filters the customer in the grid manually, the CustomerSwitch is not deselected, but set according to the filter)
• add task: allow to select exact ONE customer only
• add task: Wer den CustomerSwitch sehen darf, darf alle auswählen, sonst nur die zugewiesenen.
• fix: apply customerSwitch-filter when the gridfilter is set already (the gridfilter gets not cleared before => the customSwitch filters on the already filtered grid)
• languageResources: filtering the grid on customers causes 500-Server-Error
• filtering for "u" shows only the tasks of one customer and not of all customers that contain "u"
• setting a filter in the task grid and resetting the filter via the switch results in the clients column header still being bold and italic (meaning for ExtJS the filter is still set in some way)
• Zusammenspiel haut noch nicht immer ganz hin => erst mal Umstellung auf grid-Filter statt store-Filter umsetzten
• update content in filters in the other grids (if checked or not, last filtered string) according to the filtering of the currently shown grid and the CustomerSwitch
• Snychronisieren der grids geht erst, nachdem sie einmal geladen wurden
• after the gridfilter has been used: SwitchCustomers eg to "defaultcustomer", then back to "All Clients" => the column is still bold and italic (although the grid-column's filter-box is not checked and empty and the network-panel also shows no filter) - Sogar Filter an und abklicken in der GridSpalte ändert nichts; erst wenn Text eingetragen und gelöscht wurde. Idee für Workaround: Dem Filter dann halt erst einen value geben und dann wieder löschen, DAS ERKENNT ExtJs ja und setzt den Spaltenkopf richtig.-
  Anmerkung: Das Phänomen taucht auch ohne CustomerSwitch auf: auf einen Text filtern -> Text löschen -> FilterCheckbox anklicken: Die Spalte wird IMMER als gefilert angezeigt.

Changes in concept for future purposes:

• for users: customers CAN be empty! (eg managers should be able to see everything without being assigned to every customer)