>>> If REST service is getting bad request then service activity will not get called and how to log this request in to customized table?

• for both positive & negative paths
  • we have to capture the request & response in a page list (of class ServiceLog) for our analysis.
    • So create a page list of class org-data-ServiceLog holding the request and response values
      • this page list creation should be triggered based on DSS true-ness
    • we can either have the InteractionLog
      • under pyWorkPage or
      • can implement the same way how attachments are implements [LinkedTo and LinkedFrom]
        • So org-data-ServiceLog will be the table here with all the required properties
          • request
          • response
          • status, status code, desc, message
          • service name
          • workobject ID
          • interaction time
          • error code, description, additional notes, comments,
  • in failure scenario - the assignment is routed to either workbasket or administrator (other operator) using ticket rule.

Hi Ibrahim ,

We had a similar requirement and the approach we followed was to override the pyInvokeRestConnector to capture the raw response in a new parameter .In the 5th step of the activity you can include the below code.Once you do this you will have all the details on the parameter page and you can use an activity to get details from the parameter page and write it into a table.

  if (! (ignoreData || responseMap == null))

        {

            responseBody = responseMap.get("body");

          // CUSTOM CODE TO SET THE WEBSERVICE RESPONSE TO A PARAMETER ON PARAMETER PAGE

          tools.getParameterPage().putParamValue("MyRestResponse",responseBody.toString());

Thanks

Dinesh

where should I add this log message