I am tinkering with the Auto Amper Param templates. I have copied the two autoprompt_top template files:
autoprompt_top.xsl and autoprompt_top.css

TO:
autoprompt_top_ABC.xsl and autoprompt_top_ABC.css

I have changed my report to specifically use this template with the following code:
-autoprompt_top_ABC

I have then made changes in the XSL and CSS files (changing font sizes and graphic files). When I run the report, I don't see any changes. When I VIEW SOURCE of the report in IE, I see this: "< !-- Created with $Revision: 1.11 $: of autoprompt_top.xsl-->"

I changed that line in the .XSL file to say "autoprompt_top_ABC.xsl-->" in that comment.
So its like its not seeing my changes or using my *ABC.* files.

So then I changed this line in the report
-autoprompt_top_ABCDEFGH
the *ABCDEFGH.* files don't exist.

When I run the report, it does not work and gives me this error:
"Report has been deleted from the server. You must run the report again if you want this report"
so that tells me that it is trying to retrieve the file I specify in the - statement.
I also set the default value of IBIF_describe_xsl to be autoprompt_top_ABC in the WF Admin Console.

Anythoughts on why I am not seeing my changes I put into the XSL and CSS files?

This message has been edited. Last edited by: Scott W.,

APP PATH? MRE Folders? What release, etc? What do you expect the "-autoprompt_top_ABC" to do? Where did you put that?

Why not just build a Launch Page (HTML Composer)?

[QUOTE]Report has been deleted from the server/QUOTE]

This usually means that the agent crashed.

You may have to use tracing to find out what happened.

WebFOCUS Managed Reporting Developer's Manual > Creating Launch Pages and Publishing Reports > Working With Amper Auto-Prompting

quote:

The option to select different launch page templates can be set in the WebFOCUS Administration Console using the Parameter Prompting selection under Client Settings, where you can set the IBIF_describe_xsl value to one of the launch page templates.

You can also enter the name of the desired launch page template in a FOCEXEC using the following code:

template

quote:

Originally posted by Doug:
APP PATH? MRE Folders? What release, etc? What do you expect the "-autoprompt_top_ABC" to do? Where did you put that?

Why not just build a Launch Page (HTML Composer)?

I am doing this to see how flexible these templates are and if it will accomodate our needs, or if we need to move on to launch pages. Things like display company logo .GIF files, make the multi-select input boxes display more than only 4 lines within them, things like that. We are brand new customers and the WF MR Dev manual has a chapter on customizing these templates. Instead of messing with one of the out-of-the-box templates, I thought I'd clone it and play it safe.

Plus the documentation points out the templates affect all the reports, as opposed to having to have a launch page per report. I am not opposed to launch pages, just trying to understand our options.

I put the files where the current template files are, in
\ibi\WebFOCUS76\ibi_html\javaassist\ibi\html\describe\

WF 7.6.9

quote:

Originally posted by Francis Mariani:
WebFOCUS Managed Reporting Developer's Manual > Creating Launch Pages and Publishing Reports > Working With Amper Auto-Prompting

quote:

The option to select different launch page templates can be set in the WebFOCUS Administration Console using the Parameter Prompting selection under Client Settings, where you can set the IBIF_describe_xsl value to one of the launch page templates.

You can also enter the name of the desired launch page template in a FOCEXEC using the following code:

template

Yes, this is exactly the documentation that lead me to trying what I am trying.

Scott,

Have you ensured that you have cleared your local cache (if using I.E.)?

From IE, choose Tools/Internet Options/Delete Files.

I have my cache set to a very low amount and have set options to refresh every visit, but I still have to clear the cache when I am changing js, css, xsl files etc.

As for auto prompting files, I have created a "mimic" that uses most of IB's files (I had to "extract" some of the code elsewhere) but is modular, in as much that for each new variable you just add another section. It allows some other form controls that "normal" amper autoprompting doesn't, such as radio buttons.

I created these as the level of HTML exposure here wasn't that great and it made creating launch pages so much easier for them. They still rely upon amper autoprompting for "run of the mill" stuff, but when they need to take it further my version suffices and the end users see no real difference.

T

quote:

Why not just build a Launch Page (HTML Composer)?

that makes sense... I see that the others have given some very valuable insight... Go Fo it...

Clearing the cache did not take care of it. Too bad as I was hoping it was only that. I forgot that I have had to do that for other non-WF browser based apps I've changed in the past.

Like I said, I am "tinkering" so I don't want this to take too much time. I have backed up the \ibi\WebFOCUS76\ibi_html\javaassist\ibi\html\describe\ directory so that I can always restore the files I change. I will just make changes to the autoprompt_top CSS and XSL files and see what all I can do with it.

Launch pages are probably going to be the solution for our needs, but if I can make the Autoprompt pages closer to what we need with a minimal amount of effort, I want to know that option is available.

I am a veteran .NET/browser based app developer, but a n00b with HTML Composer. So that is another reason why I want to try working with what I am already familiar with.

Thanks everyone for your input on this one.
Scott Waller.

To reiterate what Doug said, even though you are more familiar with other tools, in the long run you will be farther ahead with the HTML Composer as you continue to use the product. If you continue down the path you are on, you will have to redo all of it with each new release you upgrade to. You might be better off creating a 'template' page that can be imported into the HTML Composer each time a new launch page is created. This template can have your look and feel or corporate standard as it were.

The HTML Composer is very easy to learn.