Okay, that's a compromise that, in my precise case, wouldn't work badly
at all though I think pre-creating optional properties might find an
application. But, my idea might also be the "camel's nose under the
tent" in other ways and make a muck of the interface. Thank you for this
suggestion!
Russ
On 04/27/2017 08:10 AM, Joe Witt wrote:
Russ,
I'd recommend having some highly common examples as optional
properties and then use docs to describe how they can add additional
ones of the same naming pattern, etc.. The purpose and tooling around
dynamic properties isnt' really meant that they'd be added by default.
But optional properties are a thing and should get you there.
Thanks
On Thu, Apr 27, 2017 at 9:54 AM, Russell Bateman <[email protected]> wrote:
Is there a way to prepopulate dynamic properties in a custom processor?
I'm writing a new processor and my users could benefit from some suggested,
in most cases it would be spot-on, configuration. Being able to prepopulate
dynamic properties that could be amended or deleted seems the best way.
Incidentally, the configuration I'm talking about was to have been done via
dynamic properties anyway.
Yes, I could resort to additional details, but my guys are in a hurry when
they use this, so cutting and pasting doesn't seem like the best help I
could give if it's possible to do what I'm asking.
Thanks,
Russ
