Timeline for Automate or simplify post-install steps for Packaged Flows
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2023 at 15:23 | vote | accept | Robert Sösemann | ||
| Feb 20, 2023 at 17:46 | comment | added | Phil W |
We have flows that are successfully packaged accessing Custom Settings. For example, a flow formula might include {!$Setup.namespace__Settings_Name__c.namespace__Settings_Field__c} to get a value. No fake values here. First class usage of custom setting fields in flow formulae.
|
|
| Feb 20, 2023 at 17:30 | comment | added | Robert Sösemann | When I have references like that I get errors during package creation: We can't find an action with the name and action type that you specified. I need a mechanism to decouple this. Fake values until a customs getting exists | |
| Feb 18, 2023 at 0:16 | history | became hot network question | |||
| Feb 17, 2023 at 20:47 | answer | added | Jaswinder | timeline score: 2 | |
| Feb 17, 2023 at 18:01 | answer | added | Rob Davis | timeline score: 2 | |
| Feb 17, 2023 at 17:24 | comment | added | Phil W |
IIRC you can easily access custom settings via $Setup expressions in flow formulae. Probably similar for CMT?
|
|
| Feb 17, 2023 at 16:16 | history | asked | Robert Sösemann | CC BY-SA 4.0 |