Skip to Content (Press Enter)
UserImage.jpg
Sam Riggleman
40Views
4Comments
Solved
Will ODC support calling OS11 service actions?
Question
ODC

Currently I see the ability to read entities from OS11 in ODC, but we use service actions between our UI and data layer. From what I see, OS11 service actions still have to be wrapped with REST API's to expose to ODC? Is this correct? I thought at the ONE Conference last year it was mentioned that we can call OS11 service actions from ODC as well.


1
0
05 Mar
Copy Link
2021-10-07 11-27-07
Fernando Moitinho
Staff
Solution

Hello!

At this current stage of the platform interoperability journey, logic reuse between O11 and ODC relies exclusively on REST APIs. While using Service Actions might seem easier, they are not currently supported across platforms because Service Actions rely on several underlying mechanisms that are currently confined to a single environment.

Here is a breakdown of the technical enablers that are currently missing to allow Service Actions to operate between O11 and ODC:

  • Authentication & Infrastructure Boundaries: Service Actions are designed to be authenticated and used within the same O11 or ODC stage/environment. Currently, they cannot be used across different infrastructures.
  • End-User Session Context: A Service Action inherently carries the context of the end-user's session. At this point, the end-user session does not transit from one platform to the other.
  • Authorization & Governance: In O11, Lifetime governs which developers are authorized to reuse a specific Service Action. Between O11 and ODC, there is no parity or unified governance yet to verify if a developer on O11 is the exact same developer on ODC, meaning authorization cannot be enforced.
  • Logging: Service actions automatically log information such as who called the action. Currently, there is no centralized logging between O11 and ODC to accurately track these calls.


Future Outlook

Proper Service Action support requires the technical enablers that are coming in the next "platform unification" phase, where IT users and SSO are fully centralized. Having these foundational elements in place means that we can consider in the future supporting Service Actions sharing between O11 and ODC instances. Until these technical enablers are ready, REST APIs will remain the supported method for cross-platform logic reuse which we are shortly releasing specific capabilities which they will not count AOs when reused between O11 and ODC (bi-directionally).

See solution in context
3
0
06 Mar
Copy Link
2025-12-03 17-22-41
Lavanya Kamalaguru
AI Generated

Hi @Sam Riggleman ,

Yes, you are right, you still need to expose Outsystems11 service action as a REST API to consume them from ODC. Currently, ODC cannot directly consume Service Action from Outsystems 11 modules directly.

Please check the below documentation.

Asset consuming its own service action - OutSystems 11 Documentation 

O11 to ODC conversion patterns - OutSystems 11 Documentation

1
0
06 Mar
Copy Link
This answer was AI-generated. Please read it carefully and use the forums for clarifications
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP

Hi Sam,

I've asked OutSystems, and it seems indeed there's nothing on the roadmap for ODC and O11 to call each other's Service Actions. A bit of a missed opportunity if you ask me, so I hope they will add it. For now, using REST APIs is the only way. I just made an Idea based on your request, so vote it up and maybe OS will implement it :).

1
0
06 Mar
Copy Link
2021-10-07 11-27-07
Fernando Moitinho
Staff
Solution

Hello!

At this current stage of the platform interoperability journey, logic reuse between O11 and ODC relies exclusively on REST APIs. While using Service Actions might seem easier, they are not currently supported across platforms because Service Actions rely on several underlying mechanisms that are currently confined to a single environment.

Here is a breakdown of the technical enablers that are currently missing to allow Service Actions to operate between O11 and ODC:

  • Authentication & Infrastructure Boundaries: Service Actions are designed to be authenticated and used within the same O11 or ODC stage/environment. Currently, they cannot be used across different infrastructures.
  • End-User Session Context: A Service Action inherently carries the context of the end-user's session. At this point, the end-user session does not transit from one platform to the other.
  • Authorization & Governance: In O11, Lifetime governs which developers are authorized to reuse a specific Service Action. Between O11 and ODC, there is no parity or unified governance yet to verify if a developer on O11 is the exact same developer on ODC, meaning authorization cannot be enforced.
  • Logging: Service actions automatically log information such as who called the action. Currently, there is no centralized logging between O11 and ODC to accurately track these calls.


Future Outlook

Proper Service Action support requires the technical enablers that are coming in the next "platform unification" phase, where IT users and SSO are fully centralized. Having these foundational elements in place means that we can consider in the future supporting Service Actions sharing between O11 and ODC instances. Until these technical enablers are ready, REST APIs will remain the supported method for cross-platform logic reuse which we are shortly releasing specific capabilities which they will not count AOs when reused between O11 and ODC (bi-directionally).

3
0
06 Mar
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.