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

using iw_branch inside a TPL

Nawin

Hello all ,

in my TPL i am trying to fetch the current branch name,
can i use __VALUE__('iw_branch') with in the to get this .
I have tried it and i am getting an generation error.

Am i missing sumthing basic .

Thank you all for your inputs.

Find more posts tagged with

Comments

ISCBorisB

Hello all ,

in my TPL i am trying to fetch the current branch name,
can i use __VALUE__('iw_branch') with in the to get this .
I have tried it and i am getting an generation error.

Am i missing sumthing basic .

Thank you all for your inputs.

__TAG__ and __VALUE__ functions belong to the Workflow Engine wft interpreter, they are not available in templates.
Use iwpt_get_flag_param('-iw_include-location') call to get the Area where your PT has been invoked and regex
out the Branch from it

Nawin

thank you boris ,

gzevin

Hello all ,

in my TPL i am trying to fetch the current branch name,
can i use __VALUE__('iw_branch') with in the to get this .
I have tried it and i am getting an generation error.

Am i missing sumthing basic .

Thank you all for your inputs.

also, any perl TPL functions thet get you an object from a workarea (ofile or dcr name) will also provide you with a path that you can use to find workarea name.

nipper

also, any perl TPL functions thet get you an object from a workarea (ofile or dcr name) will also provide you with a path that you can use to find workarea name.

You need to be careful with the assumption, it will bite you.

if I use -ofile y:/default/main/.../foo.html then when I get ofile in the TPL I have the complete list. That is how the preview/generate buttons behave from the GUI.

However, if you are debugging a TPL and cd into the workarea and then use -ofile ./foo.html you will get ./foo.html in your TPL which will break your regex.

gzevin

You need to be careful with the assumption, it will bite you.

if I use -ofile y:/default/main/.../foo.html then when I get ofile in the TPL I have the complete list. That is how the preview/generate buttons behave from the GUI.

However, if you are debugging a TPL and cd into the workarea and then use -ofile ./foo.html you will get ./foo.html in your TPL which will break your regex.

'while true, one needs to know (always) WHAT they are doing, so it's YOU who is debugging, so YOU should know what path to use, because your TPL *in most (99.99%) cases* will be used in the context that I described.

nipper

'while true, one needs to know (always) WHAT they are doing, so it's YOU who is debugging, so YOU should know what path to use, because your TPL *in most (99.99%) cases* will be used in the context that I described.

Read some of the other posts in DevNet and then reconsider your statement. :-)

Actual_sales_cumulative_psr.rptdesign

Cummulative sales_psr.rptdesign

gzevin

Read some of the other posts in DevNet and then reconsider your statement. :-)

hm. I did not get it.

nipper

OK, let me translate to English for you.

I know that, you know that, Adam & Bo know that as well. But a lot of people on this list don't know that.

gzevin

OK, let me translate to English for you.

I know that, you know that, Adam & Bo know that as well. But a lot of people on this list don't know that.

oh, of course I understand this one. What I mean is that IF you are debugging ANYTHING, you need to supply real-life parameters. If you don't - tough luck - in any area of software development.

Also, you probably would agree that those who use iwpt_compile in debug mode WILL know what to pass. N'est pas? Smiley Happy

))

Adam Stoller

Also, you probably would agree that those who use iwpt_compile in debug mode WILL know what to pass. N'est pas? ))

I think it is "... SHOULD know what to pass." because, unfortunately, it isn't always the case.

gzevin

I think it is "... SHOULD know what to pass." because, unfortunately, it isn't always the case.

well, Adam, isn't this the case with anything? When one debugs something, they MUST know what they are doing. If not, we end up with buggy scripts, etc.

nipper

If not, we end up with buggy scripts, etc.

Having worked with you, I can certainly attest to *this* statement. :-)