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

LSDS -> LSCS question

jsankara

I have created rules, actions and conditions...

If(URL contains "some value") {
get content tagged with "Category/Promo"
} else {
get content tagged with "Category/General"
}

The above rule will get executed on a .page file within a component... I want to show the resulted .page file content under the component..

And I have tagged two .page files (one with Category/Promo and other one with Category/General).

Rules getting executed correctly and I see the results showing in the logs: But the component doesn't show the resulted .page file ?.
How do I parse the output of the result ?.
How can i test it in component preview since the rule checks for some request params in URL ?
[HTML]

[DEBUG] 10:59:22 SearchResultProcessor - ACI Query response:
QUERYSUCCESS
112022021755e0d8bb8fc720669dfc6db90
f4c134851

96.0017743648904befd6ac32d99cad8a240
117594e9ea2d67317e2fc32e949702d0d514d1e8d0
[DEBUG] 10:59:22 BufferedFreemarkerView - Rendering view with name 'json/searchResultView' with model {search={total=1, status=200, start=0, included=1, urlBase=http://localhost:8090/lscs/v1}, item
s=[{id=04befd6ac32d99cad8a240117594e9ea, document=com.interwoven.wcm.iwrr.model.Document@4ce898, path=sites/lscs_app/AZSearchPromo.page, context=2d67317e2fc32e949702d0d514d1e8d0, type=document, uri
=/document/id/04befd6ac32d99cad8a240117594e9ea}], request=com.interwoven.wcm.iwrr.request.DocumentRequestImpl@19bc401} and static attributes {}
[DEBUG] 10:59:22 BufferedFreemarkerView - Added model object 'springMacroRequestContext' of type [org.springframework.web.servlet.support.RequestContext] to request in view with name 'json/searchRe
sultView'
[/HTML]

One more thing which I noticed in the logs: Its executing the query with format=json as additional param.. checked lscs-conf.properties, I see default-response format is XML

/lscs/v1/document/$?q=%28TeamSite%2FMetadata%2FContentCategories%3A%3D%22h1uw59s6%22%29+AND+%28TeamSite%2FMetadata%2FContentCategories%3A%3
D%22h1pyuecy%22%29&start=0&max=50&project=//app.project.com/default/main/LSCS&format=json

Find more posts tagged with

Comments

Rick Poulin

[Assuming this is a custom component, because I can't make sense of your question otherwise]

You have to tweak your XSL to render your results however you want to render them. For debug purposes, start with an <xsl:copy-of select="/Properties/Data/Result" /> and see what comes out of that.

That will also allow you to figure out the XML schema of the response within the context of a page. In component preview, you'd have to change the Java code to supply test parameters when context.getSite() returns whatever it returns in component preview mode. If you're using an OOTB external, then you just plain can't fake params.

As for your last question, lscs-conf.properties specifies the default response type when requesting results from the REST API without specifying the 'format' parameter. The LSCS Java client (lscsclient.jar) always forces format=json, because that's the format it's been implemented to decipher. It's always going to request JSON unless you implement your own client that does its own independent HttpURLConnection to the REST API.

Samir_Friend

I have created rules, actions and conditions...

If(URL contains "some value") {
get content tagged with "Category/Promo"
} else {
get content tagged with "Category/General"
}

The above rule will get executed on a .page file within a component... I want to show the resulted .page file content under the component..

And I have tagged two .page files (one with Category/Promo and other one with Category/General).

Rules getting executed correctly and I see the results showing in the logs: But the component doesn't show the resulted .page file ?.
How do I parse the output of the result ?.
How can i test it in component preview since the rule checks for some request params in URL ?
[HTML]

[DEBUG] 10:59:22 SearchResultProcessor - ACI Query response:
QUERYSUCCESS
112022021755e0d8bb8fc720669dfc6db90
f4c134851
0
96.0017743648904befd6ac32d99cad8a240
117594e9ea2d67317e2fc32e949702d0d514d1e8d0
[DEBUG] 10:59:22 BufferedFreemarkerView - Rendering view with name 'json/searchResultView' with model {search={total=1, status=200, start=0, included=1, urlBase=http://localhost:8090/lscs/v1}, item
s=[{id=04befd6ac32d99cad8a240117594e9ea, document=com.interwoven.wcm.iwrr.model.Document@4ce898, path=sites/lscs_app/AZSearchPromo.page, context=2d67317e2fc32e949702d0d514d1e8d0, type=document, uri
=/document/id/04befd6ac32d99cad8a240117594e9ea}], request=com.interwoven.wcm.iwrr.request.DocumentRequestImpl@19bc401} and static attributes {}
[DEBUG] 10:59:22 BufferedFreemarkerView - Added model object 'springMacroRequestContext' of type [org.springframework.web.servlet.support.RequestContext] to request in view with name 'json/searchRe
sultView'
[/HTML]

One more thing which I noticed in the logs: Its executing the query with format=json as additional param.. checked lscs-conf.properties, I see default-response format is XML

/lscs/v1/document/$?q=%28TeamSite%2FMetadata%2FContentCategories%3A%3D%22h1uw59s6%22%29+AND+%28TeamSite%2FMetadata%2FContentCategories%3A%3
D%22h1pyuecy%22%29&start=0&max=50&project=//app.project.com/default/main/LSCS&format=json

Let me get this straight:

You're retreiving a .page file through rule execution and hoping that it would automatically display in your component just like a normal .page file is previewed? The appearance XSL is also not defined for this component, right?

Can you elaborate what is your requirement? What you are trying to achieve sounds very absurd right now not knowing the details. I would suggest you to RTFM before assuming this kind of behavior for component display.

Ideally, the content that is tagged with taxonomy are the DCRs which are appended to the content XML after rule execution and which you then display using your component XSL.

In your case, if you really want to show some part of that page in your component, you'll have to append that retrieved page XML in your component's content XML and then use component's XSL to display particular values.

jsankara

Thank you both for the response..

You're retreiving a .page file through rule execution and hoping that it would automatically display in your component just like a normal .page file is previewed?
YES, resulted document will be a .page and I expect this .page content rendered under this component.
The appearance XSL is also not defined for this component, right? YES

Requirement
--
App1 -> HTTP request to http://runtime.app.com:8080/lsds_app/Main.page

Main.page contains the rule datum which executes the rule and get tagged content (another .page file). LSDS will render the Main.page and App1 will show the rendered output..

How Do i test this scenario in preview since it has dependency on request params and query string ?.

Rick Poulin

YES, resulted document will be a .page and I expect this .page content rendered under this component.

You can only render an HTML link to the .page that came back in your result. If you somehow want to render the result.page and include it into the body of your main.page, you'll have to either use an iFrame or use Java to HttpRequest the .page and then strip out what you want from the body. If you attempt to get the .page as a standard file handle, you'll get unrendered XML. You can't render the .page without going through an http request (at least not in any supported way).

How Do i test this scenario in preview since it has dependency on request params and query string ?.

Ideally, get to the page via a link on another page that has the needed parameters. For debugging, you can use Firefox: After you preview the page, right click on the frame and go "This Frame > Show only this frame". You'll get a window without the SitePub toolbar, and a URL with a seed value (long hex string) to which you can then append query string parameters parameters.

Samir_Friend

....
You'll get a window without the SitePub toolbar, and a URL with a seed value (long hex string) to which you can then append query string parameters parameters.

When you try to append your query parameters into this seed URL and hit it, it should probably throw an error. I do not have access to a TS installation right now to verify it.

Rpoulin, are you sure that this works? Have you tried it?

Rick Poulin

I don't know what you're basing that assumption on. Yes, I do this all the time and it works just fine.

If you have pageA.page which has a <a href="$PAGE_LINK[pageB]param=value&hello=world">, it's going to render the very same thing in preview => 1230984761078234.seed?param=value&hello=world. So why would doing it manually break anything?

jsankara

Thank you both... I will try that..

Samir_Friend

I don't know what you're basing that assumption on. Yes, I do this all the time and it works just fine.

If you have pageA.page which has a <a href="$PAGE_LINK[pageB]param=value&hello=world">, it's going to render the very same thing in preview => 1230984761078234.seed?param=value&hello=world. So why would doing it manually break anything?

I think both of us have been talking about different things - I was referring to the preview page URL you see in the address bar while previewing a LS page which does NOT work when you copy that URL, append some custom parameters and hit it in a new browser window, whereas you probably have been talking about page links in the component XSL where you can append custom parameters to a different page's link.

Rick Poulin

For debugging, you can use Firefox: After you preview the page, right click on the frame and go "This Frame > Show only this frame". You'll get a window without the SitePub toolbar, and a URL with a seed value (long hex string) to which you can then append query string parameters parameters.

/just sayin.