Fetching data via event

RE: Fetching data via event

Harsha Sharma — Mon, 24 Feb 2020 06:15:46 GMT

In that case, say process A is the process that saves leave request data to DB and status as Pending. Then Process B be the process where task is generated for supervisor to accept/reject the task.

If I understood your scenario correctly,in order to achieve the expected functionality you need to have the primary key (that you get after saving the data in process A) or the entire cdt containing data of the request passed in to the process B. Using this requestId you can query the db data in process B and pass that data to the UI node. On click of approve or reject button by the supervisor, save appropriate data in the status field of the request cdt. After the node, add write to db node with same primary key value, so that it updates the existing record with correct status.

Hope this helps.

RE: Fetching data via event

rahulm — Fri, 21 Feb 2020 19:12:18 GMT

I am saving information for the request leave in DB with status field pending. So when user see in record he can see status pending. when supervisor log-in and see the task for approval or reject along with request info.When he approves/rejects it ,it's again saved with status approved. It is done to separate a single process in two different processes as single process might not end if supervisor delays his action.

RE: Fetching data via event

Harsha Sharma — Fri, 21 Feb 2020 19:03:41 GMT

Can you help me understand your case better as in why wait to save the data until user clicks on task? You can simply write the required data to db as and when you have data. Then query that and display on the task UI.