Alberto, I am certain that this solution will not only fill a significant gap in the platform but also enrich the OutSystems community as a whole. Congratulations! 

Hi Alberto,

We cannot expect OutSystems to built everything native, the community pitches in and shares components for reuse on the Forge.  And what does native mean? OutSystems uses the same stack as a developer in OutSystems creating a Forge component: a mixture of OutSystems low-code, Javascript, HTML and CSS.

Did you have a look at this Forge component:
https://www.outsystems.com/forge/component-overview/7575/hierarchical-organizational-chart-o11

It also has this demo:
https://sylvain-billot.outsystemscloud.com/HierarchicalOrganizationalLiveDemo/

There is also this other component:

https://www.outsystems.com/forge/component-overview/11900/hierarchical-treeorganisation-chart-o11

Regards,

Daniel

Hi Daniel,

Actually, I don't expect anything at all. In fact, I recently needed something similar and none of those at Forge were productive and I ended up developing my own solution in JavasCript (and I will also post it on Forge).

That being said, isn't this a place for new ideas? I believe this idea is valid because I have clients who have explicit policies not to use Forge assets if they are not supported by Outsystems.

When I brought this idea up, I didn’t create any expectations about it. But is it an idea, or not?

Regards,

Alberto.

Yes it is an idea, you are right. I just tried to understand why it needs to be native in the platform and what that actually means.