We are creating Drill Down reports (.fex files) to run from summary reports which are embedded in HTML files. When we go to save the HTML for the summary report, an extra tag appears to be automatically inserted at the end of the HTML. That tag ends up referring to an APP PATH for the test environment and, if we don't catch it, it ends up that way in production. Where is that extra tag coming from and why? Is there something we can do to keep it from being created? Or if it has to be created, how can we get it to automatically refer to the proper APP PATH, short of looking for it and changing it?

Thank you!

Hi Paul,

Has this issue been resolved on your side?

Can you please paste a sample code that you are using? Also, can you please go into your profile and update your signature to show what WebFOCUS release you are on, what web/application server you are using, what tool(s) you are using, i.e. Dev Studio, MRE, or Dashboard, and what the output format(s) are?

Thank you in advance for sharing.

Cheers,

Kerry

I apologize for not posting a code sample, but I can't get HTML code to post. I'm new to these forums and to dealing with HTML in general. Is there some trick to getting the HTML code block to display in the post?

Thank you!

Select Options, then check Disable HTML...

or

I think you can place between <code> </code> tags...

Doing a global change so less-than becomes amperLT; and greater-than becomes amperGT;
(where amper is & ) should also work.

Here is the code sample. It is from the end of the HTML.

One additional thing I wanted to mention is that this is Parameterized Drill Down report. The variables section is just above the line of code in question. I have tried to BOLD that line.

Also, "Birdsall_Security" is the name of the project in our development environment.

Please let me know if you have any insight into why it is there, and what we can do to prevent it, if anything.

Thank you!

(I have changed the brackets around the code tags...)

[/variable]
		
[/variables]
	
[/request]
	
[request requestid="1" sourcetype="typeHtml" targettype="1" targetname="_parent" ibif_ex="ReportSelectionMenu.html" ibic_server="" ibiapp_app="Birdsall_Security baseapp"] 
[/request]
[/requests]
[/xml]
[/BODY]
[/HTML]

If you add a report there will be a new request tag and it will reflect the apps in use.

I am guessing you are not concerned about the request tag as much as it's reference to your test application.

You have a couple choices: First off, use a test system that uses the same app structure as production. You can add projects to the test system - but add them using the existing applications. HTML files created this way can be moved.

Secondly, if test apps names do not match production, you can create a DEPLOY scenario that will map your files to where they should go in production. Then when you deploy, the ibiapp_app parameter will be updated to reflect what is needed in production.

Thank you, Brian. We're going to look into the DEPLOY scenario. We appreciate the feedback.