I have not seen the URL returned when attempting to set the context (I could not find it in the code either). Can you double check if item 4 in this picture is really correct?
Related comment ... from the reading, it's not really clear to me how an app developer might use the "set context" portion of the flow. Watson Workspace Clients (e.g. the web client) does determine, as the article explains, how and where (in the UI) to expose access to certain actions. The typical app developer won't be doing that, will they? (If so, maybe an example on how that might look would help ... if not, maybe simplify the diagrams to focus on what's available to app developers?)
I have not seen the URL returned when attempting to set the context (I could not find it in the code either). Can you double check if item 4 in this picture is really correct?
Related comment ... from the reading, it's not really clear to me how an app developer might use the "set context" portion of the flow. Watson Workspace Clients (e.g. the web client) does determine, as the article explains, how and where (in the UI) to expose access to certain actions. The typical app developer won't be doing that, will they? (If so, maybe an example on how that might look would help ... if not, maybe simplify the diagrams to focus on what's available to app developers?)