Template Selection Bug

In the Topic List POD, use CTRL+A to select all topics.
Choose a template and apply it to all... using the 'Apply'
button.
Wait for this operation to finish. When control comes back...
Press 'OK' and RH7.001.01 disassociates the template from
every topic.

While I am at it...
Template Bug #2: Template/Topic association is lost when
force update is invoked.
It'd be useful if we could 'Permanently Apply' a template to
all topics in a project and that association would persist through
all user activities.
A template applied to a project in this fashion should also
be applied to any new topics introduced to the project in any
manner whatsoever.

Similar Messages

Problem with xsl:import and xsl:apply-templates select="element_name"

I import a xsl tranformation into another xsl file.
During the transformation i want to limit the transformation to certain xml elements using the select attribute in apply-templates. However if I want restrict to xml elements whose templates are defined in the imported file, they will not be called.
I'm using currently JWSDP1.4 but problem was also with 1.3.
Can anybody help: Is this not xslt spec compliant or just a bug inXALAN ?
regards pszawlow

Solved it by myself:
the problem was not the import but the following:
xml file: looks like:
<a>
   <b>
   </b>
    <c>
    </c>
</a>xsl file looked like and should omit output of <c> </c>:
<xsl:template match="/">
<xsl:apply-templates select="b" />
</xsl:template>
<xsl:template match="b">
</xsl:template>
However / is not the level <a>, which I thought. So there was no matching <b>.
I changed the xsl file to:
<xsl:template match="/">
<xsl:apply-templates />
</xsl:template>
<xsl:template match="a">
<xsl:apply-templates select="b" />
</xsl:template>
<xsl:template match="b">
</xsl:template>
and it worked !

Form Template Selection

Hi,
Working on the Outgoing check form template. Tested looks fine in Test system. But When I tried the same template in the production it shows no template available for outgoing checks.
Even it did not allow to edit output settings options where can choose any other template.
For some reasons it doesn't show the form template for outgoing check at all even though Form template selection setup correctly.
Any idea why Payment Management - Payment monitor not showing the any template available for outgoing checks.
Thanks in advance.

Hi Vir,
Is this adobe form template If yes,
-go to WorkCenter "Application and user Management"->Utilities and look for the form template in the Form's OWL (I don't remember the subview name for the OWL). If you do not find any relevant active template, check active or deleted section.
If you delete the current active custom template, then it should automatically be replaced by SAP's default template for that use case , if any.
Let me know if this helped.
Regards,
Damandeep
Edited by: Damandeep Thakur on Dec 30, 2011 5:46 AM

Scenario selection in Template Selection tab of the Scope of a project

Hi All
I've just installed SolMan 7.0 EhP 1 and am creating a new project (with transaction SOLAR_PROJECT_ADMIN). In the Scope tab, under the Template Selection I can only find 1 Scenario to choose.
Under "Select one or more Scenarios", there is only the selection SISE_BC - Simplified Solution Manager Basic Configuration, that has 1 check box for the selection Basic SAP Solution Manager Configuration.
I was informed by a PM that there should be many more to select from. That I must have missed something in the set up.
My question is, How do I bring in all of the Scenario selections to choose from?
Ken

Hi
I think you need to map the scenario from BPR which comprises of all SAP standard scenarios or best practices
which can be done as shown below
https://websmp110.sap-ag.de/~sapdownload/011000358700002006042008E/HowTo_Impl_Bus_Proc.pdf
Hope prb solvd
regards
prakhar

How to define Template Selection Rules according to doc language code

hi All,
I am using ucm10g, I need to use DC to convert word to html, by defining Template Selection Rules, it worked perfect.
Question is I have to use different template for different content that use different languages, for example, if a content has a primary file writing in English, that content will be checked in with langCode attribute of "en", and according to this langCode attribute, I will use different template that will show "nextpage" or "previouspage" according to langCode field, other content will use other template that show "nextpage" or "previouspage" in other language.
I donot think the fields used in Template Selection Rules(such as author, type, profile) in ucm10g can be used in this case, any suggestion?
Best regards

I will ask easier.
is it possible to set in RSCUR -> Exchange rate type 'Y' and Exchange rate from InfoObject '0EXRATE_ACC' AND use it in BEx?
If yes, how, if now why?
Thank you
Standa

Template selection (Scope)

Hello Friends,
Everytime I create a project, I get default same scenarios template underneath scope tab. When I expand Select one or more scenarios, I get "BP_UTUS147 - Best Practices for Water Utility".It is suppose to give me list of scenarios.. right..?? how can I get the list of scenarios.
Ketan

Hi Kenny,
there might be a misunderstanding.
When you create a new project with "SOLAR_PROJECT_ADMIN", Tab "Scope" -> "Template Selection" shows the available Templates.
By accident, SAP has shipped the "Best Practises for Water Utility". So, you need first to create your own templates (projects).
It's explained in detail in help:
<a href="http://help.sap.com/saphelp_sm40/helpdata/en/1a/43c93a37c59122e10000000a114084/frameset.htm">Application Help: Implementation of SAP Solutions -> Projects -> Projects Administration -> Create/Change Projects -> Specify Scope</a>
Best regards,
Ruediger Stoecker

How do you change your intial bc template selection under site options after you click finish

how do you change your intial bc template selection under site options after you click finish

You cant. BC doesnt have a theming system like Wordpress or Joomla. The template is fixed and switching templates at this stage is not an easy feat.

Is there a way to automate template selection (EBS)?

Hi all,
The background to the question is this project, where there is a single language installation of EBS, but invoices need to be sent out in 20+ languages, including Chinese, Japanese and Russian. The invoices would often be printed in batches. Often a batch would include invoices in several languages. The printing steps from the user point of view, would need to be as simple as possible.
The data will be available in the respective languages, but how to manage the templates? Can the template selection be automated, so that the template is selected according to some specific value in the database?
I would be grateful for any information regarding this, for instance if there is any BI Publisher version that supports this. There are competing solutions too, and we are verifying whether BI Publisher would make a good choice in this setting. Thanks in advance!
Best Regards, Matilda Smeds

I'm not sure if I'm understanding garths comments correctly :-)
I'm on the fence about writing if statements for multiple layouts because there will be logic that is common for each country but it will be duplicated many times (long-term harder to support, short-term really fast dev)....
I have done an international implementation for customer facing documents myself and would recommend that you follow a similar methodology as suggested by garth but use imports for the templates (make multiple templates not the opposite).
I would suggest that you look at the Blanket Sales Agreement as an example on how to do this. There is no reason to create a massive template that repeats the same logic.
Sample Call:
<?if:SEND_COUNTRY='US'?>
<?import:xdo://ONT.ONTBSAERTF.en.00/?>
<?end if?>
Modularity will be key so I would suggest you also use call-template and call-inline-template tags as well. You will find that each country will have wild and erroneous nuisances that you will have to code for and that's why I'm suggesting you use this strategy. Conceptually, think about your templates like a class and java extending another class. Setup the inheritence correctly your life will be much easier. Make sense?
Good luck with the invoices.
Ike Wiggins
http://bipublisher.blogspot.com

Tree selection bug?

Hi,
I don't know if this is a bug or not. When using XML as the
data provider for the Tree component and multiple nodes have the
same label, selecting anyone of the nodes will cause all of them to
be selected. The problem stems from the fact that XML comparison is
done by value. The comparison is dibe at line 6345 of ListBase. Is
this a bug? If not, is there a known workaround?
I attached code that reproduces the problem. Selecting the
first node, selects the first, second and last node because, by
value, they are all the same.
Thanks!
JPB

Switch to using a strongly typed object that implements IUID,
or just make
sure your XML has other identifying information to it. It's
not really that
helpful to have 19 "foos" in your list unless there is
something else
different about them.
So, something like
<mx:XMLList id="treeData">
<node label="Test entry 1" id="1"/>
<node label="Test entry 1" id="2"/>
<node label="Test entry 2" id="3"/>
<node label="Test entry 1" id="4"/>
</mx:XMLList>
HTH;
Amy
"jpbouchard" <[email protected]> wrote in
message
news:g941f3$1u8$[email protected]..
> Hi,
>
> I don't know if this is a bug or not. When using XML as
the data provider
> for
> the Tree component and multiple nodes have the same
label, selecting
> anyone of
> the nodes will cause all of them to be selected. The
problem stems from
> the
> fact that XML comparison is done by value. The
comparison is dibe at line
> 6345
> of ListBase. Is this a bug? If not, is there a known
workaround?
>
> I attached code that reproduces the problem. Selecting
the first node,
> selects
> the first, second and last node because, by value, they
are all the same.
>
> Thanks!
> JPB
>
> <?xml version="1.0" encoding="utf-8"?>
> <mx:VBox xmlns:mx="
http://www.adobe.com/2006/mxml"
width="100%"
> height="100%">
> <mx:Script>
> <![CDATA[
> import mx.controls.Tree;
>
> private function selectFirst(): void {
> myTree.selectedItem = treeData[0];
> }
>
> ]]>
> </mx:Script>
>
> <mx:XMLList id="treeData">
> <node label="Test entry 1"/>
> <node label="Test entry 1"/>
> <node label="Test entry 2"/>
> <node label="Test entry 1"/>
> </mx:XMLList>
>
> <mx:Panel title="Tree Selection Bug" height="100%"
width="100%"
> paddingTop="10" paddingLeft="10" paddingRight="10"
paddingBottom="10">
> <mx:Button label="Select First"
click="selectFirst()"/>
> <mx:Tree id="myTree" width="100%" height="100%"
labelField="@label"
> showRoot="true" dataProvider="{treeData}"/>
> </mx:Panel>
>
> </mx:VBox>
>

[svn:fx-trunk] 13362: List mouse click selection bug fix

Revision: 13362
Revision: 13362
Author:   [email protected]
Date:     2010-01-07 17:22:41 -0800 (Thu, 07 Jan 2010)
Log Message:
List mouse click selection bug fix
SDK-24963 - Mouse click is ignored by List if allowMultipleSelection="true" in some cases
Updated setSelectedIndices to perform the single index equality check if selectedIndices has only one index.
QE notes: None
Doc notes: None
Bugs: SDK-24963
Reviewer: Ryan
Tests run: checkintests, List
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24963
    http://bugs.adobe.com/jira/browse/SDK-24963
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as

Switching between Acrobat DC / XI window and another application - cursor selection bug (video and test files attached)

Hi,
When I have Acrobat XI or DC open along side InDesign (or other programs like Acrobat or Word), I run into a bug where upon switching from InDesign to Acrobat, the mouse cursor automatically selects a bunch of text in the Acrobat PDF with a spinning beach ball, and I have to click around multiple times to release it from whatever text it has selected. It is annoyance I noticed in a few versions of Acrobat now, and I had hoped the bug would be fixed in DC. The only way to prevent this from happening is to click anywhere else on the Acrobat window (eg the menu bar or the side tools panel, but not the PDF itself).
Video describing the problem: https://imgur.com/dXurXcB
Note that no clicking is taking place when switching windows from InDesign to Acrobat - the text in the Acrobat window is being selected automatically by the bug.
If you watch the video carefully, you will also notice that the Acrobat window does not look like it is taking focus during the selection bug - it only takes the focus after clicking around multiple times.
Test documents used to record the video:
http://s000.tinyupload.com/?file_id=14619964329420357364
InDesign CC File
http://s000.tinyupload.com/?file_id=18294837115907237178
PDF File
Computer:
Model Name: MacBook Air 2013
Model Identifier: MacBookAir6,2
Processor Name: Intel Core i7
Processor Speed: 1.7 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB
OS: Yosemite 10.10.1

Thanks for the reply. I think the issue is just confined to Mac machines + Adobe products (this issue doesn't occur when I switch from Word Preview 2016, or Office 2011). I can confirm this issue occurs on more than one Mac as well.
Here is a slightly larger GIF if the first was too hard to make out
https://i.imgur.com/CNKnkC0.gif
It's almost as if the text manipulation / selection from InDesign is carrying over to the Acrobat window, interrupting the normal focus it should get on first click...
Edit: It just occurred with Spotify - Switched from Spotify to Acrobat, with a scanned image PDF. The rectangular selection tool tries to grab a region of the image several times before focus returns to the Acrobat window. It also just happened after manipulating images and text in Word 2016 Preview and Word 2011.

May Release: New partner support, Infrastructure updates, Site templates and bug fixes

Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
Partner support
Infrastructure updates
Features and enhancements
Issues fixed by this release
What's next
You can jump to the corresponding section by clicking the above links.
Partner support
Updated Help & Support partner experience
Following Adobe ID support, we have upgraded BC support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
Support experience for your Small Business owner clients can now be owned by partners (see below).
Custom Help & Support URL for your clients
As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
For more details please read the Improved support workflow and new forums announcement on our blog.
Infrastructure updates
Between our April release and the following infrastructure updates have been enabled
Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in the system through the admin interface or through FTP.
Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.
Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
Features and enhancements
Site templates
To support the increasing number of partners building, sharing or reusing templates to create new sites, we're extending our site templates support from our partner portal with a new template type and improved management support. The update is going to enable partners to mark sites as templates and choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
Business Catalyst Partner fixes
While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
Social plugins integration updates
Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will update the module template to include the corresponding module code snippet from the third party platform provider.
For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
Other changes
Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
BC-Dreamweaver integration performance improvements
Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
Issues fixed by May release
Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
Issue 3162810 - Fixed a bug in rendering engine to prevent content placed between body and head tags being incorrectly moved inside the body tag
Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
Issue 2947989 - CRM passwords are now case sensitive
Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
Business Catalyst new admin interface updates
Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
Updated the confirmation message received after copying a page to match the new workflow and button names
Fixed an issue causing the current screen or section to not be highlighted in the menu
Updated styling on the new dashboard, user management and email accounts interfaces
Updated dashboard reports filters and chart display; made the chart and the filter use the site time zone
Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
Fixed some issues preventing password recovery email from being sent
Removed the alert message displayed when the user or email account limit has been reached
Added localization for the simplified dashboard
Fixed display issues for site limits, domains and user list in the simplified dashboard
Added Custom reports for webBasics plan
Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
Added TOU checkbox in the email account setup screen
Updated Site Preview link in the dashboard to load the default domain
Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
Fixed a broken invite link issue in the Email Account invite email
Updated loading indicators in File Manager and Email Accounts screens
What's next
The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever.
We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

Strange Behavior In Defining A Template Interface -- Bug/RFE

Hello.
This is a bit of a bug. I wanted to define a "template" interface. If you follow this sequence of steps, you may see this odd behavior:
In a class diagram, insert a new Interface.
Add a template parameter to that interface. Now, the display of the object has not changed.
Right-click the interface, and under "Show", select "As Icon".
Right-click again and under "Show" select "As Non-Iconic Class".
Now the interface is displayed as a "Template Class" on the diagram, with its parameters visible. This comes about since the Modeling Palette only contains a tool to draw a "Template Class", which creates a class only and not an interface.
Is this behavior somehow intentional or expected?
Is there any bug reporting tool for such reports? Or is posting on this forum sufficient to constitute feedback on a bug?
Thanks in advance.
- Steven Coco.

Hi.
I am not aware of another notation: the display given by JSE (after making it display the parameters) is all I would expect -- the UML superstructure just says that a templatable element has the dashed-outline box listing its parameters. Now, the display of the parameters can be suppressed, but I would have expected in that case a more direct "Hide or Show Template Parameters" option for the element. And in fact, I'd say that a display option like this is really what this boils down to: there's no option to hint JSE to display the parameters; and you'd have to go a round-about fashon to make them appear.
And my display does still show <<interface>> after geting the parameters to appear.
Thanks!
- Steev.

XML Publisher Template Selection Dynamically

Hi All,
I am new in XML Publisher domain and currently working on a report and I am able to generate EXCEL and PDF output using following steps.
STEPS
1.     Create RDF Report
2.     Register as Executable and Created Concurrent Program WITH XML Output
3.     Create RTF Template for PDF format
4.     Create RTF Template for EXCEL Format
5.     Register Data Definition (Concurrent Program short name is same)
6.     Register Template 1 (Default type PDF and uploaded PDF template file)
7.     Register Template 2 (Default type PDF and uploaded EXCEL template file)
8.     Running the Report using FND Request Submission form
a.     In Options Default is coming as EXCEL (only one template)
b.     Change template to PDF generates PDF output
c.     If added both the template another concurrent Program submitted (XDO) to generate both the outputs.
I have few questions
*1.* When I am submitting concurrent program how this form/concurrent program identifies default TEMPLATE (Excel or PDF)?
*2.* I have one parameter in RDF to determine which layout I have to use (Dynamically)
I found one procedure FND_REQUEST.ADD_LAYOUT to change the template code dynamically but this is not working (I tried this code in Before and After Report Triggers but without any luck)
I don’t want to submit another request (1 default present in OPTIONS tab and one from AFTER Report Trigger)
Using ADD_LAYOUT followed by FND_REQUEST.SUBMIT (XDO one to submit another request)
My interpretation of ADD_LAYOUT procedure is
This procedure set the package global (session) variables which are used by FND_REQUEST to identify template code and run XDO concurrent program to generate the actual output. But, when I submit the changes it picks template details from OPTIONS tab so ideally when I used this procedure OPTION tab values should change as per my selection? How can I change OPTIONS TAB values? Is it possible?
It will be a great help if someone can explain me how can I achieve this result.
Thanks & Regards
Sachin

You have another option which you can consider for this scenario.
Have a single RTF template and attach this to data definition.
Let this RTF conditionally choose the layout based on the input parameter.
i.e.
<?if:param1='PDF'?>
PDF layout
<?end if?>
<?if:param1='EXCEL'?>
EXCEL layout
<?end if?>

Workaround for JSFL shape selection bug?

There seems to be a bug in the document selection reporting in JSFL in CS4 (haven't tested earlier versions). I submitted it as a bug to Adobe but I'd really like to find a workaround for it. I've included my bug report below. Has anyone else encountered this? If so, have you figured out a workaround? It's pretty annoying, making the tool I'm working on really difficult to manage.
******BUG******
After performing a publish preview, fl.getDocumentDOM().selection reports an incorrect selection of raw shapes.
Steps to reproduce bug:
1. Create a JSFL command with the following contents:
doc = fl.getDocumentDOM();
fl.trace("there are " + doc.selection.length + " items selected");
2. Start the authoring environment fresh, with a new document.
3. Draw several shapes on the stage, not touching each other, all in the same frame and layer.
4. Select one of those shapes but leave the others unselected.
5. Run the previously created JSFL command. It will send the following text to the output panel, as one would expect:
"there are 1 items selected"
6. Do a publish preview (either Flash or HTML).
7. When it comes up, close the preview window.
8. Deselect all and then select one of the shapes (again, keeping the others unselected).
9. Run the JSFL command again. This time, it will say that there are n items selected (where n is the number of shapes you drew in step 3). So if you drew three shapes, it will print out the following:
there are 3 items selected
Note that this result will be the same even if you go to a different document, do a publish preview on that document, then return to the original. It seems that simply doing a publish preview alters Flash's state to report the selection incorrectly.
Results: The JSFL command reports that all the shapes are selected, despite the fact that only one of them is. The only way I've found to get Flash back to its normal behavior is to restart the authoring environment.
Expected results: In the steps above, the JSFL command should always print out that there is one element selected. There's no reason that doing a publish preview should change that.

When selected all shapes in selection are treated as one. You can see it if you run this script with selected multiple shapes:
fl.trace( fl.getDocumentDOM().selection[0].contours.length );
It will output you twise bigger number then selected shapes (because each Shape has two contours - one clockwise, other counterclockwise).
Of course this. implementation is strange for me too. Thats how i found your post

Template Selection Bug

Similar Messages

Maybe you are looking for