Pass the querystring from a component to another page's component

If your component has Datum parameters in its ContentXML, the values will be changed to query parameters values with corresponding names, automatically.

So if my component has a parameter <Datum ID="foo" Name="foo">foobar</Datum> and I access the page with the URL http://server.domain/path/MyPage.page?, then the value for parameter foo will be "foobar", but if I access the page with the URL http://server.domain/path/MyPage.page?foo=bar then the parameter foo will have the value "bar".

Stokes.

GOMATHY

Is there any other way , using which we can pass the selected link's value as a parameter form a Component to another component in a different page.

Please anybody suggest me.

I can't think of an easier way than just using the url query parameters.

If you used a Java external on your component(s), they could communicate using session state or cookies, but that's not very scalable and generally undesirable.

Can I ask: What doesn't work for you about simply passing parameters on the URL? Maybe I'm misunderstanding your needs.

Stokes.

GOMATHY

Actually the parameters should not be visible in the URL , but this can't be done using the querystring.

Can you suggest any other possible means i could use for passing parameters without showing to users.

Then I guess there are tradeoffs between how secure you need it to be, and what you want to happen if the user bookmarks the 2nd page or emails the URL to a friend.

The most stateless is still to just obfuscate it in the URL, something as simple as hex-encoding the value will make it ?foo=bar look more like ?p=C3B107142BEF.
As long as your two components both know your encoding scheme, you can obfuscate any way you want.

Stokes.

If your component has Datum parameters in its ContentXML, the values will be changed to query parameters values with corresponding names, automatically.

So if my component has a parameter <Datum ID="foo" Name="foo">foobar</Datum> and I access the page with the URL http://server.domain/path/MyPage.page?, then the value for parameter foo will be "foobar", but if I access the page with the URL http://server.domain/path/MyPage.page?foo=bar then the parameter foo will have the value "bar".

Stokes.

hi,my livesite version is 3.0
use this method to pass parameter form one page to another,but it doesn't work,is there other need to take care?

hi,my livesite version is 3.0
use this method to pass parameter form one page to another,but it doesn't work,is there other need to take care?

That should work in 3.0 as well. You've got the parameter names declared as parameter Datums in your component?

it seems like parameter Datums declaration is different with general Datum declaration,is it?
what i did is as follow:

component1
appearance xsl
//**********************************
[html]

[/html]
page1 contain component1

//**********************************************************
//**********************************************************
component2
appearance xsl
//**********************************
[html]

[/html]
content xml
//********************************
[html]

inital value

[/html]
test_2.page contain component2

but when jump from the link on page1 to page2,page2 still display "inital value"

not "value2"

pls give me advise,thx

Try changing your Content XML to:

<Data>
  <External>
    <Parameters>
      <Datum ID="Parameters" Name="Parameters" Type="String">inital value</Datum>
    </Paramaters>
    <Object Scope="local">com.interwoven.livesite.external.runtime.Debugging</Object>
    <Method>dumpContext</Method>
  </External>
</Data>

The Object and Method are just dummy values, but you can leave them as-is to see that it works.

You might also have to change your XSL because the XPath will be slightly different:

<xsl:template match="/">
  <div>
    <h1><xsl:value-of select="//Datum[@Name='Parameters']"/></h1>
  </div>
</xsl:template>

Stokes.

Dear all,
Now I am using following code to pass parameters from one page to another, but it doesn't work, does current version support this method? or other wrong? Can you advise

Destination page:

Content xml:
[html]

inital value

com.interwoven.livesite.external.runtime.Debugging
dumpContext

[/html]
Appearance xsl:
[html]

[/html]

Source page:
[html]
Link From Here
[/html]

My Version:
Teamsite 6.7.2
LiveSite 3.0
Windows server 2003

What you mean it doesnt work? What sort of error are you getting? 404? When does it not work -- in preview or in production?

You may want to use PAGE_LINK or URL_PREFIX tokens. Also keep in mind that if you use PAGE_LINK then you do NOT need *?* in your href as the token will create one for you...

What you mean it doesnt work? What sort of error are you getting? 404? When does it not work -- in preview or in production?

You may want to use PAGE_LINK or URL_PREFIX tokens. Also keep in mind that if you use PAGE_LINK then you do NOT need *?* in your href as the token will create one for you...

Thanks vpatel,
I did it in preview, it seems can't get the parameter, the value always "inital value"
I have tried by using PAGE_LINK and URL_PREFIX , but it still doesn't work.

attitional, is it possible in production can?

How and what did you try with PAGE_LINK? Please post that.

Hi vpatel,
I tried following method:
[html]
A1.

A2.

A3.

B1.

$URL_PREFIX/sites/epson-singapore/printers_and_all_in_ones/destination.page

B2.

$PAGE_LINK[printers_and_all_in_ones/destination]

[/html]

only A2--B2 can(works), other combination can not(still "inital value")
in previous version Teamsite 6.7.1, i remember other combination also can.
Addition, i compare the class com.interwoven.livesite.external.runtime.Debugging between two versions, there's nothing different.

Have you tried something like this: <a href="$PAGE_LINK[printers_and_all_in_ones/destination]Parameter=new">URL Link Text</a> ??????

Try that. I think that is similar to your A2-B2 combo. If you want URL_PREFIX to work then the way the params are passed is a bit different.
For example: $URL_PREFIX/sites/epson-singapore/printers_and_all_in_ones/destination.page?Parameter=new << this will probably work fine in Runtime.
However you need a little different syntax for passing parameters in SP Preview. Look up the SP Dev guide you need to pass params as param.Parameter=new in preview mode. So you'll have to code your XSL / External logic to account for whether the execution is being done in preview or runtime and based on that output different link.

With PAGE_LINK, all of this logic is already taken care of for you. I would recommend the PAGE_LINK here as that is the cleanest and pretty simple way to do it.

In your component code, the Datum is named "Parameters" but in your URL you're passing Parameter (singular). Is that a typo or could the mismatch be your problem?

Stokes.

In your component code, the Datum is named "Parameters" but in your URL you're passing Parameter (singular). Is that a typo or could the mismatch be your problem?

Stokes.

Good catch Stokes.

Have you tried something like this: <a href="$PAGE_LINK[printers_and_all_in_ones/destination]Parameter=new">URL Link Text</a> ??????

Try that. I think that is similar to your A2-B2 combo. If you want URL_PREFIX to work then the way the params are passed is a bit different.
For example: $URL_PREFIX/sites/epson-singapore/printers_and_all_in_ones/destination.page?Parameter=new << this will probably work fine in Runtime.
However you need a little different syntax for passing parameters in SP Preview. Look up the SP Dev guide you need to pass params as param.Parameter=new in preview mode. So you'll have to code your XSL / External logic to account for whether the execution is being done in preview or runtime and based on that output different link.

With PAGE_LINK, all of this logic is already taken care of for you. I would recommend the PAGE_LINK here as that is the cleanest and pretty simple way to do it.

First, thanks for Stokes's care. But actually, Parameter and Parameters are in two different test. It didn't impact the pass function.

Yes, [html]URL Link Text [/html] also works. Thanks for your continuous concering and useful understanding advice.

First, thanks for Stokes's care. But actually, Parameter and Parameters are in two different test. It didn't impact the pass function.

So, in the test in question, is your "Parameter" Datum declared in the External/Parameters section of your component? Those are the only Datums that are automatically bound to the query parameters.

Stokes.

So, in the test in question, is your "Parameter" Datum declared in the External/Parameters section of your component? Those are the only Datums that are automatically bound to the query parameters.

Stokes.

Yes.
As vpatel said, using type PAGE_LINK is the cleanest and pretty simple way to do it.

hi, vpatel and all

Now i am facing a new problem:

under workflow, if the attach file is dcr(.xml), then reviewer will see dcr form screen when preview. (Here we didnt use tpl while livesit.) And the client request to more friendly. So i think we can convert the url .../templatedata/product/inkjet/data/T30.xml to something related this dcr.
e.g http://icd:81/iw-cc/previewfile?vpath=/default/main/epson/SINGAPORE/WORKAREA/shared/sites/epson-singapore/printers_and_all_in_ones/product.page?filename=T30.xml

Then we can preview this dcr under .page. Obviously, it will be more friendly.
But the same problem, system only can recognise http://icd:81/iw-cc/previewfile?vpath=/default/main/epson/SINGAPORE/WORKAREA/shared/sites/epson-singapore/printers_and_all_in_ones/product.page
if we add ?filename=T30.xml behind , when click it will say "The file //icd/default/main/epson/SINGAPORE/WORKAREA/shared/sites/epson-singapore/printers_and_all_in_ones/product.page?filename=T30.xml could not be found."

for this situation, is this method viable? if yes, how can i make this kind of url available? if no, is there any method to implement this function?

hi, vpatel and all

Now i am facing a new problem:

under workflow, if the attach file is dcr(.xml), then reviewer will see dcr form screen when preview. (Here we didnt use tpl while livesit.) And the client request to more friendly. So i think we can convert the url .../templatedata/product/inkjet/data/T30.xml to something related this dcr.
e.g http://icd:81/iw-cc/previewfile?vpath=/default/main/epson/SINGAPORE/WORKAREA/shared/sites/epson-singapore/printers_and_all_in_ones/product.page?filename=T30.xml

Then we can preview this dcr under .page. Obviously, it will be more friendly.
But the same problem, system only can recognise http://icd:81/iw-cc/previewfile?vpath=/default/main/epson/SINGAPORE/WORKAREA/shared/sites/epson-singapore/printers_and_all_in_ones/product.page
if we add ?filename=T30.xml behind , when click it will say "The file //icd/default/main/epson/SINGAPORE/WORKAREA/shared/sites/epson-singapore/printers_and_all_in_ones/product.page?filename=T30.xml could not be found."

for this situation, is this method viable? if yes, how can i make this kind of url available? if no, is there any method to implement this function?

You want to pass the filename as a parameter to the URL that is being passed as a parameter (parameter to parameter)?

If yes, you should make an attempt to read the SP Dev guide. There is a solution for your problem outlined straight up in there.

You want to pass the filename as a parameter to the URL that is being passed as a parameter (parameter to parameter)?

If yes, you should make an attempt to read the SP Dev guide. There is a solution for your problem outlined straight up in there.

you mean something like component template, right?