Hi,
I can check the path of the content page in the xml file by writing the
following code:
<if test="true == ${call:matches('${field:path}','/home/.*')}">
<activation />
</if>
The above code worked for me.
Likewise, Can't I check the template on whish the page is based on writing
something like the following?
<if test="true == ${call:matches('${field:template}','Template1')}">
<activation />
</if>
I tried with writing the above code, so that when the workflow is invoked,
the pages that are based on "Template1" are activated only.
But it didn't work.
Can't we do something like this, so that we can check on which template the
page is based on in the xml itself?
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ralf Hirning
Sent: Wednesday, February 11, 2009 5:16 PM
To: Magnolia User-List
Subject: Re: [magnolia-user] Workflow Queries
Hi,
You could create a command which saves the workflow state in the page.
Then add this command to the workflow definition whenever the state changes
Ralf
Jan Haderka schrieb:
> On Wed, 2009-02-11 at 14:19 +0530, Sandipan karmakar wrote:
>
>> Hi all,
>> I have installed the workflow module and the "activation" workflow is
>> working fine. As per the "activation" workflow when a content page (say,
>> /page1/subpage1 ) is activated, the work item goes to the next group,
i.e.
>> publisher. Now is there any way to display a status in the "website"
tab,
>> that the content page (here, /page1/subpage1) is currently traversing a
>> workflow. Because if the user can't get this information then he may
again
>> activate this page and the page will again enter the workflow, though the
>> content page was already in the workflow because of the earlier
activation.
>>
>
> The common solution for this is to add e-mail notification to the
> workflow so the editor gets an e-mail as soon as he/she starts the
> workflow.
> If you really want to display different icon (or add a column) for the
> page while it is being activated, you have to extend
> WebsiteTreeConfiguration to do so and then specify it
> at /modules/adminInterface/trees/website/configurationClass.
> The few problems, i can think of right now, you would have to solve if
> doing so are:
> - not all users have rights to see content of workflow related
> repositories, as it is not needed to invoke the workflow.
> - depending on what you really want to display you might also have to
> take care of the fact that certain items can be already approved, but
> not yet published, because their publishing time is set for the future
> (or they are already published, but workflow is still running since
> there was expiration date set for given page)
>
>
>> And one more query, I tried to invoke the workflow depending on the
content
>> hierarchy the work item belongs to and it went successful.
>>
>> <if
>> test="true ==
>> ${call:matches('${field:path}','/home/.*')}">
>> <activate /
>> </if>
>> In the above snippet I was checking the path of the work item.
>> Now is it possible to activate a page depending on which template the
page
>> is based on?
>> For example,
>>
>> Say I have two pages,
>>
>> /Page1/subpage1
>>
>> Where "page1" is based on "Template1" and "subpage1" is based on
>> "Template2". Now I want to invoke the workflow only when the pages based
on
>> "Template2" are activated.
>> How can I do so?
>>
>
>
> The template information is stored in the MetaData subnode of the content
as mgnl:template
> property. Perhaps best way to deal with it is to encapsulate search for
template in question
> in separate command and add such command to the sequence of operations
executed as part of
> the workflow. Look at activation command implementation for an example of
how to implement
> the command.
>
> HTH,
> Jan
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>
>
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
