Skip to Content (Press Enter)
Back to Ideas
5
Like
Follow Idea
Forge - O11 - Add information
186Views
4Comments
New
Forge

Hi all, 

here's my idea for the OutSystems Forge portal.

About Forge components for O11, I think it's usefull to add three important details:

  1. Very often, the Forge components don't have the correct module naming convention. So, we have to assign the correct layer in Discovery. It's crucial to have suggestions from the Forge component developer about the correct layer to assign. Usually, we have to solve discovery problems (as upper references, side references) due to this missing naming convention. 
  2. The first point usually helps to solve the technical debt level in AI mentor, but not all the issues. It's interesting to show the AI mentor analysis about Forge components itself for two reasons: 

    • To permit the Forge component developer to define if the problem is known and if it's a false positive or something like this.

    • To highlight the technical debt level before to install

  3. short descriptions about Roles based on Roles' description. Usually this description is missing or incomplete

This idea is to encourage developers to follow best practices and to help the CoE to address this issue efficiently. 

thank you, 

Roberta

14 Feb 2024
Copy link to comment

Hi Roberta,

I don't understand point 1, a wrong naming convention doesn't case architecture problems like upper/side references. You can also discuss whether at all put Forge components in a seperate Team in LifeTime, so you can seperate them from your 'own'  technical debt in AI Mentor Studio. That is what we most of the times do, as we prefer not to change downloaded Forge components.

But overall I agree with you, that the quality of Forge components, in regards to best practices is something that could improve. OutSystems does curate Forge components, but this is a process that MVPs for example volunteer in. It is time consuming, to do this for all components.

Any Forge component that adheres to all Best Practices will get the Trusted badge.

Regards,

Daniel

15 Feb 2024
Copy link to comment

Hi Daniel, 

Regarding point 1, it means that without the correct naming convention, the module will not be assigned to the correct layer automatically. The developer who created the Forge component is usually the one who can specify the correct layer for each module. 

As for creating a separate team, I do the same by adding Forge components to a dedicated team. However, technical debt is an overall measurement on an OutSystems platform. 

For example, understanding the reasons behind security issues is crucial. When there are numerous developer teams and projects, we need an efficient system to manage and quickly address potential "False positives" or "Won't Fix" items in forge components. 

I believe that such a process can be managed with community involvement, and it could be the horizon for improvement. Adding this information during the Forge component upload can be helpful. 

Thank you for your response and understanding. 

best regards,

Roberta



15 Feb 2024
Copy link to comment

How you manage tech debt for OutSystems components, for example OutSystemsUI is terrible in terms of Tech Debt, you are not going to fix that right?

15 Feb 2024
Copy link to comment

Hi Daniel, 

I have never seen OutSystemsUI in AI mentor, or do you refer to other OutSystems Maps o something like this? 

We usually don't modify the forge components but we work to manage potential false positive or won't fix. 

thank you, 

best regards,

Roberta

16 Feb 2024
Copy link to comment