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

Passing Variables to External script

Vid

I am using an external task, and hence the command attribute of the task gives name of the external program. how do i retrieve the staging area correspoding to the branch my workarea is in, in the external program ?

Find more posts tagged with

Comments

Valentine

One of the parameters external task will get is a workarea name, you can easily derive staging from that.

Or, TeamSite::WFtask module has a GetArea() subroutine.

Sailesh

I am using an external task, and hence the command attribute of the task gives name of the external program. how do i retrieve the staging area correspoding to the branch my workarea is in, in the external program ?

You have to use workflow modules

use TeamSite::WFtask;
use TeamSite::WFworkflow;

then can use something like
$taskD = new TeamSite::WFtask($taskid);

my $area = $taskD->GetArea();

kaalraa

I am using an external task, and hence the command attribute of the task gives name of the external program. how do i retrieve the staging area correspoding to the branch my workarea is in, in the external program ?

As per my understanding you have the workarea, you are working on, in external script. If yes, then you have to replace WORKAREA/Content with STAGING to get the staging area corresponding to the branch.

Migrateduser

To clarify a little more what Kaalaara is indicating you would change the following..

$your_staging = somecode to change your workarea to staging.

However, I have a question. Are you looking to just find out what the staging area is within your external task, or are you wanting to have your external task run against the staging. If it's the latter, then the code above will work. But if it's the first option, then using Sailesh's answer will work to get you toward your goal.

Vid

thank you. what should be the format of the program name in the command tag.

the script i have used is
my $iwhome= TeamSite::Config::iwgethome();
my $externalcmd ="$iwhome/local/config/create.ipl";
and the command atttribute of an external task calls this as
command v='_INSERT_($externalcmd);'
but the create.ipl file in not run. . how can i run the .ipl file from the external task?

Adam Stoller

thank you. what should be the format of the program name in the command tag.

the script i have used is
my $iwhome= TeamSite::Config::iwgethome();
my $externalcmd ="$iwhome/local/config/create.ipl";
and the command atttribute of an external task calls this as
command v='_INSERT_($externalcmd);'
but the create.ipl file in not run. . how can i run the .ipl file from the external task?

What platform is your TS server running on? Windows or Unix?
If it's Windows - you need to do something like this:

my $iwhome = TeamSite::Config::iwgethome();
my $iwperl = "$iwhome/iw-perl/bin/iwperl";
my $externalcmd = "$iwperl $iwhome/local/config/create.ipl";

If it's Unix - you need to make sure that the script (create.ipl) is executable (e.g.: chmod 755) and that the #! line at the beginning correctly references the full path to iwperl.

Note - this is one of the reasons why you should include information about your environment and product version(s) when posting questions in these forums - a lot of times the answer can be different for different environments.

Vid

yes i working on windows. the script you suggested also is unable to run the file. is there a way (other than using a command tag) to run an external script in the task?

Vid

i need to create an edition from staging area, any alternatives?

Adam Stoller

i need to create an edition from staging area, any alternatives?

I don't mean to be "rude" but ...

I think you need to spend a lot more time reading the manuals, researching the forums, and/or taking Interwoven training.

Either that or you need to express yourself in such a way that it doesn't sound like you're trying to get everyone else to do your work for you in a piecemeal fashion (I need this.... I need this .... I need this ...)

Vid

thanks ghoti. am in a bit of a mess and i have 0 experience with workflows. yeap ill express my issues in a better way

Adam Stoller

thanks ghoti. am in a bit of a mess and i have 0 experience with workflows. yeap ill express my issues in a better way

I'm not sure if it will help - but you might try reading this with regard to workflow development. It's a little out of date as it doesn't cover things like the TeamSite::WFconstructor module - but you can find examples of how to use it in the iwhome/local/config/wft/solutions/ directory, the perldoc for the module and numerous forum postings in the Workflow forum.

You should probably still look into the training courses - but make sure that it's not a course on "Workflow Builder" (not sure if they have a course on Workflow Modeler yet - but that will only help you if you're using 6.7.1 and have an Interwoven SOAP license) - so ask first before you [have your company] plunk down a bunch of $$'s for it.

Vid

thanks a million !

Phanie

Are you planning to create an edition using an external task?

Phanie

One more question what version of TS are you on, if in TS 6.7.x you can use Workflow Modeller to make ur task easier.

Phanie

Vid

i am trying to create a workflow that automates the process of submitting files to staging and creating an edition , and then deploying files form the created edition. When we specify comlpete paths to files on the source , say /default/main/EDITION/index/index.asp (maybe using the filelist element) and the targetfilesystem area is given as

/default/main

Is the file index.asp deployed to

/default/main/EDITION/index or is it deployed to

/default/main

TS version 6.1

Adam Stoller

i am trying to create a workflow that automates the process of submitting files to staging and creating an edition , and then deploying files form the created edition. When we specify comlpete paths to files on the source , say /default/main/EDITION/index/index.asp (maybe using the filelist element) and the targetfilesystem area is given as /default/main

Is the file index.asp deployed to /default/main/EDITION/index or is it deployed to /default/main

TS version 6.1

You appear to be floundering here - perhaps this will help (perhaps not)?

For OD:

If you specify

- but I think that works in the current version(s) of OpenDeploy.Again, reading the manuals, taking training, and/or experimenting and carefully examining results and log files and such are things you (apparently) need to do more of.

Vid

that was very helpful, thanks !

Vid

my workflow has two tasks that require the file attribute, the deploy task and the submit task. however, from my understanding only start tasks can have the file attribute. how does the submit task work without the file attribute being specified ? are the selected files submitted to staging by default?

Adam Stoller

my workflow has two tasks that require the file attribute, the deploy task and the submit task. however, from my understanding only start tasks can have the file attribute. how does the submit task work without the file attribute being specified ? are the selected files submitted to staging by default?

The start task is where the files element is used to define the files associated with the workflow.
Once defined, that information is passed internally from task-to-task (externaltask and cgitask scripts can manipulate the list of files using TeamSite::WFtask methods) - thus a submittask simply uses information already present to generate the list of files to submit.

Vid

if submit task is my start task where i define the list of files, from what you say, dont i have to give a file list to my deploy task? For the file list to be transfered from task to task internally, should any attribute be set?

Adam Stoller

if submit task is my start task where i define the list of files, from what you say, dont i have to give a file list to my deploy task? For the file list to be transfered from task to task internally, should any attribute be set?

The list is transferred internally - without you needing to do anything about it - but your externaltask or cgitask script that performs the deployment needs to retrieve that information from the task object (see perldoc for TeamSite::WFtask) in order to generate a filelist for use with your deployment -- assuming your deployment is filelist based.