We are attempting to use a JSON (Swagger 2.0) file to setup a REST service broker. The service instance is setup successfully but we only see 3 Service Operations.
Take one of them GET /form/v1/list - Inspecting this service operation in K2 Smart Object Explorer works as expected. We see the HTTP Response code & headers property and executing the method connects to the specified host and returns a response code
However, the method we really need is POST /form/v1/do-something and this does not generate a Service Operation. We attempted to navigate to the Object Type and create a smart object and when we execute the serialize method, it does the serialization but does not actually connect to the specified host. We even tried to add a operationID in the Swagger file but that did not help.
Again, some Object Types do have Operations listed from the Swagger but the vast majority simply have the standard Serialize, Deserialize, etc. built-in methods.
How can we get this working? How does the REST broker determine which object types are considered "executable" and hence adds a HTTP response code property and service operations? There doesn’t seem to be any difference between the GET/POST operations that work and those that do not. Seems random.
Thanks