I am creating HTML in a fex using HTMLFORM BEGIN. In the HTML I am trying to reference JS file located inside a content folder. I have tried several ways. The file is not reading during the execution. Any ideas? Thanks in advance.

This message has been edited. Last edited by: Kathleen Butler,

quote:

Originally posted by WFConsultant:
I am creating HTML in a fex using HTMLFORM BEGIN. In the HTML I am trying to reference JS file located inside a content folder. I have tried several ways. The file is not reading during the execution. Any ideas? Thanks in advance.

I've never been able to get that to work from a content folder. I put my JavaScript files on the reporting server (EDASERVE for me) and access like this:

    <script type="text/javascript" src="/ibi_apps/approot/balanced_scorecard/common/js/scorecard.js"></script>

My content folder in this example is "balanced_scorecard", so there is a corresponding folder of the same name on the reporting server (With subfolders "common" and "js" in this example).

Thank you Squatch. The JS file in the content is widely used by many reports. I cannot move it to the reporting server. It will be lot of work.

quote:

Originally posted by WFConsultant:
Thank you Squatch. The JS file in the content is widely used by many reports. I cannot move it to the reporting server. It will be lot of work.

It looks like if you are using App Studio to develop an HTML application, you can specify that you want to use a JavaScript file in the Content area. But if you are using "-HTMLFORM" in a procedure it doesn't seem to work.

I think the reason for this is because files in the Content area are actually stored in a database, and App Studio creates the necessary mechanism to access these files when creating an HTML application. Outside of App Studio, it appears we are out of luck and have to use the Reporting Server to house JavaScript/CSS files.

If anyone has information to the contrary, I'd love to hear about it!

quote:

Originally posted by WFConsultant:
Thank you Squatch. The JS file in the content is widely used by many reports. I cannot move it to the reporting server. It will be lot of work.

But you could make a copy of the file and put it on the Reporting Server, couldn't you?

Time for me to drop in and come to the rescue! haha

It is totally doable. Use this syntax/URL build:

<link type="text/css" rel="stylesheet" href="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/appDirectory/Hidden_Content/styles/tablesaw.css">
<script src="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/appDirectory/Hidden_Content/scripts/tablesaw.js" type="text/javascript"></script>

You can also call libraries from a CDN. :-)

Hope this helps!

quote:

Originally posted by CoolGuy:
Time for me to drop in and come to the rescue! haha

It is totally doable. Use this syntax/URL build:

<link type="text/css" rel="stylesheet" href="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/appDirectory/Hidden_Content/styles/tablesaw.css">
<script src="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/appDirectory/Hidden_Content/scripts/tablesaw.js" type="text/javascript"></script>

You can also call libraries from a CDN. :-)

Hope this helps!

It definitely helps, CoolGuy! This is something that has been driving me nuts for some time now. Thank you very much.

This is why coders will still be required for a while yet!

Understanding the construct of the output and how you can effect a change, is one measure of a developers worth!

Another is being able to apply that change using the architecture available to you.

T

quote:

Originally posted by Tony A:
This is why coders will still be required for a while yet!

Understanding the construct of the output and how you can effect a change, is one measure of a developers worth!

Another is being able to apply that change using the architecture available to you.

T

Agreed.

Although I must admit that I haven't been able to get CoolGuy's example to work yet.

I'm assuming I'm doing something wrong at this point, however.

Squatch,

Can you post your code so we can take a look at it? Wondering if you've got it in the right spot or not. This works for us without a problem.

Thanks.

quote:

Originally posted by CoolGuy:
Squatch,

Can you post your code so we can take a look at it? Wondering if you've got it in the right spot or not. This works for us without a problem.

Thanks.

-HTMLFORM BEGIN
<!DOCTYPE html>
<head>
<script src="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS:/WFC/Repository/balanced_scorecard/Common/js/scorecard.js" type="text/javascript"></script>
</head>
<body>
Test
</body>
</html>
-HTMLFORM END

I've confirmed the path by going into the WebFOCUS web interface, right-clicking on the JavaScript file and selecting properties.

The error I get is "Method Not Implemented". This is different from the error I get if I make the path wrong. In that case, it's just a "File Not Found" error.

Thanks for the help, it's appreciated.

If I use the debugging ability in the Chrome browser, the error I see is "Uncaught SyntaxError: Unexpected token <" at "WFServlet.ibfs:1".

Change &|IBFS:/ to &IBFS_path=/.

Squatch,

try this:

 
-HTMLFORM BEGIN
<!DOCTYPE html>
<head>
<script src="/ibi_apps/run.bip?BIP_REQUEST_TYPE=BIP_RUN&|BIP_folder=IBFS:/WFC/Repository/vesir218/others&|BIP_item=alert.js" type="text/javascript"></script>
</head>
<body>
Test
</body>
</html>
-HTMLFORM END

 

PS.: change path to fit yours!

quote:

Originally posted by CoolGuy:
Change &|IBFS:/ to &IBFS_path=/.

Sorry, CoolGuy, the code I posted above had a copy and paste mistake in it. It is now:

-HTMLFORM BEGIN
<!DOCTYPE html>
<head>
<script src="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/balanced_scorecard/Common/js/scorecard.js" type="text/javascript"></script>
</head>
<body>
Test
</body>
</html>
-HTMLFORM END

And it works! But when I use the browser's debugging facilities, there is this error: "Uncaught ReferenceError: $ is not defined". However, the JavaScript file starts with a JQuery command, which I think causes the confusion because it does begin with a dollar sign.

(I must have the "&|" in there or App Studio interprets it as an ampersand variable and throws a screen full of errors.)

Thank you so much!

WFConsultant, CoolGuy has answered your original question.

You do something like this:

<script src="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/balanced_scorecard/Common/js/scorecard.js" type="text/javascript"></script>

I have confirmed that this works.

If your referenced JS file uses jQuery, you need to reference the jQuery library as well.

Yes. I just happened to test on a JavaScript file that had JQuery in it.

It did load, though, and that was all I was trying to accomplish.

... and so the coders conquer again.

Gives you a nice warm fuzzy feeling, doesn't it

T

Thank you all for contributing with great ideas. Going by same notation, can we include a CSS file in the content?

You can.

Example:

<link type="text/css" rel="stylesheet" href="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/appDirectory/.../styles.css">

quote:

Originally posted by CoolGuy:
You can.

Example:

<link type="text/css" rel="stylesheet" href="/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&|IBFS_path=/WFC/Repository/appDirectory/.../styles.css">

Is there an online place where all these "WFServlet.ibfs" parameters are documented? Or do you just have to be part of the "in crowd" to gain this knowledge?

Here's the not-too-helpful docs article for it (at least what I could find):

WFServlet doc

I came across the repository syntax string/build from some IBI developed code in the Responsive Demo CM package we acquired last year. Lots of good undocumented ways to work with WF content in there.

quote:

Originally posted by CoolGuy:
Here's the not-too-helpful docs article for it (at least what I could find):

WFServlet doc

I came across the repository syntax string/build from some IBI developed code in the Responsive Demo CM package we acquired last year. Lots of good undocumented ways to work with WF content in there.

Thanks for the info!