|
Home > Archive > Microsoft Content Management Server > October 2004 > approval procedure
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
approval procedure
|
|
| choihead 2004-10-15, 9:13 pm |
| as far as I know, there is 1 level of approval procedure right??
but My boss wants 2 levels of approval procedure. So except working on the
hooks file, ( I know it's rather difficult), is there any other method
easier??
like for example, Author only save the page, Author read it then submit and
the moderator approve it, is it possible and workable?? do I make my
approach clear??
| |
| Cédric Dardenne 2004-10-15, 9:13 pm |
| Hi choihead,
MS sold us during a commercial presentation 2 levels of approval, so we had
to do so for the client too... :-)
You have 2 parallel approval procedures each having one level:
- For content: Author -> Editor
- For properties: Author/Editor -> Moderator
So to achieve a two level approval you can ensure (as Stefan tiped in an old
post) to always to a property modification, this way you will ensure to
always have:
Author -> Editor -> Moderator.
What we do is hooking on approved event, and then take current value of
page's Hide property, set it to the opposite, reset it to the real value,
and this is done.
The only issue this way is that a moderator has not rights to approve
content, so if he modifies the content, editor will have to validate his
modification.
HTH,
Cédric
--
Programming today is a race between software engineers
striving to build bigger and better idiot-proof programs,
and the Universe trying to produce bigger and better idiots.
So far, the Universe is winning.
-- Rich Cook
choihead wrote:
> as far as I know, there is 1 level of approval procedure right??
>
> but My boss wants 2 levels of approval procedure. So except working on
> the hooks file, ( I know it's rather difficult), is there any other method
> easier??
> like for example, Author only save the page, Author read it then submit
> and the moderator approve it, is it possible and workable?? do I make my
> approach clear??
| |
| choihead 2004-10-15, 9:13 pm |
| thx for your reply, but I am a new biw on MCMS(I just touched it not more
than 1 month, so I dun quite understand the below meaning, can u further
explain to me please???
"What we do is hooking on approved event, and then take current value of
page's Hide property, set it to the opposite, reset it to the real value,
and this is done."
"Cédric Dardenne" <cedric.nospam_dardenne@accenture.com> ¦b¶l¥ó
news:eK4VmxCsEHA.1816@TK2MSFTNGP15.phx.gbl ¤¤¼¶¼g...
> Hi choihead,
>
> MS sold us during a commercial presentation 2 levels of approval, so we
had
> to do so for the client too... :-)
> You have 2 parallel approval procedures each having one level:
> - For content: Author -> Editor
> - For properties: Author/Editor -> Moderator
>
> So to achieve a two level approval you can ensure (as Stefan tiped in an
old
> post) to always to a property modification, this way you will ensure to
> always have:
> Author -> Editor -> Moderator.
>
> What we do is hooking on approved event, and then take current value of
> page's Hide property, set it to the opposite, reset it to the real value,
> and this is done.
>
> The only issue this way is that a moderator has not rights to approve
> content, so if he modifies the content, editor will have to validate his
> modification.
>
> HTH,
>
> Cédric
>
> --
> programming today is a race between software engineers
> striving to build bigger and better idiot-proof programs,
> and the Universe trying to produce bigger and better idiots.
> So far, the Universe is winning.
> -- Rich Cook
>
>
> choihead wrote:
method[vbcol=seagreen]
>
>
| |
| Cédric Dardenne 2004-10-15, 9:13 pm |
| Concerning Workflow events hooks, you can look at "cutomizing the publishing
workflow" seciton in MCMS documentation.
Basically, this means that each time a posting is approved, you will change
one of its property programatically (Hide property in my example) for
enforce the posting to be approved by a Moderator.
Events handlers are declares in global.asax.cs file, and look like this:
public void CmsPosting_Creating( Object sender, CreatingEventArgs e )
{
if( e is PostingCreatingEventArgs )
{
// typecast e to PostingCreatingEventArgs
PostingCreatingEventArgs postingCreatingArgs = e as
PostingCreatingEventArgs;
// if the action is create new posting
if( postingCreatingArgs.CreateAction == CreateAction.New )
{
Template sourceTemplate = postingCreatingArgs.Template;
// todo: logic based on the template
}
}
}
Does this make more sense?
Cédric
--
Programming today is a race between software engineers
striving to build bigger and better idiot-proof programs,
and the Universe trying to produce bigger and better idiots.
So far, the Universe is winning.
-- Rich Cook
choihead wrote:[vbcol=seagreen]
> thx for your reply, but I am a new biw on MCMS(I just touched it not more
> than 1 month, so I dun quite understand the below meaning, can u further
> explain to me please???
>
>
> "What we do is hooking on approved event, and then take current value of
> page's Hide property, set it to the opposite, reset it to the real value,
> and this is done."
>
>
> "Cédric Dardenne" <cedric.nospam_dardenne@accenture.com> ¦b¶l¥ó
> news:eK4VmxCsEHA.1816@TK2MSFTNGP15.phx.gbl ¤¤¼¶¼g...
| |
| Stefan [MSFT] 2004-10-15, 9:13 pm |
| Just to add (as I was quoted before): Using Moderator approval will always
move the page out of production.
This means if you update a posting there will be no live version until the
approve is done!
A solution for this would be to integrated one of the following workflow
engines:
www.teamplate.com
www.k2workflow.com/
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Cédric Dardenne" <cedric.nospam_dardenne@accenture.com> wrote in message
news:OSYdObDsEHA.2684@TK2MSFTNGP12.phx.gbl...
> Concerning Workflow events hooks, you can look at "cutomizing the
publishing
> workflow" seciton in MCMS documentation.
>
> Basically, this means that each time a posting is approved, you will
change
> one of its property programatically (Hide property in my example) for
> enforce the posting to be approved by a Moderator.
>
> Events handlers are declares in global.asax.cs file, and look like this:
>
> public void CmsPosting_Creating( Object sender, CreatingEventArgs e )
> {
> if( e is PostingCreatingEventArgs )
> {
> // typecast e to PostingCreatingEventArgs
> PostingCreatingEventArgs postingCreatingArgs = e as
> PostingCreatingEventArgs;
> // if the action is create new posting
> if( postingCreatingArgs.CreateAction == CreateAction.New )
> {
> Template sourceTemplate = postingCreatingArgs.Template;
> // todo: logic based on the template
> }
> }
> }
>
> Does this make more sense?
>
> Cédric
>
>
> --
> programming today is a race between software engineers
> striving to build bigger and better idiot-proof programs,
> and the Universe trying to produce bigger and better idiots.
> So far, the Universe is winning.
> -- Rich Cook
>
>
> choihead wrote:
more[vbcol=seagreen]
value,[vbcol=seagreen]
an[vbcol=seagreen]
ensure[vbcol=seagreen]
value,[vbcol=seagreen]
his[vbcol=seagreen]
on[vbcol=seagreen]
submit[vbcol=seagreen]
my[vbcol=seagreen]
>
>
|
|
|
|
|