Skip to Content (Press Enter)
2021-03-19 09-32-13
Soren Staun
98Views
2Comments
[IdP] AO reduction for this component?
Question
Forge
Traditional Web
idp
Web icon
IdP (O11)
Forge asset by João Barata
Application Type
Traditional Web

Hello,

We're using IdP in production, but the cost of 41 Application  Objects is quite a big cost for "just" providing SSO. Is there any chance you could look at reducing the AO imprint of this component? Alternatively, is there a smaller subset of IdP components that can replace the big one?

Thanks in advance,

Søren

2
0
02 Aug 2022
Copy Link
2022-05-19 19-10-01
felipe.castilla

I'm reviewing this situation iwth my clients. 41 AOs I understand is because the backoffice, but maybe we can reduce the screens or something.

any one have a idea to resolve it or reduce this number? 

3
0
24 Apr 2024
Copy Link
2021-03-19 09-32-13
Soren Staun
  • Reduce number of screens
  • Remove screens and turn them into tabs on same screen
  • Turn screens into popups (that cost 0 AO)
  • Remove static entities (the price for a static entity is way too high in OutSystems)
  • Collapse static entities into fewer or none (might slightly reduce the "readbility" of your design, but can save a lot of of AOs) - often you can use the same static entity in place of 10 different ones
  • Collapse several tables into fewer tables

Yes, some of these things might break OutSystems design guidelines, but they also actively refused to reconsider the price of Static Entities being = 1 AO, so.. well. There it is.

2
0
25 Apr 2024
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.