Timeline for Dynamically render Screen Flow from Extensions in Flexipage of Base package
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2021 at 22:08 | vote | accept | Robert Sösemann | ||
| Oct 25, 2021 at 13:40 | answer | added | Robert Sösemann | timeline score: 3 | |
| Oct 25, 2021 at 8:57 | answer | added | Christian Menzinger | timeline score: 0 | |
| Oct 23, 2021 at 18:09 | history | edited | Robert Sösemann | CC BY-SA 4.0 | added 87 characters in body |
| Oct 23, 2021 at 11:40 | history | edited | Robert Sösemann | CC BY-SA 4.0 | edited title |
| Oct 23, 2021 at 9:40 | comment | added | Robert Sösemann | Not a 100% sure what you mean with bind but in my case extension packages are not really optional extensions. The BASE functionality only works with 1 or many extensions installed that implement the specifics of their types. So overriding is interesting (please put it into your answer if you create one) but not a hard requirement. | |
| Oct 23, 2021 at 1:21 | comment | added | Jeff Kranz | Does it have to bind to the Type__c field? I ask because packaged flows can now be "overridden" which means your base package could contain the object and base flow and however that flow is launched (embedded in flexipage, flow action, etc), then your extension package could simply override the base flow with its own flow. help.salesforce.com/apex/… | |
| Oct 22, 2021 at 22:30 | history | asked | Robert Sösemann | CC BY-SA 4.0 |