Start a workflow from editing an asset
We are able to associate a workflow to an asset factory.
The workflow starts fine on initial use of this asset.
What we need is at any time this asset is now edited, a workflow is started.
The asset in question is a data definition associated to a block.
Again, the workflow will fire on initial asset creation, but DOES NOT fire once editing this asset.
This is a MUST have, or else the workflows are completely useless.
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tim on 14 Jun, 2013 06:15 PM
Hi,
By definition, I believe Workflows assigned to Asset Factories only fire on creation of assets. What you should be able to do is edit the Workflow in question, enable the 'Edit' Workflow Type (in addition to the 'Create'), then assign the Workflow to the Folder where your Data Definition Blocks are being stored in the system. Since the Workflow is now marked as an 'Edit' Workflow as well, any edits to assets underneath the Folder where this Workflow is assigned will trigger the Workflow (assuming that Workflow is required and the User doesn't have the ability to bypass Workflows).
Let me know if this helps at all.
2 Posted by tthomas on 14 Jun, 2013 06:36 PM
Thanks for the reply, but that was of no use.
Here is how our site is working:
1) Data defs created
2) Base Asset Block created with relationship to the data def
(These items above are in a common site)
3) Asset Factories created for each site - linked to the base assets
4) These new "assets" can be included in any folder at anytime, associated to particular regions on the template by us if/when needed.
5) only a select few of these base assets requires the workflow fired on edit ONLY.
We originally setup the sites/bl;ocks etc... so when a user decides to make an edit, that is when we want the workflow to be triggered.
Assigning to asset factory works on creation, but is of no use as we create these and bypass because we are admin.
We want to have the assets that we specify use the workflow on edit.
These assets are stored in any folder we need to drop them in.
We don't want pages etc.. that are not associated to the asset to trigger a workflow, just the specific assets.
Support Staff 3 Posted by Tim on 17 Jun, 2013 02:01 PM
I see. It seems like the main issues here are that the Block assets can be created in any Folder throughout the Site(s). Because of this, setting a Workflow at the Folder level - while it could be limited to a specific Group of Users - would require that any type of asset in that Folder go through that Edit Workflow (which you don't want at this time).
I checked our Idea Exchange for features related to the behavior you described in your initial description and found this idea. Surprisingly, it only had 1 vote. I went ahead and voted for it as I do believe there are specific use cases where it could come in handy (such as what you've described here). I sent you an invite to the Idea Exchange and I encourage you to vote/comment on that particular idea as well. If you have others in your organization that need access to the Idea Exchange, please send a list of those email addresses in a private discussion here and I can invite them. That way they can add their votes as well.
4 Posted by tthomas on 17 Jun, 2013 02:14 PM
Thanks for the invite.
I voted for this and left a comment.
Support Staff 5 Posted by Tim on 17 Jun, 2013 03:55 PM
Perfect. Thanks for the update! Have a good one.
Tim closed this discussion on 17 Jun, 2013 03:55 PM.