Default layout on email step when created through API
Through the API, when I create a workflow with an email step, the default layout is not set as the layout for that step. More technically, the step returns a _layoutId as null. A look at the source code confirms that behaviour as much as I could tell.
Is this what is expected/desired?
I have follow thoughts, but just want to confirm that first.
A general comment is that the Web client seems to overlay functionality/lifecycle management that I would have thought could/should be in the API. This makes it harder to understand particularly as I am trying to help maintain a client SDK (and looking to build a terraform provider).
Is this what is expected/desired?
I have follow thoughts, but just want to confirm that first.
A general comment is that the Web client seems to overlay functionality/lifecycle management that I would have thought could/should be in the API. This makes it harder to understand particularly as I am trying to help maintain a client SDK (and looking to build a terraform provider).
