Hi,

When i call a maintain module from a report in our dashboard (which we open within our dashboard not in a seperate window - as our client requested ) , i can't use the back button anymore , cause when i click on it it states "disconnected from server" , and just refreshes the maintain module ...

Is there anyway i can get control over the back button back.

Any ideas anyone .....

Pete,

Just so that the issue isn't confused (as is always the case when someone mentions "dashboard") could you confirm that you are talking about a Self Service app and your own "dashboard" and not the IB one?

I ask this, not because I know much about maintain (we'll leave that to the wizard ) but more in an effort to ensure that the replies do not go around the houses because of a misunderstanding about the term "dashboard".

T

Hey T.,

Its BI Dashboard , the one and only

P.

Hi Pete,

Are you opening it within a content frame or a new page?

T

T.,

we open the maintain module in a content frame

basically , we use one page with two blocks ,
one list block
and one output block

the maintain module opens in the output block


P.

By default, persistent Maintain procedures that are abruptly disconnected from server (for example: by browser Back button, Back Space key, F5 key, closing browser window, etc.) will yield “This application has been disconnected from server”. As of version 5.3.4 and 7.1.1, the warning message can be disabled by a simply MNTCON command in the server profile. See feature description below.

How to Disable the Disconnect Message When Closing a Browser

By default, the exit message ‘This application has been disconnected’ appears when a browser session containing an active Maintain application is closed. To control the display of this exit warning, place the following statement in the server profile file, edasprof.prf, or in individual user profiles



MNTCON EXIT_WARNING {ON|OFF}

where:
ON
Enables the display of the exit warning, This application has been disconnected, when
an active Maintain browser is closed. ON is the default value.

OFF
Disables the exit warning that displays when an active Maintain browser is closed.

Hi Wizz,

the problem is that we are on 5.3.3 ....

This WAS a new feature in 5.34. The only thing you could do is open a case with Customer Support and maybe we can back port the feature for you.

One thing ....


Does this new feature , give me back the back button functionality , meaning will i be able to go back to previous reports from which the maintain module was called ?

This feature only disables or enables the disconnect warning message. But in general when browser Back button is clicked it should return to the previous page, in your case back to the report.

I just tested your scenario in 533. In fact, hitting the Back button returned me to the Table report that called the Maintain. Here are my steps, let me know how it differs from yours.

1) Logon to BI Dashboard.
2) Run a standard report that contains a drilldown to Maintain procedure, MNTIVP. The report is displayed in the Output block/frame on the right-hand side of Dashboard.

TABLE FILE CAR
PRINT MODEL
BY COUNTRY BY CAR
ON TABLE SET PAGE-NUM OFF
ON TABLE SET STYLE *
TYPE=DATA, COLUMN=N1, URL=/cgi-bin/ibi_cgi/ibiweb.exe? (IBIF_cmd='MNTCON EX MNTIVP’ IBIS_connect='on' IBIAPP_app='ibisamp' IBIC_server='edaserve'), $
ENDSTYLE
END

3) Click on drill down to launch MNTIVP.MNT in the same Output frame.
4) Click browser Back button. Without the new feature, I get the Maintain disconnect warning message in which I click Ok to. Then immediately followed by the redirection to the previous report.

In any case, I strongly suggest you open a case with Customer Support to troubleshoot and resolve problem.

Hi,

I've been testing with your suggestion , and indeed , i'm able to use the back-button

but the only (and rather important thing ) i can't do now is SAVE updates

basically, i have grid with a data , users can add change the data and then hit the save button which does the update

but now when i click on save , i get and unknown error 0 and my data hasnt been saved

any clues why?

Peter

It sounds like the Maintain form is being displayed, but is actually in disconnect. Meaning that no Maintain commands will now work. Please open a case with Customer Support and we can debug the issue.

Hi Mark

I actually got it working now (apart from the disconnect message)

I worked with your suggestion some more

i think the problem is that the maintain module is being cached ...

so instead of calling it with a URL

i called it with a javascript :

TYPE=DATA,ACROSSCOLUMN=TOTAL_NBR_PAYROLLED,
JAVASCRIPT=enterMntApp(SUBELEMENT V_WORKW),
WHEN=TOTAL_NBR_INVOICED NE TOTAL_NBR_PAYROLLED ,
$


i added the javascript in my fex :

  
-HTMLFORM BEGIN
<html>
<meta http-equiv="Pragma" content="no-cache">
<head>
<script language="javascript" type="text/javascript">
  function enterMntApp(SUBELEMENT, V_WORKW)
  {
    start.IBIF_cmd.value="MNTCON CLOSEMSH;MNTCON APPPATH payroll;MNTCON EX payroll";
    start.SUB_TYPE.value = SUBELEMENT;
 if ( '!IBI.AMP.BYGROUP;' == '0' )
 {
    start.WWEEKV.value = V_WORKW;
    start.WWEEKT.value = V_WORKW;
 }
 if ( '!IBI.AMP.BYGROUP;' == '2' )
 {
    start.WMNDV.value = V_WORKW;
    start.WMNDT.value = V_WORKW;
 }
 if ( '!IBI.AMP.BYGROUP;' == '1' )
 {
    start.BWEEKV.value = V_WORKW;
    start.BWEEKT.value = V_WORKW;
 }
    start.submit();
 }
</script>
</head>
  <form name="start" action="http://S11007:80/cgi-bin/ibi_cgi/ibiweb.exe" method="GET">
    <input type="hidden" name="IBIS_connect" value="on"/>
    <input type="hidden" name="IBIS_passthru" value="on"/>
    <input type="hidden" name="IBIC_server" value="CLUSTER"/>
   <input type="hidden" name="IBIF_cmd" value=""/>
    <input type="hidden" name="SUB_TYPE" value=""/>
    <input type="hidden" name="MAATSCHAPPIJ" value="!IBI.AMP.MAATSCHAPPIJ;"/>
    <input type="hidden" name="OUTPUT" value="HTML"/>
    <input type="hidden" name="ELM_TYPE" value="!IBI.AMP.ELM_TYPE;"/>
    <input type="hidden" name="WWEEKV" value="!IBI.AMP.WWEEKV;"/>
    <input type="hidden" name="WWEEKT" value="!IBI.AMP.WWEEKT;"/>
    <input type="hidden" name="WMNDV" value="!IBI.AMP.WMNDV;"/>
    <input type="hidden" name="WMNDT" value="!IBI.AMP.WMNDT;"/>
    <input type="hidden" name="BWEEKV" value="!IBI.AMP.BWEEKV;"/>
    <input type="hidden" name="BWEEKT" value="!IBI.AMP.BWEEKT;"/>
    <input type="hidden" name="BYGROUP" value="!IBI.AMP.BYGROUP;"/>
    <input type="hidden" name="INDRAND" value="!IBI.AMP.INDRAND;"/>
    <input type="hidden" name="INDHOUSE" value="!IBI.AMP.INDHOUSE;"/>
    <input type="hidden" name="SHOWHOUSEH" value="!IBI.AMP.SHOWHOUSEH;"/>
    <input type="hidden" name="SHOWRANDST" value="!IBI.AMP.SHOWRANDST;"/>
    <input type="hidden" name="SHOWNUMBER" value="!IBI.AMP.SHOWNUMBER;"/>
    <input type="hidden" name="SHOWAMOUNT" value="!IBI.AMP.SHOWAMOUNT;"/>
  </form>
</html>
-HTMLFORM END

and this seems to work

So thanks again for putting me on the right track

Peter

Excellent solution. We usually recommend including a TimeStamp to avoid the caching issue. I am glad this is working for you.