This is just out of curiosity, but does anyone know why the app path needs to be specified in the code of HTML Composer, even though it is already associated with the domain?

Thanks!
Melanie

This message has been edited. Last edited by: Kerry,

MRE domain I guess ?

The issue there is that I don't think that path is passed to FOCUS, may be wrong. Also if you have the path in the code you can change it to what ever you want.

Yes, MRE domain. Thanks for your input!

Not sure what you are saying. You should not have to add it when building the HTML page. If the page was served up from a domain, the subsequent interactions back to WF Client are in the "execution environment" of that domain. If that is not working, then please provide a more detailed description.
The composer only writes IBIAPP_app when the page was developed under dataservers or local projects.

Every HTML Composer file I've ever seen has app references in the code, similar to: ibiapp_app="edw_sellthru_dev". HTML Composer puts it in the code automatically. I'm not having any problems. My team is just wondering why, if the app path is already specified by the domain, it needs to put it in the code also.

because you can reference any app you want from an html page, mutliple apps per page, if you want. think 'dashboard', your bits in a dashboard , especially a dashboard built on 'the back end', could come from a whole bunch of apps.
so the same theory is replicted when you build an html page on the 'front end', eg MRE;
EG: if your site has its own portal software, then you'll want to write your htm pages , fexes, on 'the back end', eg in the apps directories.

That makes sense. Thanks for your answer!

Melanie

Pages in the MR space do not have any application directories written in the HTML.

quote:

Every HTML Composer file I've ever seen has app references in the code, similar to: ibiapp_app="edw_sellthru_dev".

The above is what I've been referring to, and is copied directly from the code of the HTML composer. Perhaps you are thinking of something else. But I believe susannah gave me the answer I was looking for.

A hidden variable named IBIAPP_app is always written to the page, however when in the MR area, it does not contain any app folder references. Instead it contains ismre=1, which means the page is in MR, and will therefore obtain the app folders dynamically from the MR properties.

quote:

ismre=1

Good info to know.