tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/14851-start-a-workflow-from-editing-an-assetCascade CMS: Discussion 2013-08-19T21:26:23Ztag:help-archives.hannonhill.com,2010-02-09:Comment/273263762013-06-14T18:15:32Z2013-06-14T18:15:32ZStart a workflow from editing an asset<div><p>Hi,</p>
<p>By definition, I believe <a href=
"http://hannonhill.com/kb/Workflow/#assigning-workflows">Workflows
assigned to Asset Factories</a> 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).</p>
<p>Let me know if this helps at all.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/273263762013-06-14T18:36:14Z2013-06-14T18:36:14ZStart a workflow from editing an asset<div><p>Thanks for the reply, but that was of no use.</p>
<p>Here is how our site is working:</p>
<p>1) Data defs created<br>
2) Base Asset Block created with relationship to the data def</p>
<p>(These items above are in a common site)</p>
<p>3) Asset Factories created for each site - linked to the base
assets<br>
4) These new "assets" can be included in any folder at anytime,
associated to particular regions on the template by us if/when
needed.<br>
5) only a select few of these base assets requires the workflow
fired on edit ONLY.</p>
<p>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.</p>
<p>Assigning to asset factory works on creation, but is of no use
as we create these and bypass because we are admin.</p>
<p>We want to have the assets that we specify use the workflow on
edit.</p>
<p>These assets are stored in any folder we need to drop them
in.</p>
<p>We don't want pages etc.. that are not associated to the asset
to trigger a workflow, just the specific assets.</p></div>tthomastag:help-archives.hannonhill.com,2010-02-09:Comment/273263762013-06-17T14:01:28Z2013-06-17T15:50:15ZStart a workflow from editing an asset<div><p>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).</p>
<p>I checked our Idea Exchange for features related to the behavior
you described in your initial description and found <a href=
"http://ideas.hannonhill.com/forums/52559-cascade-ideas/suggestions/1028093-asset-level-workflow">
this idea</a>. 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.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/273263762013-06-17T14:14:54Z2013-06-17T14:14:54ZStart a workflow from editing an asset<div><p>Thanks for the invite.</p>
<p>I voted for this and left a comment.</p></div>tthomastag:help-archives.hannonhill.com,2010-02-09:Comment/273263762013-06-17T15:55:25Z2013-06-17T15:55:25ZStart a workflow from editing an asset<div><p>Perfect. Thanks for the update! Have a good one.</p></div>Tim