As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Do you get an error? What happens when you run this EX procedure?
I've seen IBIWF_defer=defer in some URL but I can't remember where and doesn't show up in the doc when I search for it.This message has been edited. Last edited by: BabakNYC,
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
As far as I know, there are three four ways to run a fex in deferred mode:
1) From the Resource Tree, right-click a fex, then select Run Deferred 2) In a report drilldown link, include the &IBIMR_defer parameter, with value "Defer" 3) From an HTML form, include the &IBIMR_defer parameter, with value "Defer" 4) Via a URL that includes the &IBIMR_defer parameter, with value "Defer"
From this knowledge, I came up with this demo fex, which includes an HTML form. On Mondays, Wednesdays and Fridays, the second fex runs in deferred mode. On other days, it runs immediately.
Change the days in the IF statement to see it behave in both ways - immediate and deferred
-SET &ECHO=ALL;
-SET &DOW = DOWK(&YYMD, 'DW');
-SET &DEFER_IND = IF &DOW IN ('MON', 'WED', 'FRI') THEN 'Defer' ELSE '';
-HTMLFORM BEGIN
<html>
<body onload="document.forms[0].submit();">
<form action="run.bip" method="post">
<input type="hidden" name="BIP_REQUEST_TYPE" value="BIP_RUN"/>
<input type="hidden" name="BIP_folder" value="IBFS:/WFC/Repository/FocalPoint"/>
<input type="hidden" name="BIP_item" value="/fp_anatess2.fex"/>
<input type='hidden' name='IBIMR_defer' value="!IBI.AMP.DEFER_IND;" />
</form>
</body>
</html>
-HTMLFORM END
This message has been edited. Last edited by: Francis Mariani,
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Hi Francis, Thank you for your response. Yes, I use several of those methods already.
But here is my dilemma:
I want to use EX IBIMR_defer=Defer to execute a procedure on deferred mode.
Using FOCEXEC=(IBIMR_defer=Defer) in the stylesheet works just fine when the user clicks on the link on the Report record. But the way I want the fex to work, I want it so that if there is only 1 record returned in the report, it won't bother displaying the records for the user to select which one they want to run deferred, rather it would just run the fex deferred automatically.
So I want to do this simple thing:
TABLE FILE... ON TABLE HOLD END
IF &LINES=1 goto :EXME;
TABLE FILE ... ... ... ON TABLE PCHOLD FORMAT HTML TYPE=DATA, FOCEXEC=runme.fex(IBIMR_defer=Defer) $ END -EXIT
-:EXME EX runme.fex IBIMR_defer=Defer
Very simple. But the EX doesn't work. By the way, &IBIMR_user parameter also doesn't get passed when using EX.
By the way, both calling program and called program are in Content. Dunno if that matters. I haven't tried running this under EDASERVE.