Do I have to add PUBLIC properties to be passed to a deferred custom action as parameters to SecureCustomProperties?
It's been a while. Hope all had a great Holiday Season.
So, I have an immediate custom action, which runs from a UI button click and grabs a value from an XML file and sets a PUBLIC property to that value. I then want to run a custom action condition to run if the PUBLIC property has been populated or has a value and also pass the property to the widget as a parameter. Do I have to add this property to SecureCustomProperties?
The install runs elevated requiring Admin rights.
If I do have to add it to SecureCustomProperties, do I have to seed the PUBLIC property in the Property table (I will not set a value) or can I just add the Property name to SCP?
Any help appreciated.
I'm thinking I have to add to Property table, add to SCP, and then things will work.
Over the years I am often confused with using SCP or CustomActionData. I think in all the years I've been tasked with creating installs, I've only used CustomActionData a few times. The majority of install tasks just work or seem to work if added to SCP.
Thanks for any clarification, tips, etc.