If in M.App Enterprise a workflow is created to draw new polygons, the Desktop App (Thick Client) give’s an error that the geometry can’t be saved. In the error log there is a message, which says it searches the workflow on a server in Vienna in a Tenant called New York. This connection is stored hardcoded in the M.App Enterprise, because I didn’t even know about the existents of this server. See screenshot.

Because of this hardcoded server, connection I don't think we can build a workflow where we can create new geometry's.

We re-installed M.App Enterprise, with the above version. In the log I do not find any link to the server to vienna anymore, which is good. However, I still got the same error on screen. Now I got a different error in the log

Had some problems with the community. This is the thirs time I'm trying to report my logs. But somehow I can't post the error message here, so I added as zip file. I've got an other error message as above.

I've will check my geometries also as suggested above, but I'm sure they are correct.

the error in your case looks different: looks like there is a wrong "connection" between the workflow configuration and the map content (layer or specific object). Do you have the same error for all the layers in your legend?

everything looks correct at first impression. I see you are using a PostGIS database, sometimes I've got problems with tables with capital letters, because it is case sensitive probably (in some cases you have to include the table name in double quotes). Can you try with a simple table name (no big letters and special chars)?