Expand my Community achievements bar.

SOLVED

Web service call to orchestration through reader

Avatar

Former Community Member

Hello,

I have a form where I want to do a lookup of values that are outputs on a given orchestration.  When I reader extend the form to allow web service calls, it works fine from Reader 9, but doesnt work when the Reader is opened in a browser window.  Is there something else needed to submit a web request from the browser based reader?

Also - I thought it was possible to make web service calls from a form without reader extending as long as your form was rendered via the reader in a browser window?

Thanks,

Jigster

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

There is nothing "special" you have to do to make it work from a browser .....it shoudl just work. Are you getting any errors? Could your browser be blocking the WS call?

For your second question .....you always have to Reader Extend for Web Service calls regardless of whether you are in Reader or a browser.

Paul

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

There is nothing "special" you have to do to make it work from a browser .....it shoudl just work. Are you getting any errors? Could your browser be blocking the WS call?

For your second question .....you always have to Reader Extend for Web Service calls regardless of whether you are in Reader or a browser.

Paul

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----