Non-Persistence and Widget Use

I'm looking for someone who can explain the limitation on using non-persistent entities with widgets. Specifically, what are the issues with using the isPath attribute on an entity that is non-persistent (or your inability to do so). For example, if you try to use the input reference selectors, the context passed to the object cannot be non-persistent - even if you set allowNonPersistableEntities. A normal Microflow operation would allow you to retrieve the data via association, so I am assuming it has something to do with client-side limitations. Can anyone expound?
0 answers