Call a process from a GET Web API

RE: Call a process from a GET Web API

Madhu RK — Thu, 12 Oct 2023 01:29:02 GMT

Yes we can call write the data store entity and start a process one in another in the Web API something like below

 a!writeToDataStoreEntity(
        dataStoreEntity: cons!DSE_NAME,
        valueToStore: local!constructRequest,
        onSuccess: a!startProcess(
          processModel: cons!PM_NAME,
          processParameters: {
            inputJason: a!toJson({ aa: fv!storedValues })
          },
          onSuccess: a!httpResponse(
            statusCode: 200,
            headers: {
              a!httpHeader(
                name: "Content-Type",
                value: "application/json"
              )
            },
            body: a!toJson({ aa: fv!storedValues, bb: fv!processInfo })
          ),
          onError: a!httpResponse(
            statusCode: 500,
            headers: {
              a!httpHeader(
                name: "Content-Type",
                value: "application/json"
              )
            },
            body: a!toJson(
              {
                error: "There was an error starting the process"
              }
            )
          )
        ),
        onError: a!httpResponse(
          statusCode: 500,
          headers: {
            a!httpHeader(
              name: "Content-Type",
              value: "application/json"
            )
          },
          body: a!toJson(
            {
              error: "There was an error writing to the data store"
            }
          )
        )
      )

RE: Call a process from a GET Web API

paulc919 — Fri, 30 Nov 2018 11:58:50 GMT

Hi ... I think the JBOSS / TOMCAT access log (18.3 and higher for TOMCAT) will register the webAPI calls - not sure if that will include parameters or not though. You could try checking that access log in the root directory of the logs to see if it contains the information you need.

RE: Call a process from a GET Web API

susanan0001 — Fri, 30 Nov 2018 08:37:43 GMT

Thank you both for your answers!

The problem of the a!startprocess() is that 1) it's asynchronous and 2) I can't pass values out of the process for the a!httpResponse().
I was trying to do both things separately inside the Web API, because I need to give a response (ex: calculate something, get/post client data) and to log the request.
Should I try a different approach? For example, trying to retrieve the information from the Appian Logs?

Regards
Susana

RE: Call a process from a GET Web API

aloks0189 — Fri, 30 Nov 2018 03:41:02 GMT

Hi susanan0001 as per my understanding, you need to change your implementation approach a bit.

Instead of calling two smart service functions together, (while working with POST/PUT/DELETE but not GET API methods) try calling a!startprocess() which will trigger the target process model, pass necessary information as it's parameter and persist the data into the DB using Write to Data Store Entity Smart Service and then call the actual process, which you were trying to invoke.

Hope this will help.

RE: Call a process from a GET Web API

Josh — Thu, 29 Nov 2018 18:35:52 GMT

1) You can't call smart services with GET API's, only POST/PUT/DELETE methods will allow you to launch a smart service.

2) Could you pass in the log info to the process and write to the data store inside of your process instance? To get around having to put this DSE node for the Web API log in each process you will invoke, you could create a pass-through process model that writes to the DSE and then invokes the start process node to start the relevant process model.