Jan Flink

Hi Arne, the custom palette groups are independent regarding the group configuration of integrated tools. Moving components to custom groups is a local, profile based, configuration and has no effect...

Hello Arne, Not enabling drag & drop for group assignments was conscious usability decision. Since drag-and-drop is used to add components to a workflow and the assignment of components to...

We are not able to reproduce this issue within our current RCE 9 release cycle. Maybe the problem vanished due to further developments regarding the SSH connections. We will keep...

Hi JASaa, Well, by considering the given details, I understand that you will pass a .txt file to output0. In order to do this, you need to specify the path...

An issue has been added to our internal issue tracker: https://mantis.sc.dlr.de/view.php?id=17074

Hi Arne, the components.json file is currently not intended to be changed programmatically from outside RCE. So RCE will not be notified of changes on any system. There is also...

What is the reason to update the `components.json`? This file currently only holds the publishing information that are handled by the `set-auth` command.

Okay, I see. It would also be a good choice to publish components to the public group via the `set-auth` command. Then, the components are instantly available in the RCE...

But in this issue you describe that you first change the components.json file programmatically and then use the `set-auth` command. Since modifying the file from outside is not intended, this...

`rcec.exe` starts RCE with an additional console window. It acts like `rce.exe -console`. Thanks for pointing out that the documentation is missing information on this.