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

template_script in WFM

kaalraa

Hi there,

We are in process of migrating some WFTs within WFM. It has some complex code been done within template_script tag. Can anyone provide me some pointers/suggestions as where that code should be written within WFM?

Thanks in advance.

Find more posts tagged with

Comments

Adam Stoller

Hi there,

We are in process of migrating some WFTs within WFM. It has some complex code been done within template_script tag. Can anyone provide me some pointers/suggestions as where that code should be written within WFM?

Thanks in advance.

I don't think there's a simple single answer. It depends a lot upon what the code within the template_script tag was doing - but essentially it either becomes javascript - often as part of a conditional link between tasks, or as part of a custom instantiation form (i.e. FormAPI), or it becomes Java code as part of a preprocessor.

This is one of the reasons why IWOV never provided a tool to automatically convert from WFT to WFM - it requires a personal (and generally knowledgable) touch.

I'd suggest taking a step-back from the WFT code itself - and figure out (at a higher level) what you need the workflow to do, and set about implementing it as a WFM from scratch rather than trying to do 1:1 code transition.

BDO Data Set Order.jpg

kaalraa

Thanks Adam!! I was trying to do it as a part of pre-processor, however could not figure out the real place to implement. In general terms, the much important logic is of branch management. Rest could be handled through task or job params.

They are assigning the commands to the task based on the file from which branch it has been submitted. As an example:
Branch A - /default/main/store/production/WORKAREA
Branch B - /default/main/store/maintenance/WORKAREA

Any file submitted from any of the two, should call respective command within the workflow. Like file submitted from Branch A should execute the perl file residing at /apps/iw-home/local/bin/production/abc.ipl

Also, can a perl file be executed through a pre-processor?

Thanks.

I don't think there's a simple single answer. It depends a lot upon what the code within the template_script tag was doing - but essentially it either becomes javascript - often as part of a conditional link between tasks, or as part of a custom instantiation form (i.e. FormAPI), or it becomes Java code as part of a preprocessor.

This is one of the reasons why IWOV never provided a tool to automatically convert from WFT to WFM - it requires a personal (and generally knowledgable) touch.

I'd suggest taking a step-back from the WFT code itself - and figure out (at a higher level) what you need the workflow to do, and set about implementing it as a WFM from scratch rather than trying to do 1:1 code transition.

Adam Stoller

Thanks Adam!! I was trying to do it as a part of pre-processor, however could not figure out the real place to implement. In general terms, the much important logic is of branch management. Rest could be handled through task or job params.

They are assigning the commands to the task based on the file from which branch it has been submitted. As an example:
Branch A - /default/main/store/production/WORKAREA
Branch B - /default/main/store/maintenance/WORKAREA

Any file submitted from any of the two, should call respective command within the workflow. Like file submitted from Branch A should execute the perl file residing at /apps/iw-home/local/bin/production/abc.ipl

Also, can a perl file be executed through a pre-processor?

Thanks.

While you could do it with Configurable Variables, from experience with that, I'd suggest doing it with Script Variables.

If you always call the same task, but the task calls a different script based on the branch path - you set up a Global Script Variable (in the Workflow Properties) and then use that Script Variable as the value of the Command in the Task Properties for that task.

The script would look something like (note: "like" - you may have to play with the syntax a bit):

if ("$IW_BRANCH".match("\/default\/main\/store\/production") || "$IW_BRANCH".match("\/default\/main\/store\/maintenance")) {
    "/apps/iw-home/local/bin/production/abc.ipl";
}
else {
   "/apps/iw-home/local/bin/some_other_script.ipl";
}

I suppose you could use a pre-processor, but I haven't dealt with those yet, so I'm not sure what would be involved - the above should, I believe, do what you want (assuming I understood what you wanted).

It does add a level of additional maintenance, if the contents of the Script Variable needs to change for some reason, but by making the variable Global, you only have to change it at the Workflow Properties level, rather than at the individual task level (which comes in handy if the same script choice needs to occur in multiple tasks).

Hope that helps.