Hi,
I have made a flowchart that calls an API, gets a result, creates a record of type Task and then relates this task to a Meeting. The flowchart is activated with a button action in a Workflow for the Meeting entity. When I press the button, the relationship is created and shows directly in a bottom panel of the Meeting Record. This flowchart calls an external API which sometimes takes too long to respond, so I want to make this asynchronous.
Therefor, I have changed the workflow. When the user presses the button, it now creates a record of type Query (in a flowchart). It relates the query record to the entity record. The API is then called. The API will use the EspoCRM API to update the Query record with the query result. I then have a workflow on entity Query that listens to updates on Query records. When it detects that a Query is updated related to a Meeting record, it executes a formula script. The formula script then creates the Task records and relates them to the Meeting record.
So both setups create Tasks and relate them to Meeting.
However the difference is:
1. The first workflow updates the Tasks in the bottom panel when I trigger the button action (however when the API request times out, it fails to create tasks)
2. The second workflow doesn't update the Tasks in the bottom panel. I need to refresh the page to see the tasks.
This is not really great for user experience. Is there a way in the asynchronous setup (2) to also auto refresh the bottom panel when records are related?
I already have a websocket connection.
I have made a flowchart that calls an API, gets a result, creates a record of type Task and then relates this task to a Meeting. The flowchart is activated with a button action in a Workflow for the Meeting entity. When I press the button, the relationship is created and shows directly in a bottom panel of the Meeting Record. This flowchart calls an external API which sometimes takes too long to respond, so I want to make this asynchronous.
Therefor, I have changed the workflow. When the user presses the button, it now creates a record of type Query (in a flowchart). It relates the query record to the entity record. The API is then called. The API will use the EspoCRM API to update the Query record with the query result. I then have a workflow on entity Query that listens to updates on Query records. When it detects that a Query is updated related to a Meeting record, it executes a formula script. The formula script then creates the Task records and relates them to the Meeting record.
So both setups create Tasks and relate them to Meeting.
However the difference is:
1. The first workflow updates the Tasks in the bottom panel when I trigger the button action (however when the API request times out, it fails to create tasks)
2. The second workflow doesn't update the Tasks in the bottom panel. I need to refresh the page to see the tasks.
This is not really great for user experience. Is there a way in the asynchronous setup (2) to also auto refresh the bottom panel when records are related?
I already have a websocket connection.

Comment