nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Managing Editions

tirrudev

Hi,

We have a script which runs on a scheduled job daily.This publishes an edition daily.But for a particular branch "branch1" editions are published twice a year that is for every 6 months.As of now, our script deletes an edition considering number of editions in that branch..Say the number of editions should be not be greater than particular value "x". But If a user who has persmissions to create new edition from th GUI has published 5 editions in a 6 months period. Say If the value of "X" is 5..Then it deletes all the 5 editions.So we came to an approach to check the "age" of the edition and then check the number of editions.If the age of the dition is older than "6months" and the number of editions is greater than the maximum number of editions.Then delete the edition..Is this the correct approach?Can some please suggest a better approach....

Thanks in Advance...

Find more posts tagged with

Comments

nipper

This is the most convoltued post I have read.

Why not have you script ignore the branch with updates every 6 months ? Or have an oldest edition per branch setting and do not delete anything newer than that. Or do not create editions automatically and create/delete them manually.

5 Editions is barely useful, esp if you have daily updates. Is there a problem you are trying to solve by deleting the Editions ?

Jamik

or you could just write the script to only create an edition daily if there was an actual change made to facilitate the need for an edition. seems much simpler than the convoluted thing you are trying to do.

Really, if you want most control doing an edition creation manually is the best process. Otherwise, if you're going to do them automatically then simpler is better.

tirrudev

Thanks for the response...

Crsb

Thanks for the response...

How can we know if there was an actual change made? and then create a edition...

if you are using CLT iwpublish then there is a flag to only publish if changes were submitted to STAGING. I think the flag is -f but you can verify by looking up iwpublish CLT usage.

tirrudev

Thanks for the response...

I have refered to CLT manual..the -f option publishes the edition only if the changes were submitted to staging..Since the last edition

newpaperdefault.rptdesign

tirrudev

Hi,

I want to run a custom script when the user clicks "New Edition" link..Can some one please suggest...How can I do this?

Thanks in Advance...

Jamik

You can disable the ability for people in certain roles to create New Editions and then create a custom script that does a New Edition and runs your other script, then add that as a custom menu item. Check the TeamSite UI customization guide for info on that.

The other option which might be a better option is to set up a trigger job that runs anytime a new edition is published. Others can correct me if I'm wrong but you could have your custom script run after the new edition menu is called by using the iwatpub.ipl command. For more info on that look in the CLT guide for your given OS (unix or windows)

tirrudev

Thanks for the reposne...

I have tried registering the event as below:

iwat PublishStagingArea

\Interwoven\Teamsite\scripts\custom.ipl -p

After this I have listed using iwlsat.exe
ID: 30754 "PublishStagingArea"

\Interwoven\Teamsitscripts\custom.ipl

But when I GO AND CLICK "New Edition" link..the custom script is not triggered..

Can someone suggest where am i going wrong? and is this the correct way to do?

ISCBorisB

you could have your custom script run after the new edition menu is called by using the iwatpub.ipl command

That's correct, you can. It is however much easier to configure and maintain using generic "iwat" with proper Event Regex

ISCBorisB

Thanks for the reposne...

I have tried registering the event as below:

iwat PublishStagingArea \Interwoven\Teamsite\scripts\custom.ipl -p

After this I have listed using iwlsat.exe
ID: 30754 "PublishStagingArea" \Interwoven\Teamsitscripts\custom.ipl

But when I GO AND CLICK "New Edition" link..the custom script is not triggered..

Can someone suggest where am i going wrong? and is this the correct way to do?

"iwat" Collection of tools intercepts "Post" Events. "I've clicked New Edition" is not an Event at all, not on the Server Side.
If configured correctly "iwat PublishStagingArea" will fire after iwserver publishes an Edition

Adam Stoller

I have tried registering the event as below:

iwat PublishStagingArea \Interwoven\Teamsite\scripts\custom.ipl -p
...
Can someone suggest where am i going wrong? and is this the correct way to do?

On Windows you need to supply the perl engine first - so first remove the trigger you have (using iwlsat and iwrmat) and then try this:

\> iwat PublishStagingArea "D:\Interwoven\TeamSite\iw-perl\bin\iwperl.exe \Interwoven\TeamSite\scripts\custom.ipl -p"

Then try publishing an edition and see if the script gets kicked off.

Note: I'm assuming you've already done:

\> iwperl -w -c \Interwoven\TeamSite\scripts\custom.ipl

to verify that there are no errors in the script itself.

tirrudev

Thanku very much...For the information Borris..&& ghoti

Now, I have understood that "iwat" intercepts post events...and we have to supply perl engine...

This is a perl script and not an ipl file..we are running this on a scheduled job with -s option and now i want to run this script with -p option for :"new edition"...

Now, I am changing the script to an "ipl".

Thanks in Advance...

tirrudev

Ghoti,

I tried to register by suppling an perl engine as below:


Diwat PublishStagingArea \Interwoven\TeamSite\iw-perl\bin\iwperl.exe \Interwoven\TeamSite\scripts\custom.ipl -p

But when i listed using iwlsat it gave me
ID: 30755 "PublishStagingArea"

\Interwoven\Teamsite\iw-perl.exe

Instead of listing an ipl file...

Thanks for the responses...

ISCBorisB

I tried to register by suppling an perl engine as below...

This is NOT the syntax provided by Ghoti. Try to read his post again - this time carefully.
Keep in mind that iwat takes 2(two) parameters, you've tried to register with 3(three)

tirrudev

Thanks for all your support and responses..

It worked now...after changing to the syntax provided by Ghoti...

SimplePageVariable.pdf

tirrudev

Hi,

Is at possible to trigger any events or run the scripts before the event...That is If the user click "New Edition" and says ok..If there are no changes sincle the last publish...He should be displayed with a message "Publishon" Failed because there are no updates since last publish...otherwise...With a message Successfully published an edition...

Thanks in Advance...

Adam Stoller

Hi,

Is at possible to trigger any events or run the scripts before the event...That is If the user click "New Edition" and says ok..If there are no changes sincle the last publish...He should be displayed with a message "Publishon" Failed because there are no updates since last publish...otherwise...With a message Successfully published an edition...

Thanks in Advance...

All iwat triggers are POST-operative.
If you want do something PRE-operative, you need to replace the OOTB functionality with a custom interface (as suggested by Jamik earlier in this thread)
If you want to catch a no-op with regard to publishing an edition, first you have to figure out if the event is thrown regardless of whether the edition is created. If it is, you might be able use tools like iwlasted and stat'ing the edition directory to see if it was just created. If the event isn't thrown you're back to having to design your own custom UI to replace the OOTB UI.