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

detecting embedded dcuments

Priya_N

HI

Consider the following scenario

A user (author) generates a page and triggers a workflow ..Workflow also has a opendeploy component
which is used to deploy the file when approved.

only approved pages will be deployed to the deployment server. no other pages will e deployed. we achive this by writing the value of iw_file to a txt file and triggereing a file list deployment.

This works fine till the user embeds a document to the generated page.

Lets say the user generates a page called test.html ... with a embedded document in it(test.doc).
test.doc has been uploaded to the teamsite server so that test.html doesnt have a broken link.

now the workflow (value(iw_file) ) will return only test.html in other words the page that was generated. the html page will be deployed but not the document.
which will result in a broken link in the actual live server.

how do we get around this problem ?

Find more posts tagged with

Comments

Jeremy

Hi,

One idea would be to have an external task which will parse the attached DCR for any other files that my be linked to it - .jpg, .gif, .doc, .pdf etc. The external task will then attach those files to the workflow as well so that they too are deployed in the filelist deployment.

HTH

Jeremy

Priya_N

Hi
writing an perl file for parsing the file for jpg's doc's etc etc and invoking is an option,but I do feel this is something very much complicated for this task .

Anyone come across instances where this is done in a much simpler way ?

Adam Stoller

I'm not sure how you could do it in any simpler manner.
But to start with - how does "the user embed a document to the generated page" ?
If you can explain how that happens, then perhaps we can provide other ideas of how to track it so that it can be processed correctly in the workflow - otherwise you need to parse something to find the file references to use for adding the files to the workflow - and the DCR (*not* the generated page) is the best place to look for that information - and generally pretty easy to parse).

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Sunil Mugalavally

Hi,
You could consider storing all the embedded documents (comma seperated) as an extended attribute when you generate the file (html) from DCR.
You can have a script (workflow external task) that reads the extended attribute of the file and add the embedded documents to the filelist deployment.

-Sunil

Priya_N

HI

The term embedded gave a wrong meaning . what I intended was the user while generating the html (output) adds a link to a file which he uploads to the teamsite server.

Now lets say the generated page is generated.html he gives a link to say link.doc in generated.html. The user then uploads link.doc thru upload functionality in TS.

Now the workflow + opendeploy will deploy only the html (generated.html ) page and not the linked document(link.doc).

I guess the word embedded document gave a wrong meaning .

Adam Stoller

I had a feeling that was what you meant, in which case, you've already been given the answer - you need to parse the DCR to find the embedded reference to the other document(s) and, if they are located within TeamSite, add them to the task, so that they're part of the workflow process, and then they should automatically become part of the filelist generated for the OpenDeploy part of your workflow.
I'm not sure why you'd think there be a "simpler" way of doing it - parsing a DCR is not [usually] that difficult.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

webkicha

Yes. as fish said, all you need to do is attach the generated.html and link.doc files to workflow and submit it. It will automatically submit to staging and as well as submit to your production server using opendeploy.

-Kiran

neski

I've implemented something similar.

First I've creates a hidden field in the DCT which is gonna store every file attached to the dcr. This is done with formApi:


         //recursive function to parse items
 function parse_items(lista)
 {
               var resultados= new Array();
  for (var i=0; i<lista.length;i++)
  {
   var item = lista;
   listahija = item.getChildren();
   tipoitem = item.getType();
   valoritem = item.getValue();
   if(listahija != null)
   {
    var res2 = new Array();
    res2 = parse_items(listahija);
    concatenaArrays(resultados,res2);    
   }
   else if (tipoitem == "browser" && valoritem != "")
   {
    resultados.push(valoritem);
   }
  }
  return resultados;
 }

         //main function
 function get_files()
 {
  rootItems = IWDatacapture.getRootItems ();
  fileList= parse_items(rootItems);
  IWDatacapture.getItem("/hidden/file_paths").setValue (fileList.join());
 }

What we have now is a dcr hidden field with attached files separed by commas. It's easy to parse this field in order to obtain every file and adde it to the task within an external task:


 my $dcr_path = "absolute_path_to_dcr";
 if (open DCR, "<$dcr_path")
 {
  local $/=undef;
  $dcr_data = <DCR>;
  close DCR;
 }
 else
 {
  $error = 1;
 }

 my $rootnode = TeamSite:CRnode->new($dcr_data);

 if (defined $rootnode)
 {
        $file_list = $rootnode->value("hidden.file_paths");
    }
 else
 {
  my $l_error = $parser->get_error();
  $error = 1;
 }

 my @array_files = split(/,/,$file_list);

 foreach $file (@array_files)
 {
  $logger->writeLog(1,"PROCESAMOS $adjunto ");
  if (-f "$iwmount$area$file" && isModified("$iwmount$area$file"))
  {
   my $resp = $task->AddFile($file, "$area$file Added");
  }
 }

Something like that maybe works for you.