Hi! Mathutils component is flagged as "traditional web" only, but being fully Server oriented, can't we assume full compatibility with Mobile, Reactive & Service as well?
Thx!
Correct. All OutSystems server-side code runs the same. All of these projects can access these calls.
J.Ja
Thx for the answer, but most important, for such great component 👏
Don't know if that's possible, but will be great if Forge a component is compatible with multiple project types, it is properly reflected when filtering in the Forge component search. As per Mathutils, it only shows up when filtering for Web components (or All).
Not only is it only able to have 1 selected, it does not allow me to change what has been selected.
My strong suggestion - and I know it's neither intuitive nor what you would expect - is to NEVER use that filter when searching the Forge. I learned a long time ago that when you use it, you often do not get what you want/need, or miss good components because of this. :(
The problem is that my company has a policy not to use any Traditional Web components, so to avoid any incompabilities with ODC migration. Can't judge on that criteria, but this prevents me (and anyone in my company) to use this component if it's not flagged as Service....
A TWA module that only has server side logic, can be converted to a service module. If you do that at as part of your refactoring effort in O11 to migrate to ODC, you should be good to go.
A few points here:
1. This module contains an extension. To convert it, you would need to wrap the functionality in Service Actions. You still would have a difficult road to ODC with it because "extensions" and "external libraries" are very different in their implementations. I do not know if extensions will convert to ODC or not.
2. Due to the nature of service actions (as well as external libraries in ODC) - using REST calls - and the high volume of calls often sent to this extension, using it as service actions or external libraries in ODC is a very bad idea in many (most?) scenarios.
3. There was a ton of discussion during ODC's development around point #2, OutSystems agreed that performance was a concern, and built many of the functions in this component directly into the ODC platform. Before making any decisions on what to do (and I think simply wrapping extension code as service actions simply to comply with this mandate is the wrong idea and misinterprets the intent of the mandate, the simple fact is, this component needs to be completely re-written for ODC, not simply wrapped as a Service module and then upgraded), take a look at what math functions are built into ODC, compare it to the list of math functions you need; there is a very good chance that you will not need this component at all after the upgrade, so you can use this for now in O11, and then stop using it in ODC.
ah got it my comment was more generic, not knowing the details of your forge component.
Thanks for your replies and quite insightful technical details . I would then recommend the option keep the component as-is, and make another evaluation of options once the ODC migration is being planned.