Referencing templates with Parameters

Hi All,
I need to access templates based on the language type. For example, If I have the parameter selected as Japanese then I need to select the template which is a template in Japanese. Is there any way that we have a parameter list with all the language types and based on what is selected, change the template? Please let me know if there is a way to do this or atleast an alternate way to meet the requirement. Any help is appreciated. Thanks.

It's IE-only behaviour as a result of changes Microsoft made
last
year to their browser, regarding how Active Content (Flash,
Quicktime etc)
is handled, after losing a high profile court case.
http://blog.deconcept.com/2005/12/15/internet-explorer-eolas-changes-and-the-flash-plugin/
Background:
http://en.wikipedia.org/wiki/Eolas
See also
http://www.adobe.com/devnet/activecontent/
If you're running Dreamweaver 8.0.2, the fix is already built
into DW's
interface.
If not, try
http://blog.deconcept.com/swfobject/
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"marialmar" <[email protected]> wrote in
message
news:epltgd$qcm$[email protected]..
> Hello,
>
> I have several pages with templates, but with the new
Flash player, the
> swf that are included in the templates don't work, they
do'nt appear in
> the webpage.
> Any help please!!

Similar Messages

  • PA_CONTRACT_XSLFO: How to invoke a RTF-template with related data template

    Dear Reader,
    actually I want to extend the standard Document Type Layout for a Purchase Agreement Contract with additional data from approved supplier list (ASL).
    Therefor I have created a RTF-template and a data template with the needed sql-statement. For testing I put this in a standalone concurrent programm and it works fine (result was a blue table with all data rows).
    Next step for me was to invoke the RTF-template into the PA_CONTRACT_XSLFO template for extending the Document Type Layout for my Purchase Agreement Contract. So I put the neede invoke-statements
    <xsl:import href="xdo://XXOC.XX_RTF_TEMPLATE.de.00/"/>
    and
    <xsl:call-template name="XX_RTF_TEMPLATE"/>
    into the XSLFO-template. Also I extend the RTF-template with the define template statement
    <?template:XX_RTF_TEMPLATE?>
    So all seems to be fine.
    As result I get the standard document for Purchase Agreement Contract with the additional blue table from RTF-template BUT WITHOUT DATA !
    From my point of view there is no execution of the sql-statement in data template. But I dont know why.
    Do Oracle support a combination of XSLFO-template with data template?
    [XSLFO-template] with related [XSD-data definition]
    calls [RTF-template] with related [data template (with included sql-statement)]
    Thanks for your help.
    Best regards
    Mario.

    How to call a rtf template from another rtf template by passing a value try in main template create hyperlink of url with parameters for another template
    http://bipconsulting.blogspot.ru/2010/02/drill-down-to-detail-or-another-report.html
    When user pull a quote report from siebel this new rtf template should attach to the quote at the end.it'll be only another report
    IMHO you can not attach it to main. it'll be second independent report
    you can try subtemplate but it's not about rtf from rtf by click
    it's about call automatically rtf subtemplate from main rtf based on some conditions
    for example, main template contain some data and if some condition is true then call subtemplate and place it instead of its condition

  • Trying to create a template with adjustable text fields.

    I need to creat a form or template with adjustable text and image fields.  I need to have a background template for multiple pages that when I make a change to the template it make the changes to all pages, like the master page of indesign.  I also need to have text and image fields that are specific to each page but the dimensions and placement are controled by the template,but the information inside is page spacific.  What program should I use and anyone know a tutorial for help?

    What you want would require elaborate programming or dealing with variables in Framemaker or InDesign (Server) to dynamically generate the output upon request. You can of course get part of the features using normal variables in ID e.g. to pull linked images based on some parameters, but generally your request sounds too complex to deal with all scenarios.
    Mylenium

  • Problem with parameters in xsl

    Hi there,
    I have some trouble to use parameters or varaibles between models.
    Here is my xml file format :
    <ROOT>
    <PARAM>
    <NAME>NUMBER_STATION</NAME>
    <TYPE>INT</TYPE>
    <VAL>20</VAL>
    </PARAM>
    <PARAM>
    <NAME>NAME_STATION</NAME>
    <TYPE>TEXT</TYPE>
    <VAL>LAX</VAL>
    </PARAM>
    </ROOT>
    What I would like to do in the xsl code is to deal with PARAM differently if TYPE is INT or TEXT.
    Here is my xsl code :
    <xsl:stylesheet
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:java="java"
    xmlns:display="base.Display"
    version="1.0">
    <xsl:param name="name_p">0</xsl:param>
    <xsl:param name="type_p">INT</xsl:param>
    <xsl:output method="html" />
    <xsl:template match="/">
    <xsl:apply-templates select="ROOT/PARAM[NAME=$name_p]/TYPE" />
    <xsl:apply-templates select="ROOT/PARAM[NAME=$name_p]/VAL" />
    </xsl:template>
    <xsl:template match="TYPE">
    <xsl:variable name="type_p" select="text()"/>
    </xsl:template>
    <xsl:template match="VAL">
    <xsl:choose>
    <xsl:when test="$type_p = 'POURCENT'">
    <td>
    </td>
    </xsl:when>
    <xsl:otherwise>
    <td>
    </td>
    </xsl:othewise>
    </xsl:choose>
    </xsl:template>
    But of course this is not working...I also tried to use <xsl:call-template> with a parameter but without sucess. Does anybody have some idear about that ?
    Thanks in advance !

    "Not working" is not much information to go on. So I will just throw out some ideas. First make sure you are actually passing the parameters to your transform. Second, use XPath expressions that actually select something from your XML. The ones you are using are looking for a TYPE element that's the child of a PARAM element (that has a NAME child with a particular value), and there are no such elements in your example.
    PC&#178;

  • Filter Web Template with URL Cmd: doesn't work with compound infoobject ?

    Hello all,
    I've to filter the query contained on a web template with URL command, but it doesn't work.
    The web template contains only one query, and on the free chars I have 0PLANT.
    I call the web template adding to the normal url the following command:
    &FILTER_IOBJNM=0PLANT&FILTER_VALUE=33
    where 33 is the code of the plant I want to filter.
    The command is executed, I think, because the  result is "NO APPLICABLE DATA FOUND". The fact is that when I execute this query on the Bex filtering 0PLANT by value 33 the data exists.
    May be because 0PLANT on our system is in compound with 0SOURSYSTEM ? In this case, what's the value I can use as filter ?
    Thank's in advance,
    Max

    Hi,
    please see http://help.sap.com/saphelp_nw04/helpdata/en/59/edfe395dd76846e10000000a114084/frameset.htm
    especially:
    If the variant with ending 'EXT' is selected, the fully compounded value has to be entered in the external format, for example, 24.12.2000.
    If the ending 'EXT' is not used, the fully compounded value has to be entered in the internal format, for example, 20001224 for 24.12.2000.
    and
    In the internal display (see table below) you can easily determine the name of the characteristic and the filter value using the URL parameter &snippet_operations=%20 (see also Object Tag for the Properties of Web Templates). Call the Web application with this URL parameter. If you filter using the context menu, the parameters FILTER_IOBJNM and FILTER_VALUE are automatically added to the URL in the Web browser. You can then use the desired values with Command URLs in hyperlinks.
    Heike

  • Problems with parameterized Url

    Hey,
    can anybody help me?
    I created following URL with 4 filter values:
    http://XXX/sap/bw/BEx?sap-language=EN&bsplanguage=EN&CMD=LDOC&TEMPLATE_ID=my_template& FILTER_IOBJNM_1=0SOLD_TO&FILTER_VALUE_1=123&FILTER_IOBJNM_2=0CO_AREA&FILTER_VALUE_2=123&FILTER_IOBJNM_3=0COMP_CODE&FILTER_VALUE_3=123&FILTER_IOBJNM_4=0SALESORG&FILTER_VALUE_4=123
    When I execute the url in browser a screen with filter value selection appears. I created the template with WAD 3.x - with WAD 7.0 it doesn't work. Do I have to use other parameters here?
    Best regards,
    Jule

    Hi Jule,
    I am facing issuse of URl length
    We pass the parameters in the URL for new 7.x machine. Unfortunately we are running more than 3000 characters, whereas system is allowing upto 2083 characters. Please do needful.
    &BI_COMMAND_1-BI_COMMAND_TYPE=SET_SELECTION_STATE_SIMPLE
    &BI_COMMAND_1-TARGET_DATA_PROVIDER_REF_LIST-TARGET_DATA_PROVIDER_REF_1=DATAPROVIDER_1
    &BI_COMMAND_1-TARGET_DATA_PROVIDER_REF_LIST-TARGET_DATA_PROVIDER_REF_2=DATAPROVIDER_2
    &BI_COMMAND_1-TARGET_DATA_PROVIDER_REF_LIST-TARGET_DATA_PROVIDER_REF_3=DATAPROVIDER_3
    &BI_COMMAND_1-TARGET_DATA_PROVIDER_REF_LIST-TARGET_DATA_PROVIDER_REF_4=DATAPROVIDER_4
    &BI_COMMAND_1-TARGET_DATA_PROVIDER_REF_LIST-TARGET_DATA_PROVIDER_REF_5=DATAPROVIDER_1_2
    &BI_COMMAND_1-RANGE_SELECTION_OPERATOR=EQUAL_SELECTION
    &BI_COMMAND_1-RANGE_SELECTION_OPERATOR-EQUAL_SELECTION=MEMBER_NAME
    &BI_COMMAND_1-RANGE_SELECTION_OPERATOR-EQUAL_SELECTION-MEMBER_NAME=0000000000000000000000000000000080000020
    &BI_COMMAND_1-CHARACTERISTIC=ZCRMPRDL1
    &BI_COMMAND_2-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_2-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroMonthlyBacklogofOpenBugs
    &BI_COMMAND_2-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_2-INIT_PARAMETERS-TITLE=AstroMonthlyBacklogofOpenBugs
    &BI_COMMAND_2-TARGET_ITEM_REF=CHART_1
    &BI_COMMAND_3-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_3-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroMonthlyBacklogofOpenBugs
    &BI_COMMAND_3-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_3-TARGET_ITEM_REF=TABLE_1
    &BI_COMMAND_4-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_4-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroWeightedDefectCount(WDC)ofOpenCustomerBugs
    &BI_COMMAND_4-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_4-INIT_PARAMETERS-TITLE=AstroWeightedDefectCount(WDC)ofOpenCustomerBugs
    &BI_COMMAND_4-TARGET_ITEM_REF=CHART_2
    &BI_COMMAND_5-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_5-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroWeightedDefectCount(WDC)
    &BI_COMMAND_5-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_5-TARGET_ITEM_REF=TABLE_2
    &BI_COMMAND_6-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_6-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroMonthlyIncomingRateofBugs
    &BI_COMMAND_6-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_6-INIT_PARAMETERS-TITLE=AstroMonthlyIncomingRateofBugs
    &BI_COMMAND_6-TARGET_ITEM_REF=CHART_3
    &BI_COMMAND_7-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_7-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroMonthlyIncomingRateofBugs
    &BI_COMMAND_7-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_7-TARGET_ITEM_REF=TABLE_3
    &BI_COMMAND_8-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_8-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroIncoming/ResolvedRatio-CustomerProductionBugs
    &BI_COMMAND_8-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_8-INIT_PARAMETERS-TITLE=AstroIncoming/ResolvedRatio-CustomerProductionBugs
    &BI_COMMAND_8-TARGET_ITEM_REF=CHART_6
    &BI_COMMAND_9-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_9-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroIncoming/ResolvedRatio-CustomerProductionBugs
    &BI_COMMAND_9-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_9-TARGET_ITEM_REF=TABLE_6
    &BI_COMMAND_10-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_10-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroIncomingSupportCalls
    &BI_COMMAND_10-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_10-INIT_PARAMETERS-TITLE=AstroIncomingSupportCalls
    &BI_COMMAND_10-TARGET_ITEM_REF=CHART_4
    &BI_COMMAND_11-BI_COMMAND_TYPE=SET_ITEM_PARAMETERS
    &BI_COMMAND_11-INIT_PARAMETERS-WITH_TRAY-TRAY_SETTINGS-CAPTION=AstroIncomingSupportCalls
    &BI_COMMAND_11-INIT_PARAMETERS-WITH_TRAY=X
    &BI_COMMAND_11-TARGET_ITEM_REF=TABLE_4

  • Email template with an image

    Hi,
    I would create an email template with an image embedded.
    I created the email template with outlook on my PC. The body is the following.
    <body lang=EN-US link=blue vlink=purple><div align=right style='text-align:right'><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"
    filled="f" stroked="f">
    <v:stroke joinstyle="miter" />
    <v:formulas>
    <v:f eqn="if lineDrawn pixelLineWidth 0" />
    <v:f eqn="sum @0 1 0" />
    <v:f eqn="sum 0 0 @1" />
    <v:f eqn="prod @2 1 2" />
    <v:f eqn="prod @3 21600 pixelWidth" />
    <v:f eqn="prod @3 21600 pixelHeight" />
    <v:f eqn="sum @0 0 1" />
    <v:f eqn="prod @6 1 2" />
    <v:f eqn="prod @7 21600 pixelWidth" />
    <v:f eqn="sum @8 21600 0" />
    <v:f eqn="prod @7 21600 pixelHeight" />
    <v:f eqn="sum @10 21600 0" />
    </v:formulas>
    <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
    <o:lock v:ext="edit" aspectratio="t" />
    </v:shapetype><v:shape id="Picture_x0020_1" o:spid="_x0000_s1026" type="#_x0000_t75" alt="Description: LOGOXYZ_resized" style='position:absolute;left:0;text-align:left;margin-left:62.8pt;margin-top:0;width:114pt;height:68.25pt;z-index:251658240;visibility:visible;
    <v:imagedata src="cid:[email protected]" o:title="LOGOXYZ_resized" croptop="4024f" cropbottom="9198f" cropleft="10723f" cropright="9533f" />
    <w:wrap type="square"/>
    </v:shape><![endif]--><![if !vml]><img width=152 height=91 src="cid:[email protected]" align=right hspace=12 alt="Description: LOGOXYZ_resized" v:shapes="Picture_x0020_1"><![endif]><b><u><span lang=IT
    style='color:black'><o:p></o:p></span></u></b></p><p style='<b><u><span lang=IT>SI RACCOMANDA DI LEGGERE ATTENTAMENTE QUESTA LETTERA E DI CONSERVARLA</span></u></b><span lang=IT
    style='color:black'><o:p></o:p></span></p><p style='<span lang=IT style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p style='<span lang=IT>Si
    comunica che sono state attivate le credenziali di [//Target/LastName] [//Target/FirstName] per l'accesso alla Rete.<span style='color:#1F497D'><o:p></o:p></span></span></p><p style='<b>Scadenza: </b><span
    lang=IT>[//Target/EmployeeEndDate]</span><b>&nbsp;</b><span style='color:#1F497D'><o:p></o:p></span></p><table border=0 cellspacing=0 cellpadding=0 style='border-collapse:collapse'><tr><td
    width=225 valign=top style='width:168.5pt;border:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt'><p align=center style='text-align:center'><b>Applicazione</b><o:p></o:p></p></td><td width=225 valign=top style='width:168.55pt;border:solid
    windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt'><p align=center style='text-align:center'><b>Nome utente</b><o:p></o:p></p></td><td width=225 valign=top style='width:168.55pt;border:solid windowtext
    :p></o:p></span></p></td><td width=225 valign=top style='width:168.55pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt'><p
    align=center style='text-align:center'><span lang=IT>[//Target/ADInitialPassword]<o:p></o:p></span></p></td></tr></table><p style='<span style='color:black'><o:p>&nbsp;</o:p></span></p><p
    style='<span lang=IT style='color:black'>Per eventuali ulteriori informazioni contattare il SSIT all’indirizzo
    [email protected].</span><span lang=IT><o:p></o:p></span></p></div></body>
    Then I exported this template to the FIM Portal server, in the "Email Template" administration section on the Portal.
    Where must I put the image to allow FIM to link it? Which attribute have I to modify with the correct path (src?)? And how?
    Can you provide me some examples of the correct form of the path attribute?
    Thank u very much.
    Francesca

    The problem with using "cid" for embedded images is that the email message needs to be formatted differently. You don't have control over the header, mime type and other aspects that need to be defined to include and reference a "cid image" in the message
    body.
    First, the message header will need to have the following fields:
    From: [email protected]
    To: [email protected]
    Subject: Test example
    Mime-Version: 1.0
    Content-Type: multipart/related; boundary="boundary-name"; type="text/html"
    The "boundary" is what separates the content of the message to form the "multipart/related" pieces.
    The message body then has boundary markers and additional content headers to define the individual pieces:
    --boundary-name
    Content-Type: text/html; charset="US-ASCII"
    This is an HTML document, which contains a URI
    referencing a resource in another body part, for example
    through a statement such as:
    <img src="cid:myImage" ALT="Big Smiles">
    --boundary-name
    Content-Location: CID:blahblah ; this header is not used
    Content-ID: <myImage>
    Content-Type: image/jpeg
    Content-Transfer-Encoding: BASE64
    /9j/4AAQSkZJRgABAQEASABIAAD/4QJQRXhpZgAATU0AKgAAAAgACgEPAAIAAAAUAAAAhgEQAAIA
    AAAJAAAAmgEaAAUAAAABAAAApAEbAAUAAAABAAAArAEoAAMAAAABAAIAAAExAAIAAAASAAAAtAEy
    AAIAAAAUAAAAxgITAAMAAAABAAEAAIdpAAQAAAABAAAA2sSlAAcAAAAQAAAB/gAAAg5TYW1zdW5n
    IEVsZWN0cm9uaWNzAFNHSC1BODY3AAAAAABIAAAAAQAAAEgAAAABUGFpbnQuTkVUIHYzLjUuMTAA
    MjAxMjowODoxMiAyMzoxODoyOAAAEYgiAAMAAAABAAIAAJAAAAcAAAAEMDIyMJADAAIAAAAUAAAB
    rJAEAAIAAAAUAAABwJEBAAcAAAAEAQIDAJIBAAoAAAABAAAB1JIHAAMAAAABAAEAAKAAAAcAAAAE
    MDEwMKABAAMAAAABAAEAAKACAAQAAAABAAAGAKADAAQAAAABAAAIAKAFAAQAAAABAAAB3KMAAAcA
    AAABAwAAAKMBAAcAAAABAQAAAKQBAAMAAAABAAEAAKQCAAMAAAABAAAAAKQDAAMAAAABAAEAAAAA
    AAAyMDEyOjA4OjEyIDE0OjU3OjI1ADIwMTI6MDg6MTIgMTQ6NTc6MjUAAAAMAAAABAAAAgABAAIA
    AAAEUjk4AAACAAcAAAAEMDEwMAAAAAAAAAAAUHJpbnRJTQAwMzAwAAAAAAADARoABQAAAAEAAAI4
    ARsABQAAAAEAAAJAASgAAwAAAAEAAgAAAAAAAAAAAEgAAAABAAAASAAAAAH/2wBDAAIBAQIBAQIC
    AgICAgICAwUDAwMDAwYEBAMFBwYHBwcGBwcICQsJCAgKCAcHCg0KCgsMDAwMBwkODw0MDgsMDAz/
    2wBDAQICAgMDAwYDAwYMCAcIDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM
    DAwMDAwMDAwMDAz/wAARCAgABgADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQF
    BgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS
    0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4
    eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi
    4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
    AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl
    8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImK
    kpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP0
    9fb3+Pn6/9oADAMBAAIRAxEAPwD6dmiZmyF4HNOjXygMkc1NjyhjPIppjDA+9em6e9jzIK2ok0wI
    64B/SoIozLGSDUgG75WGMcfWmyMI4yFOAKzUdLNlOnzatEaqCSC3K9P/AK1SMx8oBRkGq6oZJeMA
    GraR+ZsUHocmsqsLtN6mlNq1oljTrJlAz610Ok6eEkDk9BVXTbQNGuDyDWo8nkRba2pUbxvMxquP
    Ly2KeuSrgqOoqrpSmVSah1GbzpDjPWrVo4t7Pd6CrdJuJlCCg0UtaultYmDcEVxepkSuWxkGtbxX
    qX2mbaD096xWQFQcipkr7GzjdNSIjH5oHJAHt1pFgXf/AFNSiMLEcdetMjYouM8miEHF6HLJJpLY
    bLhOhxnvRDaoVJGeaiklJPpinpMIIx3xWsoy0VzOnGCmAgRHYcHjNWra2MpA7VT2GeTeFxitrw/Z
    GYgH8aHDoHKnLa5t6PYqI0J5A/KofEd0udqdBWxGEtbQj+L6Vx3ii9MDMQe/rTS5LWY5wlpZGTq8
    ytMSRjiodPhDtuHaq8lz9qJx1NX7W3WCHryazSlN6nTOMIU7ou2x/dk9cdqcg8wgelRo3lxD1NTx
    ncoA496rks7nIrShykkbEIV6k1B5SwvuPrUvO3AbJqrdXW2M57VsptbkypR08jK8TSi7iYEfNyAa
    5m2VpmKjr/KtjU7oMWO6qPh2Atcu7D5TwD71pH4TjnBOtfqUrmI22QRiremSB0HoO1WNXtlaI560
    3R1W3iIKne3qKh8rTTNo03TmmWZJDhQh5zznrj296bfBvIBzz+vFTRhXc7sgiq08zSTf7PaiKSXK
    TNc03UI4ZCeH6euKZdQmQZGCP1qwsJU5J+lMRBJLjPGax5eV3Om/PHlJbOEtBgdcVz+sWpiZkPQn
    v1rtdIt0kXAUYNc345sTb3vHQjAryMfdvmPqMlXLF0znXkSMAFscVGtgHkLZytMumMgCYwT/ADpE
    le3bGBkVxRi7N7Ho+xTldks0ghTABAzj8KtaTcpHqELZ6GqkhLW+WGDmoomEUwcHoeKzhK+jZUaf
    K20j3DStSik0+Pa3y4zTn1BQCQeK8+8M+NI5LZYhJ8yDGKu3nisRAruwT3FdEKi2PPrUG/iOvl1t
    HBG8cfzrNudZTee5zXHz+K2Y4BqOfxCZEznmm5S2GqCdtLs7NvFChQARx71XuNc3tuGAa4OfVpGc
    MCetLda5PsABYgelZQhyat3K9jzy1Wx2i6xtY5K8/pTZdeTcRkZIxiuBk8Qyl8DORznNLDqkkjYY
    gMfeuiNNN+0uS6PLeKidrHqwJ5IyDSvrQEgG6uMk1CSFxghs+/NF3qckaZ3fNilOX8hVLBvlOsm1
    oRS43DFMfxEu71AFchHqxkQ7mwaT+1yOxpdbkywzadkdiuvoSSTxSrq6MMluetcTPfSSgbSQPrSS
    am6DAJH409W7jp4TRSmjtW8Tp9xn4FJJ4kjCYLDNcLJeNu3bs5qFdVaSXaCeK0jDmWi2E6Mov1O1
    l1xGBwxyPWmHxCgGMfrXGza0wOACM96Fvy5wCefeibeiYoYLVnaJ4jURhQQPxqjPriySMrOOveuU
    lnkZsKTmoBOxY7zzUSjKL0Z0LBxqWjI6866sakbxs/SobvxGkigKSBXOKxEffH1pjA7sqM4/Ss4S
    m/iZnPDx5nCOxuT+JhGwHUkVXHiLcW28fjWI8vmOcjBFIAUJI71o5tR5UJYWN1M1rnxKzAHHTvUa
    eIXeTPpWaYTuyehoWHCHbzRzaJSLWEvNSaNabxM+zj73as3UNSmnZWJOT7UstsVjUjqabMAiiqi0
    ndI6nhIVLqexFb3JRySKfLPk+mfzpkFuysz4ypNK4E8oGcY/nVVal5oyWGhBWgrMZvAc8YNV5mad
    yAM1bNqvOajwFl471NJ2lqNYeKS5iKKBi21jjFOY+U3y9DxU7oAMjmmtbkENj5aUqd5XvuZujGL0
    W5G8fnIA2M/ypUbyY8d+lOa3IYsW4qQlViBIyaxcHpG+x0UIqzcdyrLbbhknr7VClkzOGarkf785
    6gVLs2kkjjtW6lb4jWthoVYq6Kf2TYDyBzUaWYlYseKurDuBJbr2pi2xD9eKt9Wmc8cOrqJVePyF
    GDnNS2aFsnPNStEG4boKdCiR5IbkVz16jceS5v7O0tBfsxlTk4xUfk7Tk9Vp4JD5BpWnDZBoow5F
    aJVuaXvFcRndkdjT5IGMfJp5nXawxSWr5BBHNTOKvdilRUpr8x1vJ5UO304piMN2fWpJEUEc/wD6
    6aEXNHslFadSp0o1I8r6BICy5zVVm2BgO9WlTjnpTJYxnApVUlCyQ/Yc6Vuhnpu34PGPapZMPHyc
    4ptwFR6dFEki8nnvzWUW7pozhGTTpkCgwnI+7SM3nK3HFMvW2uQh+WnRkrDjpkV0ppLnOe0V7jVz
    C1wBZipHIqot4UIH8IFaOvoCB/eH61jhcHnpTS5kc85ezqbaMW5vpI4tqng+1RzXmHwOQO5qW4IX
    B7Cid4/K5UbselS46WE3dtjIr5iOME4qG5dln8z0HSpoCvk5VTmo2g8zdvz7emKVOpZKLRpKm5rm
    uQpqTKxJxlvamvqEss4UcYpLgAuAMjHqKYJtsxJwSfUda0qOUveRFGXJFw7jboIj/PnJ/nUlixZx
    2A4/+uKJ4hOQScEd6SWJoivI+b07Gtoz51Znn+z9i+aK6k1zIY2+RvlPfNVZYzbx5z94fhU8q+TD
    jqelVLqcGEgdBXOvitE7alN25noVppflJJ4qPTpQpLFs4Ofw7VSurpAMbzx61We4MY3DjNepGF4H
    zta8KvMjWa7V3ODkdqSGfzEIIPH51mm9R4AM7WHeqzak0k+NxPlng++KrV6I6adKHKnJ7mheRKcu
    OGH5msK7AkIY8bTn/Cr73284yeB6VSm8sybSD0/SlQT+0YVqacrUylLqLOhI6g1Wa586IFiAQfTt
    V4WiysCB0qtqFnBasBk5I/DrXQ5Ju6WxzWlCS5nYo6+oks2ZDjI/KvM/EFt5kz7/AMK9N1UeTZHb
    8w28153rDpc3gwfmU1MJOE3K50aT9SppTCMLGT93Fei+CbjfAMj2rztJfKnbA6D8cc133hFwLYc8
    moqVG1dIupSV49DodR/eSKo+9t6+1FnbGOQEg5A/AU6G32NvbcpHTIqaGKSRvlbGR/8ArqoTsmjO
    tRfMpPfoWBqKAKkjc56VMtxDEdwPLVRltVtcbjuPQZpECLNls98fhStGNlHqKlRUtWtYmv8A2gJA
    MnoOBTIb4oSMEfTtVAIZDj7oHT3FPLF5Rl1bn8KlqzsaQ11e9yzd6sbVtir1PSlt5vNddxwR3qld
    wiSbcWziprVhM6A4yD+Vc1SbWxvh4e/bc6KxVyMdV96mutPTyxkkk/pUViMR7FPzL1q0rAkK3Ufn
    Xnyk29eh9FSoxUPUqCYWfyj/AOvVPUr77UMHgCtS7tUUhyoJrL1aNCjNnDCqo1Oaepz4qhKFH3Sl
    NeqvAPTikjv9mNxGBVK4RJY2Azk/zqCQsY2UqckYFesqcbK587TxU1JtfM111bzwXjOSvFEeou/z
    Dkis7TpI0TkYOPzqwzFcbBijlTVwqVpLTpuWBq+9SNqhgPxqGC6+Z2Peq8ilHHOKmaMvgqcJiqSS
    d2Y1ak57CW9+zTkZ4zV1IRGwIbr0qpHEiuSPX86tKu+NQOMGtFLd9zmdK9oy6ak7xGQ7nJI9KlNw
    08Z24wBj86ZPFlFwfmP5U+1BgZlxxWWqSZ6E6NrNrcdbzPHEo7E5+lIJftjsnQqalZsMD29MVIY4
    omBUckdhSm1K1gpRlFWRUEYS4VCzdecVanl8qHC4KjtSNbRPMG/i4JzUzQK4ULjC1nJXtY0pJwUu
    frsRaXKHf5RgjpWtqKs0C9cqKy7QCNye47AVpLc+fCwbhj0NTJu5NKSdJ9CiQ23rhgOKfZTNt+fI
    zUywYG5u3T600Qgkeh/Srg76SOWceSScdS1C6LCyMTg0xH3kcVIkKJArHOMcVCr734bGaUd7G9R6
    JNb9B1wrQo2OM0yzJTOOasW9k0/BbG01bi05YY2YnDH+dVKSV0ZU6Dm1JLYrW915UZDKSTzUtxD5
    smegFKLZCuSx61OXQAIO361nG0al4mqg5JxloitaAKSuBuq2DnCgUlukUbE7cY/WrAuIghwRuA/W
    rbbbuZUoqFmvQiUZc4GPWnJEXjDcgHtTi6qRz196mKnH+z/Sphd+9c2nDmVmU2tfNYqw4HSi2tAJ
    dgPT+dWoLlN5zjrSC5QXWRnp27VtHRu3YynH4e1y/bwKUI6cfjVWSwzKRnFWIryNYS5PzelRC8W4
    YnHSuNyqdDtVGErx
    --boundary-name--
    The HTML references the embedded content-id via the special "cid" URI. This is the same method used for email attachments. Using the "cid" allows an attachment to be rendered as content in the body of the email.
    Since this would already require you to know the underlying mime type of the image, you already need to have the image data converted to Base64 encoding, and you don't have any control over the headers of an email template in FIM... you would need to write
    your own email activity and not use the out-of-the-box FIM activities. The other method of getting an email to embed an image is to use the special "data:mime-type" URI in the src attribute of an img tag:
    The same image shown above can be placed inline like so:
    <img src="data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEASABIAAD/4QJQRXhpZgAATU0AKgAAAAgACgEPAAIAAAAUAAAAhgEQAAIA
    AAAJAAAAmgEaAAUAAAABAAAApAEbAAUAAAABAAAArAEoAAMAAAABAAIAAAExAAIAAAASAAAAtAEy
    AAIAAAAUAAAAxgITAAMAAAABAAEAAIdpAAQAAAABAAAA2sSlAAcAAAAQAAAB/gAAAg5TYW1zdW5n
    IEVsZWN0cm9uaWNzAFNHSC1BODY3AAAAAABIAAAAAQAAAEgAAAABUGFpbnQuTkVUIHYzLjUuMTAA
    MjAxMjowODoxMiAyMzoxODoyOAAAEYgiAAMAAAABAAIAAJAAAAcAAAAEMDIyMJADAAIAAAAUAAAB
    rJAEAAIAAAAUAAABwJEBAAcAAAAEAQIDAJIBAAoAAAABAAAB1JIHAAMAAAABAAEAAKAAAAcAAAAE
    MDEwMKABAAMAAAABAAEAAKACAAQAAAABAAAGAKADAAQAAAABAAAIAKAFAAQAAAABAAAB3KMAAAcA
    AAABAwAAAKMBAAcAAAABAQAAAKQBAAMAAAABAAEAAKQCAAMAAAABAAAAAKQDAAMAAAABAAEAAAAA
    AAAyMDEyOjA4OjEyIDE0OjU3OjI1ADIwMTI6MDg6MTIgMTQ6NTc6MjUAAAAMAAAABAAAAgABAAIA
    AAAEUjk4AAACAAcAAAAEMDEwMAAAAAAAAAAAUHJpbnRJTQAwMzAwAAAAAAADARoABQAAAAEAAAI4
    ARsABQAAAAEAAAJAASgAAwAAAAEAAgAAAAAAAAAAAEgAAAABAAAASAAAAAH/2wBDAAIBAQIBAQIC
    AgICAgICAwUDAwMDAwYEBAMFBwYHBwcGBwcICQsJCAgKCAcHCg0KCgsMDAwMBwkODw0MDgsMDAz/
    2wBDAQICAgMDAwYDAwYMCAcIDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM
    DAwMDAwMDAwMDAz/wAARCAgABgADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQF
    BgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS
    0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4
    eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi
    4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
    AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl
    8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImK
    kpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP0
    9fb3+Pn6/9oADAMBAAIRAxEAPwD6dmiZmyF4HNOjXygMkc1NjyhjPIppjDA+9em6e9jzIK2ok0wI
    64B/SoIozLGSDUgG75WGMcfWmyMI4yFOAKzUdLNlOnzatEaqCSC3K9P/AK1SMx8oBRkGq6oZJeMA
    GraR+ZsUHocmsqsLtN6mlNq1oljTrJlAz610Ok6eEkDk9BVXTbQNGuDyDWo8nkRba2pUbxvMxquP
    Ly2KeuSrgqOoqrpSmVSah1GbzpDjPWrVo4t7Pd6CrdJuJlCCg0UtaultYmDcEVxepkSuWxkGtbxX
    qX2mbaD096xWQFQcipkr7GzjdNSIjH5oHJAHt1pFgXf/AFNSiMLEcdetMjYouM8miEHF6HLJJpLY
    bLhOhxnvRDaoVJGeaiklJPpinpMIIx3xWsoy0VzOnGCmAgRHYcHjNWra2MpA7VT2GeTeFxitrw/Z
    GYgH8aHDoHKnLa5t6PYqI0J5A/KofEd0udqdBWxGEtbQj+L6Vx3ii9MDMQe/rTS5LWY5wlpZGTq8
    ytMSRjiodPhDtuHaq8lz9qJx1NX7W3WCHryazSlN6nTOMIU7ou2x/dk9cdqcg8wgelRo3lxD1NTx
    ncoA496rks7nIrShykkbEIV6k1B5SwvuPrUvO3AbJqrdXW2M57VsptbkypR08jK8TSi7iYEfNyAa
    5m2VpmKjr/KtjU7oMWO6qPh2Atcu7D5TwD71pH4TjnBOtfqUrmI22QRiremSB0HoO1WNXtlaI560
    3R1W3iIKne3qKh8rTTNo03TmmWZJDhQh5zznrj296bfBvIBzz+vFTRhXc7sgiq08zSTf7PaiKSXK
    TNc03UI4ZCeH6euKZdQmQZGCP1qwsJU5J+lMRBJLjPGax5eV3Om/PHlJbOEtBgdcVz+sWpiZkPQn
    v1rtdIt0kXAUYNc345sTb3vHQjAryMfdvmPqMlXLF0znXkSMAFscVGtgHkLZytMumMgCYwT/ADpE
    le3bGBkVxRi7N7Ho+xTldks0ghTABAzj8KtaTcpHqELZ6GqkhLW+WGDmoomEUwcHoeKzhK+jZUaf
    K20j3DStSik0+Pa3y4zTn1BQCQeK8+8M+NI5LZYhJ8yDGKu3nisRAruwT3FdEKi2PPrUG/iOvl1t
    HBG8cfzrNudZTee5zXHz+K2Y4BqOfxCZEznmm5S2GqCdtLs7NvFChQARx71XuNc3tuGAa4OfVpGc
    MCetLda5PsABYgelZQhyat3K9jzy1Wx2i6xtY5K8/pTZdeTcRkZIxiuBk8Qyl8DORznNLDqkkjYY
    gMfeuiNNN+0uS6PLeKidrHqwJ5IyDSvrQEgG6uMk1CSFxghs+/NF3qckaZ3fNilOX8hVLBvlOsm1
    oRS43DFMfxEu71AFchHqxkQ7mwaT+1yOxpdbkywzadkdiuvoSSTxSrq6MMluetcTPfSSgbSQPrSS
    am6DAJH409W7jp4TRSmjtW8Tp9xn4FJJ4kjCYLDNcLJeNu3bs5qFdVaSXaCeK0jDmWi2E6Mov1O1
    l1xGBwxyPWmHxCgGMfrXGza0wOACM96Fvy5wCefeibeiYoYLVnaJ4jURhQQPxqjPriySMrOOveuU
    lnkZsKTmoBOxY7zzUSjKL0Z0LBxqWjI6866sakbxs/SobvxGkigKSBXOKxEffH1pjA7sqM4/Ss4S
    m/iZnPDx5nCOxuT+JhGwHUkVXHiLcW28fjWI8vmOcjBFIAUJI71o5tR5UJYWN1M1rnxKzAHHTvUa
    eIXeTPpWaYTuyehoWHCHbzRzaJSLWEvNSaNabxM+zj73as3UNSmnZWJOT7UstsVjUjqabMAiiqi0
    ndI6nhIVLqexFb3JRySKfLPk+mfzpkFuysz4ypNK4E8oGcY/nVVal5oyWGhBWgrMZvAc8YNV5mad
    yAM1bNqvOajwFl471NJ2lqNYeKS5iKKBi21jjFOY+U3y9DxU7oAMjmmtbkENj5aUqd5XvuZujGL0
    W5G8fnIA2M/ypUbyY8d+lOa3IYsW4qQlViBIyaxcHpG+x0UIqzcdyrLbbhknr7VClkzOGarkf785
    6gVLs2kkjjtW6lb4jWthoVYq6Kf2TYDyBzUaWYlYseKurDuBJbr2pi2xD9eKt9Wmc8cOrqJVePyF
    GDnNS2aFsnPNStEG4boKdCiR5IbkVz16jceS5v7O0tBfsxlTk4xUfk7Tk9Vp4JD5BpWnDZBoow5F
    aJVuaXvFcRndkdjT5IGMfJp5nXawxSWr5BBHNTOKvdilRUpr8x1vJ5UO304piMN2fWpJEUEc/wD6
    6aEXNHslFadSp0o1I8r6BICy5zVVm2BgO9WlTjnpTJYxnApVUlCyQ/Yc6Vuhnpu34PGPapZMPHyc
    4ptwFR6dFEki8nnvzWUW7pozhGTTpkCgwnI+7SM3nK3HFMvW2uQh+WnRkrDjpkV0ppLnOe0V7jVz
    C1wBZipHIqot4UIH8IFaOvoCB/eH61jhcHnpTS5kc85ezqbaMW5vpI4tqng+1RzXmHwOQO5qW4IX
    B7Cid4/K5UbselS46WE3dtjIr5iOME4qG5dln8z0HSpoCvk5VTmo2g8zdvz7emKVOpZKLRpKm5rm
    uQpqTKxJxlvamvqEss4UcYpLgAuAMjHqKYJtsxJwSfUda0qOUveRFGXJFw7jboIj/PnJ/nUlixZx
    2A4/+uKJ4hOQScEd6SWJoivI+b07Gtoz51Znn+z9i+aK6k1zIY2+RvlPfNVZYzbx5z94fhU8q+TD
    jqelVLqcGEgdBXOvitE7alN25noVppflJJ4qPTpQpLFs4Ofw7VSurpAMbzx61We4MY3DjNepGF4H
    zta8KvMjWa7V3ODkdqSGfzEIIPH51mm9R4AM7WHeqzak0k+NxPlng++KrV6I6adKHKnJ7mheRKcu
    OGH5msK7AkIY8bTn/Cr73284yeB6VSm8sybSD0/SlQT+0YVqacrUylLqLOhI6g1Wa586IFiAQfTt
    V4WiysCB0qtqFnBasBk5I/DrXQ5Ju6WxzWlCS5nYo6+oks2ZDjI/KvM/EFt5kz7/AMK9N1UeTZHb
    8w28153rDpc3gwfmU1MJOE3K50aT9SppTCMLGT93Fei+CbjfAMj2rztJfKnbA6D8cc133hFwLYc8
    moqVG1dIupSV49DodR/eSKo+9t6+1FnbGOQEg5A/AU6G32NvbcpHTIqaGKSRvlbGR/8ArqoTsmjO
    tRfMpPfoWBqKAKkjc56VMtxDEdwPLVRltVtcbjuPQZpECLNls98fhStGNlHqKlRUtWtYmv8A2gJA
    MnoOBTIb4oSMEfTtVAIZDj7oHT3FPLF5Rl1bn8KlqzsaQ11e9yzd6sbVtir1PSlt5vNddxwR3qld
    wiSbcWziprVhM6A4yD+Vc1SbWxvh4e/bc6KxVyMdV96mutPTyxkkk/pUViMR7FPzL1q0rAkK3Ufn
    Xnyk29eh9FSoxUPUqCYWfyj/AOvVPUr77UMHgCtS7tUUhyoJrL1aNCjNnDCqo1Oaepz4qhKFH3Sl
    NeqvAPTikjv9mNxGBVK4RJY2Azk/zqCQsY2UqckYFesqcbK587TxU1JtfM111bzwXjOSvFEeou/z
    Dkis7TpI0TkYOPzqwzFcbBijlTVwqVpLTpuWBq+9SNqhgPxqGC6+Z2Peq8ilHHOKmaMvgqcJiqSS
    d2Y1ak57CW9+zTkZ4zV1IRGwIbr0qpHEiuSPX86tKu+NQOMGtFLd9zmdK9oy6ak7xGQ7nJI9KlNw
    08Z24wBj86ZPFlFwfmP5U+1BgZlxxWWqSZ6E6NrNrcdbzPHEo7E5+lIJftjsnQqalZsMD29MVIY4
    omBUckdhSm1K1gpRlFWRUEYS4VCzdecVanl8qHC4KjtSNbRPMG/i4JzUzQK4ULjC1nJXtY0pJwUu
    frsRaXKHf5RgjpWtqKs0C9cqKy7QCNye47AVpLc+fCwbhj0NTJu5NKSdJ9CiQ23rhgOKfZTNt+fI
    zUywYG5u3T600Qgkeh/Srg76SOWceSScdS1C6LCyMTg0xH3kcVIkKJArHOMcVCr734bGaUd7G9R6
    JNb9B1wrQo2OM0yzJTOOasW9k0/BbG01bi05YY2YnDH+dVKSV0ZU6Dm1JLYrW915UZDKSTzUtxD5
    smegFKLZCuSx61OXQAIO361nG0al4mqg5JxloitaAKSuBuq2DnCgUlukUbE7cY/WrAuIghwRuA/W
    rbbbuZUoqFmvQiUZc4GPWnJEXjDcgHtTi6qRz196mKnH+z/Sphd+9c2nDmVmU2tfNYqw4HSi2tAJ
    dgPT+dWoLlN5zjrSC5QXWRnp27VtHRu3YynH4e1y/bwKUI6cfjVWSwzKRnFWIryNYS5PzelRC8W4
    YnHSuNyqdDtVGErx" alt="Big Smile" />
    This method is mostly supported by most of the common email clients, including Outlook.
    Hope this better explains an alternate solution,

  • WAD template with BSP Application - how to read selection screen values

    Hello,
    I've created Web template with Web Application Designer (WAD).
    I would like to extend  that page with BSP Application...
    Purpuse of this application is to read some information from tables
    on BW transaction server and display them within Web page.
    Question: How to read selection screen values from a Web template ?
    Thanks for any help,
    Pawel Borowiec

    Hi,
    The selection screen parameters will be on an inputField, so try and get the is of the inputfield generated by doing View source...
    And once you get the inputfield Id, you can read the value in the InputField(InF) by
    using the following code...!
    data : if_value type ref to cl_htmlb_inputfield.
    data : variable type string.
    if_value ?= cl_htmlb_manager=>get_data( request = request
                                                name    = 'inputField'
                                                id      = 'InF_ID_here'
           if if_value->value is not initial.
             variable  = if_value->value.
           endif.
    Hope this helps.
    <b><i>Do reward each useful answer..!</i></b>
    Thanks,
    Tatvagna.

  • Error in viewing data in a data template with multiple data sources

    Hello,
    I have designed a data template with two data sources.One is from DEPARTMENTS table and the other datasource is a xml file.Following is the code for the data template :
    <dataTemplate name="EmployeeListing" dataSourceRef="demo">
    <parameters>
    <parameter name="p_DEPTNO" dataType="character" defaultValue="20"/>
    </parameters>
    <dataQuery>
    <sqlStatement name="Q1">
    <![CDATA[SELECT DEPARTMENT_NAME,DEPARTMENT_ID,LOC from DEPARTMENTS]]>
    </sqlStatement>
    <xml name="empxml" expressionPath=".//ROW[DEPARTMENT_NAME =$DEPARTMENT_NAME]">
    <url method="GET" realm="" username="" password="">file:///D:\OraHome_1\xmlp\XMLP\DemoFiles\Employee Salary Report.xml</url>
    </xml>
    /dataQuery>
    </dataTemplate>
    The problem is when i am trying to view the data, only data from SQL Query Q1 is getting displayed and the data from Employee xml is not at all getting displayed.
    Could anyone please let me know what i am missing?
    Thanks
    Nutan
    Edited by: user609971 on Oct 23, 2008 8:06 AM

    This is from Documenation sample....
    Did you see the data structure section, where you say, how you wanted the columns ?
    <?xml version="1.0" encoding="WINDOWS-1252" ?>
    <dataTemplate name="Employee Listing" description="List of Employees" v
    ersion="1.0">
    <parameters>- Defines a single parameter for the Department Number
    - with default of 20:
    <parameter name="p_DEPTNO" dataType="character"
    defaultValue="20"/>
    </parameters>
    <dataQuery>
    <sqlStatement name="Q1">
    <![CDATA[SELECT DEPTNO,DNAME,LOC from dept
                      order by deptno]]>
    </sqlStatement>
    <xml name="empxml" expressionPath=".//ROW[DEPTNO=$DEPTNO]"> - Defines name
    - and link to DEPTNO in Q1
    <url method="GET" realm="" username="" password="">
    file:///d:/dttest/employee.xml</url> - Defines url for xml data
    </xml>
    </dataQuery>-
    <dataStructure>- The following section specifies the XML hierarchy
    - for the returning data:
    <group name="G_DEPT" source="Q1"
    <element name="DEPT_NUMBER" value="DEPTNO" />
    <element name="DEPT_NAME" value="DNAME"/>
    - This creates a summary total at the department level based
    - on the salaries at the employee level for each department:      
    <element name="DEPTSAL" value="G_EMP.SALARY"
    function="SUM()"/>
              <element name="LOCATION" value="LOC" />
    <group name="G_EMP" source="empxml">
    <element name="EMPLOYEE_NUMBER" value="EMPNO" />
    <element name="NAME" value="ENAME"/>
    <element name="JOB" value="JOB" />
    <element name="MANAGER" value="MGR"/>
    <element name= "HIREDATE" value="HIREDATE"/>
    <element name="SALARY" value="SAL"/>
    </group>     
    </group>
    </dataStructure>
    </dataTemplate>

  • [Layout] Specify width with parameters

    Hi,
    I created some specific layouts using NWDS.
    Now, my requirements are to provide a solution to create new layouts (essentially, new values for widths between the various columns) in the Portal.
    As a solution, I tried to parameterize these values using component-profile and passed it to the jsp.
    It almost works since the ratios between columns are rendered as expected, but the parameters do not show up when I edit the layout in the PCD.
    Am I missing something here ??
    <%@ taglib uri="prt:taglib:com.sap.portal.reserved.layout.TagLibHtmlb" prefix="hbj" %>
    <%@ taglib uri="prt:taglib:com.sap.portal.reserved.layout.TagLibLayout" prefix="lyt" %>
    <%
    IPortalComponentRequest currentRequest   = (IPortalComponentRequest) pageContext.getAttribute(javax.servlet.jsp.PageContext.REQUEST);
    IPortalComponentContext componentContext = currentRequest.getComponentContext();
    IPortalComponentProfile profile          = componentContext.getProfile();
    String widthColumn1                      = profile.getProperty("com.mycompany.dyna_layout.column1.width");
    String widthColumn2                      = profile.getProperty("com.mycompany.dyna_layout.column2.width");     
    %>
    <lyt:template>
        <hbj:content id="myContext" >
            <hbj:page title="Portal Page">
                <hbj:gridLayout   id="GridLayout1"  width="100%" cellSpacing="2">
                    <hbj:gridLayoutCell rowIndex="1" columnIndex="1" width="<%=widthColumn1%>" verticalAlignment="top">
                        <lyt:container id="column1" />
                    </hbj:gridLayoutCell>
                    <hbj:gridLayoutCell rowIndex="1" columnIndex="2" width="<%=widthColumn2%>" verticalAlignment="top">
                        <lyt:container id="column2" />
                    </hbj:gridLayoutCell>
                </hbj:gridLayout>
            </hbj:page>
        </hbj:content>
    </lyt:template>
    Thanks in advance.
    Best regards,
    Guillaume

    Hi,
    Here is the portalapp.xml part :
    <!-- 2 Columns Dynamic -->
        <component name="Casino_2Col_Dyna">
          <component-config>
            <property name="ClassName" value="com.sapportals.portal.pb.layout.PageLayout"/>
            <property name="ResourceBundleName" value="pagebuilder_nls"/>
            <property name="SafetyLevel" value="no_safety"/>
          </component-config>
          <component-profile>
            <property name="ComponentType" value="com.sapportals.portal.layout"/>
            <property name="com.sap.portal.pcm.Title" value="Casino 2 Columns Dynamic"/>
            <property name="com.sap.portal.pcm.Description" value="Two-column layout with parameterized widths"/>
            <property name="com.sap.portal.reserved.layout.TagLibLayout" value="/SERVICE/com.sap.portal.pagebuilder/taglib/layout.tld"/>
            <property name="com.sap.portal.reserved.layout.TagLibHtmlb" value="/SERVICE/com.sap.portal.htmlb/taglib/htmlb.tld "/>
            <property name="com.sap.portal.reserved.layout.TemplateFile" value="Casino_2Col_Dyna.jsp">
              <property name="administration" value="NONE"/>
            </property>
            <property name="AuthScheme" value="anonymous"/>
            <property name="com.sap.portal.reserved.layout.Cont1" value="column1">
              <property name="administration" value="NONE"/>
              <property name="title" value="Column 1"/>
              <property name="orientation" value="vertical"/>
              <property name="designClass" value="prtlPageConL"/>
            </property>
            <property name="com.sap.portal.reserved.layout.Cont2" value="column2">
              <property name="administration" value="NONE"/>
              <property name="title" value="Column 2"/>
              <property name="orientation" value="vertical"/>
              <property name="designClass" value="prtlPageConR"/>
            </property>
            <property name="com_sap_webdynpro_mandatory_app_namespace" value="sap.com/pb_lyt">
              <property name="administration" value="NONE"/>
            </property>
            <property name="com_sap_webdynpro_mandatory_app_id" value="com.sap.portal.pb.layout.narrowwide.NarrowWideLayout">
              <property name="administration" value="NONE"/>
            </property>
            <property name="fr.group-dummy.dyna_layout.column1.width" value="38%"/>
            <property name="fr.group-dummy.dyna_layout.column2.width" value="62%"/>
          </component-profile>
        </component>
    Thanks.
    Best regards,
    Guillaume

  • Issue with using SSXA region templates with Content Presenter.

    I am using Content Presenter taskflow in Webcenter Portal. When i try to use the SSXA region template with content presenter, it doesnot render the html markup. But if i use normal UCM region templates(hscp), its rendering the html markup properly.
    Http Server acts as a proxy for both webcenter and ucm. Enabled SiteStudio, SiteStudioforExternalApplications, Webcenter Configure and other required features in Webcenter. Can any one tell me, if i missed any step?
    All i am getting the output as
    ${data.body}
    Taskflow binding
    <taskFlow id="doclibcontentpresenter1"
    taskFlowId="/oracle/webcenter/doclib/view/jsf/taskflows/presenter/contentPresenter.xml#doclib-content-presenter"
    activation="deferred"
    xmlns="http://xmlns.oracle.com/adf/controller/binding">
    <parameters>
    <parameter id="taskFlowInstId"
    value="${'23a55c99-abdd-4dea-a24a-1e04a68aa0bf'}"/>
    <parameter id="datasourceType" value="${'dsTypeSingleNode'}"/>
    <parameter id="datasource"
    value="${'UCM#dDocName:JLR_WYSIWYG_DATA'}"/>
    <parameter id="templateCategory" value="${''}"/>
    <parameter id="templateView" value="${'WYSIWYG_BLOCK_1_RGT'}"/>
    <parameter id="regionTemplate" value="${true}"/>
    <parameter id="maxResults" value="${''}"/>
    </parameters>
    </taskFlow>
    region template:
    <?xml version='1.0' encoding='UTF-8'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
    xmlns:wcm="http://www.oracle.com/jsp/wcm">
         <wcm:dataFile var="data"/>
         ${data.body}
    </jsp:root>
    This uses one region definition containing WYSIWYG element. I am able to edit and could type the html markup or data in WYSIWYG editor at contribution mode, but when i click save and close, all i am getting output as ${data.body}
    I manually verified the data file in UCM, and i could see the information stored (the data entered in contribution mode)

    Prasath,
    I'm not 100% sure but i believe that WebCenter does not support everything from the WCM tags. You can read the topic on SSXA on the WebCenter EMG:
    https://groups.google.com/group/webcenter-emg/browse_thread/thread/2ef9cca0252a0ae3
    Just a quote:
    "With the 11.1.1.4 release, WebCenter is very much targeted at the type of sites that would have previously been done using the WCM components (eg. Extranet, Internet sites). By surfacing the site studio region templates (and allowing in place editing of the documents) many of the use cases can be met. The question now is not whether,or not, the native templating + region support is sufficient for your needs (WebCenter does not support all the WCM artefacts as yet). "
    Regards
    Yannick

  • Calling subtemplate with parameters in footer

    Hi,
    I have the following syntax that calls a conditional footer depending on orgid and country:
    <xsl:call-template name="Super"><xsl:with-param name="organiz"select="ORG"/>
    <xsl:with-param name="country" select="BILL_COUNTRY_DESCRIPTION"/></xsl:call-template>
    This works great if I call it from a form-field but if I paste this code into the footer it does'nt get interpreted as xsl-code.
    Is there any way to work around this?
    Rg. Daniel

    By the way - you can call subtemplates with parameters using the short <??> notation in the real header.
    Edward our local guru gave me syntax:
    HEADER:
    <?call@inlines:aaa?><?with-param:name;string(‘edward’)?><?end call?>
    BODY:
    <?template:aaa?>
    <?param:name;string(‘Default Value’)?>
    Name: <?string($name)?>
    <?end template?>

  • Calling stored procedures with parameters with the Database Connectivi​ty Toolkit

    Hi all,
    I am new to the forum and am having difficulty finding a solution to a particular problem I am having regarding using the LabVIEW Database Connectivity Toolkit on a project I am currently working on at my job.  I have a database in which I have tables and stored procedures with parameters.  Some of these stored procedures have input, output, and return parameters.
    I have been trying to follow this example but to no avail:  http://digital.ni.com/public.nsf/allkb/07FD1307460​83E0686257300006326C4?OpenDocument
    One such stored procedure I am working on implementing is named "dbo.getAllowablePNs", which executes "SELECT * from DeviceType" (DeviceType is the table).  In this case, it does not require an input parameter, it has an output parameter that generates the table [cluster], and has a return parameter which returns an integer value (execution status code) to show if an error occurred.  The DeviceType table has 3 columns; ID (PK, int, not null), PN (nvarchar(15), null), and NumMACAddresses (int, null).  I have gone over many examples and have talking to NI support to try to implement this and similar stored procedures in LabVIEW but have not been successful.  I am able to connect to the database with the Open Connection VI without error, but am running into some confusion following this step.  I am then trying to use the Create Parameterized Query VI to call the stored procedure and set the parameters.  I assume I would then use the Set Parameter Value VI for each parameter that is wired into the parameters input on the previous Parameterized Query VI?  I am also having some confusion during and following these steps as well.  I would greatly appreciate any advice or suggestions anyone might have in regards to this situation as I am not a SQL expert.  Also, I would be happy to provide any more information that would be helpful.
    Regards,
    Jon
    Solved!
    Go to Solution.

    Also, I don't know if this would be helpful but here is the actual stored procedure in SQL:
    CREATEPROCEDURE [dbo].[getLastSequenceNumber]
    @p1 nvarchar(10)='WO-00000'
    AS
    BEGIN
    -- SET NOCOUNT ON added to prevent extra result sets from
    -- interfering with SELECT statements.
    SETNOCOUNTON;
    -- Insert statements for procedure here
    selectmax(SequenceNumber)from Devices where WorkOrderNumber= @p1
    END
    GO

  • I am changing from Word to Pages. I have created my custom template with all my styles etc and that is what comes up when I go for a New Document. Fine. How do I get it to use the same Custom Template when I use Pages to open a Word document?

    I am changing from Word to Pages. I have created my custom template with all my styles etc and that is what comes up when I go for a New Document. Fine. How do I get it to use the same Custom Template when I use Pages to open a Word document?

    The template is a document in itself, it is not applied to an existing document whether it is a Pages document or a Word document converted to a Pages document.
    You would need to either copy and paste content, using existing styles, or apply the styles to the converted Word document.
    You can Import the Styles from an existing document and those imported Styles can be used to override the current document's styles:
    Menu > Format > Import Styles
    The process is simplified if the styles use the same names, otherwise you will need to delete the style you don't want and replace it with the one that you do want when asked, then the substitution is pretty straightforward.
    Peter

  • Excel Template with Multiple Sheets

    Hi everyone,
    I need to build Excel template with multiple sheets where each sheet should have at-least one chart.
    Thanks
    Aravind

    Hi
    Could you please explain those ways here.?
    Many Thanks,
    BK

Maybe you are looking for