problem

During the usage of the REST API the following problems popped up:

1. the task entity must contain the current workflowStepName for filtering tasks via API (the current stepName can be selected from LEK_workflow_log)
2. Some custom data fields are needed in the task entity, for example for a local task id or name in a system using translate5 via API. This fields are not visible in the translate5 GUI, just via API (for example apiForeignId or so)
3. The languages fields accept only language IDs, this must be changed, so that it accepts multiple values:
   ##if it is a string, then its interpreted as rfc language name
   ##if it is a string starting with LCID- the given value is a LCID, for example LCID-123
   ##if it is an integer it is the internal language id as it is currently implemented
   Or better idea: create separate named fields, so that it works also for reading tasks...