You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #63 let's start with a simple Component for showing one Indicator in a Flow. Pass in the CMDT Name for the Indicator, and show one Indicator.
The text was updated successfully, but these errors were encountered:
OK I've given up on this for now... I was able to create a simple indicator that was not record aware... that worked, but it defeats the purpose of the CMDT setup completely. I tried to make the Bundle Flow Aware but I could not work out how to get the recordId from the Flow into the Apex. So I'm not sure of the value of this at all now, so I'm putting it to future and discussion.
An idea that has come to me is if we design a version that instead of using the component's record context, we can create a special version for a Flow that creates either:
Dynamic SOQL to retrieve the data it needs using just a record id to render the Indicators.
Accepts a record variable and can the render the Indicators.
It would of course need other inputs, such as the Bundle itself.
Similar to #63 let's start with a simple Component for showing one Indicator in a Flow. Pass in the CMDT Name for the Indicator, and show one Indicator.
The text was updated successfully, but these errors were encountered: