How to refresh indicators from a workflow? They are disappearing.
Building a dashboard with web, I have an app initialize workflow - call this A - run to query all my data that update indicators and charts - this works great on the initial app load.
I have a button to open a modal that has a 2nd WF - call this B - to filter the indicators/charts to a new time range - all WF B is doing is presenting a form for range input, and on submit, trip WF A off with varying WF parameters.
After B trips A off, my dash gets new data and runs through the same commands to update indicators/charts. Charts update with the new data perfectly fine, indicators on the other hand completely disappear.
WF A is using kpi.display with the kpiCard and features parameters with the appropriate id and feature sets. This works fine on initial app load with WF A but for whatever reason is not after. I've verified that the kpi cards are getting new feature sets after WF B is ran, I've tried ui.activate on the kip cards, but no matter what I do they just disappear.
-
Hi Andrew,
Can you check the browser console to see if there are any errors displayed when the card disappears? What version of Web and Workflow are you currently seeing this with?
Thanks, Stefan
0 -
We are on 5.8.0 for Web and 5.17.0 for Workflow. No errors show in the console after WF B runs WF A with a new time frame.
For values and references in the kpi card config, I'm using arcade - loop to grab specific features for display - if that plays a role, I'm not sure. The kpi's are also hooked up to the initialize WF - not a map or anything.
kpi.display is being used with the kpiCard and features parameters to get them to load out, some things I've tried:
- kpi.clear before the kpi.display - Works on initial load, kpi's still disappear after data refresh.
- kpi.add-features before kpi.display. Works on initial load, kpi's still disappear after data refresh.
- ui.activate on all the elements the kpi's live in - still disappears.
0 -
Hi Andrew,
Would you be able to provide links or files for your app and workflow that are causing this issue? We have not been able to reproduce this yet.
There were a few updates and fixes to Workflow that might impact your scenario in Geocortex Web 5.10 and Geocortex Workflow 5.18.1; would you be able to upgrade and see if this resolves your issue?
Thanks, Stefan
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
3 kommentarer