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; } } }

Edit Submitted file before it goes to STAGING

raeovine

I have a SitePublisher HTML file that my content contributors will submit when ready. I have a custom script set up in the iwlocal.cfg configuration file which will execute a special program that will rewrite URLs in the html file on the submit event.

What I am noticing is that it looks like the submitted file is ending up in the STAGING area before my script edits the file. I see my edits in the file that exists in WORKAREA, but STAGING has the file without applying my script to it. The WORKAREA file is showing as edited after the submit (pencil icon)

I am not using workflows.

Find more posts tagged with

Comments

vpatel

I have a custom script set up in the iwlocal.cfg configuration file which will execute a special program that will rewrite URLs in the html file on the submit event.

How you are doing this? Post your files/scripts/configs.

raeovine

I have the following in my iwlocal.cfg
iwatsub root /app/teamsite/httpd/iw-bin/NextGen/processDeploymentRequestStaging.sh '$IW_EVENTLINE'

In my shell script processDeploymentRequestStaging.sh, I execute a PERL script on the command line passing in the path to the HTML file
/app/teamsite/iw-perl/bin/iwperl /usr/local/adm/scripts/content/filereplacer.ipl /tsbranch/iwmnt/default/main/Microsite/BobURLTest/WORKAREA/shared/html/BobURLTest/MyTestDownload.html

I know if I run this command line outside of teamsite, it works as expected. It also works correctly if executed via the Teamsite environment. It just appears that the file goes to staging before my script is able to make edits to the file. Does anyone know the process sequence on a submit event?

nipper

That is a horrible implementation.

You have a trigger that says on the submit event (and it is on the event, not before the event and wait for this to complete) run this script. So the submit happens and the script runs just slightly after. Now depending on how the stars are aligned, you may see the changes in the submitted file, however it is not surprising that you see the results you are seeing.

How do you kick off the submit ? You say you are not using WF, so is this from the command line running iwsubmit ? You can write a wrapper around iwsubmit that calls your script first and then calls iwsubmit.

raeovine

The submit is triggered via the Teamsite UI submit button. Ideally, I would prefer to run the replacement script when the user selects to Generate HTML from the SitePublisher menu, but I was unable to find any documentation on how to intercept this event and run my script. Can I customize processing when the user selects Generate HTML instead?

nipper

The submit is triggered via the Teamsite UI submit button. Ideally, I would prefer to run the replacement script when the user selects to Generate HTML from the SitePublisher menu, but I was unable to find any documentation on how to intercept this event and run my script. Can I customize processing when the user selects Generate HTML instead?

OK, assuming you are not using a 8 year old copy of TeamSite, then you are using workflow, likely just not an approval process.

As of TeamSite 5.0 the submit button on the GUI kicks off a workflow, you just do not know it.

You are probably using the LiveSite Publish Content workflow (at least you should be using that). Does it pop up and ask about meta data?

You can add a task to that workflow (before the first deployment) that runs an external task which can be your perl script.

raeovine

Thanks nipper. Our teamsite environment has evolved from a legacy 5.x implementation, so we are still using some archaic methods. I will look to access the workflow running behind the scenes and report back. Your feedback is much appreciated.

vpatel

... I would prefer to run the replacement script when the user selects to Generate HTML from the SitePublisher menu ...

You are probably using the LiveSite Publish Content workflow (at least you should be using that). Does it pop up and ask about meta data?

You can add a task to that workflow (before the first deployment) that runs an external task which can be your perl script.

It seems like his users are using the SP menu item to Generate HTML first and then simply using the "Submit" WF to submit it to Staging. If they switch to PLC then your suggestion would work fine. If he wants to continue using the menu item + submit workflow (for whatever reason) then he needs to customize that menu item.

SP Generate HTML menu item is one of the core functions of that comes with SP. You shouldn't try to customize it as that type of solution is not maintainable through product updates. If you know TS/SP/LS/J2EE enough then you could create a custom menu item that'll do whatever processing that you need to do before the HTML generates and then just call the OOTB Generate HTML functionality. It is quite tricky from my personal experience.

Your use case is simple enough, customizing a WF would be easier option here. I have once attempted to customize the Generate HTML when it was absolutely necessary for my use case and like I said earlier it is quite tricky to get it to work.

My $0.02!

raeovine

That is a correct interpretation of our process vpatel. The users will generate the HTML from the .page file via the SitePublisher -> Generate HTML menu option. After generation, the will submit the HTML. We need to modify the HTML before the file gets to STAGING. It look like the only real option is to redesign the submit processing to use workflow

nipper

It look like the only real option is to redesign the submit processing to use workflow

You are incorrect. You are using a workflow, you just do not know it.

find the file $iwhome/local/config/wft/available_templates.cfg and post it and mention what branch you are working on. It is easy to find the workflow.

raeovine

Thanks again nipper. I did find the workflow - configurable_default_submit.wft. I am going to create a copy of this workflow and then add a step before the deploy step which will call my external application to massage the html file. Does that approach sound correct?

nipper

that works for me

raeovine

Thanks Nipper. You were right and I was using workflow. I have it mostly working ... I created an external task and then linked it into the workflow. I've confirmed that my external task is running when I submit (I can see the log created) but it doesn't look like the submit is happening after that because the file does not change in STAGING. I created the following task:

declare_task('html_cleanup',
name => "html_cleanup",
description => "modify links and urls in submitted HTML files for web deployment",
type => "externaltask",
owner => $iw_areaowner,
areavpath => $iw_workarea,
command => "$html_replacer",
variables => {
"ClassName" => "com.interwoven.ui.teamsite.workflow.task.urltask.DeployURLExternalTask",
"odDeploymentName" => $wft_config->get_value('deployment_name')
});

And then linked it into the workflow before the submit via the following:
link_tasks('conflictchk', 'html_cleanup', $done_label);
link_tasks('html_cleanup', 'submit', $done_label);
link_tasks('submit', 'deploy', $done_label);

Any ideas?

Adam Stoller

Thanks Nipper. You were right and I was using workflow. I have it mostly working ... I created an external task and then linked it into the workflow. I've confirmed that my external task is running when I submit (I can see the log created) but it doesn't look like the submit is happening after that because the file does not change in STAGING.
...
Any ideas?

Did you make sure that your externaltask performs a callback to tell the workflow to transition to the submittask?

raeovine

Thanks ghoti. I did not have the perl script send a callback.

I added the following lines to my script:
use TeamSite::CGI_lite;
# Callback to teamsite workflow to continue if there is a submit
my $cgi = new TeamSite::CGI_lite();
$cgi->iwcallback("success", "HTML paths replaced");

If I run the script from the command line, it outputs the following:
Content-type: text/html
[html]

<script language="javascript">
function handleOnLoad()
{
document.mainform.submit();
}
</script>

[/html]
Then, in my workflow, I've added the following to link the tasks together
link_tasks('conflictchk', 'html_cleanup', $done_label);
link_tasks('html_cleanup', 'submit', "success");
link_tasks('submit', 'deploy', $done_label);

However the submit still isn't happening - the STAGING file is not updated with the changes.

Adam Stoller

If you're using an externaltask - you don't want TeamSite::CGI_lite's iwcallback, you want TeamSite::WFtask's CallBack()

raeovine

Thanks ghoti - that fixed it. Much appreciated to all who assisted on this including nipper and vpatel.