REFramework as Library

- This is great. It abstracts much of the implementation allowing for a cleaner project. Unfortunately, I have two issues with it. Although it can read from a xlsx config file, it also creates the config.json. I suggest adding a dropdown to the Utilities to choose the type of config, and then generate just the one selected. The second problem is regarding Orchestrator Assets. The original framework can load them through the Assets sheet inside the config file, but your solution ignores these and doesn't load their values. I would love to fix the problems myself but the source code isn't open. Can I expect a fix for the Assets problem?

Cool approach - I've tried it and it works! It's very nice to see a new approach to REFramework. Definitely easier for new users to understand and build their processes around. This custom-activity based approach seems to me like it has a lot of potential, looking to see it developed further!