95
Views
1
Comments
[REST API] Best way to expose consumed Static Entities/Enums
Question

Hi,

When consuming a REST Service that has some ENUMS defined, these are translated(as far as I can tell), to in-memory static entities. 

This makes it troublesome to then consume as aggregates for, say, dropdown selections etc.. Are there any best-practices or solutions to use these?


RELATED:

https://www.outsystems.com/forums/discussion/61848/rest-api-swager-import-static-entity-enums-static-entity-identifier-types/


Thanks!


Nuno

TestsND2020IS.oml

Rank: #1944

I would be interested in an answer, just running into the same issue. 

One way to deal with it is to re-create the static entities, but this decouples the values from the service. If I am basing my app on the values of a services, I might want to control the possible values using the service.