Skip to main content
Solved

Subroutine not exposed as API (SF)

  • November 5, 2024
  • 4 replies
  • 36 views

Freddy
Forum|alt.badge.img+16
  • Thinkwise Local Partner Brasil
  • 533 replies

Hi, 

Following the documentation I should be able to call this subroutine via API when the API checkbox is on. This returns 404.  https://base_url/indicium/sf/app_id/ocr_result_klippa

What am I missing?

 

 

Best answer by Mark Jongeling

Well, I did manage to do it:

Steps I did:

  • Subroutine with API + Alias like you have shown
  • Control procedure and template linked to program objects
  • Deployed on DB
  • Do a POST request to Indicium on my SF and my Runtime configuration

Are you sure it is the correct Indicium? I'm guessing at this point.

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

4 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Freddy,

Is your runtime configuration active? If you do a GET on "https://base_url/indicium/sf/app_id/”, does that result in the model + branch being shown?


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • 533 replies
  • November 5, 2024
Mark Jongeling wrote:

Hi Freddy,

Is your runtime configuration active? If you do a GET on "https://base_url/indicium/sf/app_id/”, does that result in the model + branch being shown?

Yes, also /openapi gives the options.. but it doesn't contain this procedure.. 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • Answer
  • November 5, 2024

Well, I did manage to do it:

Steps I did:

  • Subroutine with API + Alias like you have shown
  • Control procedure and template linked to program objects
  • Deployed on DB
  • Do a POST request to Indicium on my SF and my Runtime configuration

Are you sure it is the correct Indicium? I'm guessing at this point.


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • 533 replies
  • November 5, 2024

The trick was the api alias on the procedure I guess, after creating the model once again it worked.. 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings