search

UiPath / ReFrameWork

Robotic Enterprise Framework Template
MIT License
342 stars 564 forks source link

Binary Config.xlsx - worst file format for merging #17

Closed misiam closed 4 years ago

misiam commented 4 years ago

As a POC Config.xlsx was a very good concept. But for now, any binary file in development provides problems with merging and I with it is possible to switch from it to any plain text format as a set of files "csv","tsv" or single file "json" with a set of nodes.

Blackspo0n commented 4 years ago

I fully agree. The big downside is that end users from the workflow mostly familar with excel and dont even know what json is. It would be a step back in terms of accesablity.

I thought long about it and I think configurations should be integrated directly in the project. End users could modify these settings with a user friendly and easy to use gui from the agent. For unattended robots the orchestrator can manage these or even provide a form, similar to "kapplets" from kapow.

misiam commented 4 years ago

I fully agree. The big downside is that end users from the workflow mostly familar with excel and dont even know what json is. It would be a step back in terms of accesablity.

I thought long about it and I think configurations should be integrated directly in the project. End users could modify these settings with a user friendly and easy to use gui from the agent. For unattended robots the orchestrator can manage these or even provide a form, similar to "kapplets" from kapow.

Sad but true. That is why I mentioned CSV which is not so familiar for non developers as xlsx but could bring the similar experience by using MS Excel. In any case, thanks for the answer.