Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
getting a dcr value in callout
conmgmt
We have a dct which has an image item name with a browse button next to it. The user can click on the browse button and select another image dcr.
We want to achieve the following.....
Get the image.dcr and pass it to a callout (the callout is on the e same DCT next to browse button) and then open up that image dcr in a new window as read-only.
Has anyone implemented this using CCI or may be with another option ?
Find more posts tagged with
Comments
Migrateduser
It sounds to me like FormAPI might help with this (but not knowing what version of TeamSite you are dealing with I am not sure it is available).
The other option might be that in your callout you may be able to access some of the dct form attributes (you might want to just try capturing all of them in your callout and printing them out to see what is available).
conmgmt
we are using Teamsite 5.5.1
sajiddc
TS 5.5.1 should support FormAPI
james1
Let me see if I understand you. You have a piece of a DCT that looks like this:
<item name="...">
<browser initial-dir="/templatedata/category/type/data">
<callout ...>
</callout>
</browser>
</item>
You want the end user to browse for a DCR, and then you want the callout button to show the DCR is read-only/view mode.
Is that correct?
I don't see why this shouldn't be possible, assuming that this is the browser UI. The callout CGI will receive the value of *every* field on the screen, and it will receive the name of the item that the callout is attached to. Given that, it can get the value of its item, which is the path to the DCR. (See the callout docs and/or the example callout CGI for specific CGI parameter names to look for.)
Given the DCR path and other information, I assume (?) that the callout CGI could forward the browser window to a URL that is the read-only view of the specified DCR. Off hand, I don't know what that URL would look like, but I suspect that there may be a Knowledge Base article describing how to do this...?
Hope this helps.
-- James