You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to create a Submission when another plugin (Formie) creates a Draft within a given Section.
Based on what I've found in Workflow's logic, it's pretty tightly-coupled to a CP Request and its POST data on the Entry Detail page.
Is there an existing method of creating a Submission when a Draft is created by something that isn't a person? (i.e. plugins creating Drafts, mainly)
What's your proposed solution?
Based on what I've seen in the plugin, it's not currently possible, given the tight coupling I mentioned. (I'm hopeful that it's simply user-error and I'm missing something obvious!)
Additional context
No response
The text was updated successfully, but these errors were encountered:
You'd be correct in that Workflow is specific to Entries, and there's no immediate plans to expand that to other elements. And it's also tied to that "traditional" method of submitting a draft, either in the control panel or the front-end.
This is mostly because we require some form of user interaction to create a Workflow submission, to kick off the review lifecycle. There's nothing really like that for programatic drafts. So there's not really an existing method for you to use.
What are you trying to do?
I'm attempting to create a Submission when another plugin (Formie) creates a Draft within a given Section.
Based on what I've found in Workflow's logic, it's pretty tightly-coupled to a CP Request and its POST data on the Entry Detail page.
Is there an existing method of creating a Submission when a Draft is created by something that isn't a person? (i.e. plugins creating Drafts, mainly)
What's your proposed solution?
Based on what I've seen in the plugin, it's not currently possible, given the tight coupling I mentioned. (I'm hopeful that it's simply user-error and I'm missing something obvious!)
Additional context
No response
The text was updated successfully, but these errors were encountered: