Has anyone upgraded from 8202, or 8203, to 8204 and found issues with the Drop Down Lists (DDL) not passing values as they did on 8202/3?
Case in point: The values from my DDLs don't make it to my procedures (fex reports / charts) anymore. All incoming values, from the parameter page, are DEFAULTH'd. One of the pages is entirely created in App Studio as an HTML Document. This particular one is all inclusive and can run as a stand-alone procedure. Except that it no longer passes the values. The same procedure, which is running with this issue here in '8204 test' is running fine in '8202 production'.
I did edit this HTML page, made a minor change, then saved it and it still has the issue. I did this as some of us have found that editing something in a newer release sometimes fixes the issue.
Thanks in advance for your insight, DougThis message has been edited. Last edited by: Doug,
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
October 17, 2018, 05:54 AM
Wep5622
Could this be a client-side issue? Do you see the same in a different browser, or is it limited to, say, Internet Explorer? Is there anything in the Javascript console that jumps out as an error?
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
October 17, 2018, 02:01 PM
Doug
Could this be a client-side issue? ♦ Checking... Do you see the same in a different browser, or is it limited to, say, Internet Explorer? ♦ This issue shows up in both IE and Chrome. It worked just fine in 8202 Gen 60. Is there anything in the JavaScript console that jumps out as an error? ♦ I don't see anything there.
I even added a new Submit button to execute a new fex that displays the values that should come through... To no avail...
October 17, 2018, 02:55 PM
TexasStingray
I'm on and 80xx version, but one thing that I have focus is that if I create a html document that calls a procedure and then later on update that procedure to use DEFAULTH for the parameter. If I go back in the Document Composer and if I click on the button to refresh that parameters it remove the ones for the DEFAULTH. This may or may not be the same type of issue.
Scott
October 17, 2018, 05:08 PM
Doug
Thanks TexasStingray, That's downright freaking crazy... I removed the -DEFAULTH &Variables and the values came thru... I'm going to analyze this a bit deeper...
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
October 18, 2018, 03:49 AM
Wep5622
DEFAULTH hides parameters for HTML Composer. That you got them through in an earlier version was perhaps a bug...
If you want your parameters to be seen by HTML Composer, use DEFAULT instead of DEFAULTH.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
October 18, 2018, 09:32 AM
Doug
quote:
DEFAULTH hides parameters for HTML Composer. That you got them through in an earlier version was perhaps a bug...
I agree with that. What I have been doing for years is: 1) Use '-DEFAULT &Variable' in my fex so that they are available from within the HTML Composer. 2) Create my HTML for, Parameter Page (Now 'Filter Page'), which picks up the -DEFAULT'd variables and presents me with the option to create controls for the -DEFAULT'd variables. 3) Go back to the fex after the filter page is working as needed, and change '-DEFAULT' to '-DEFAULTH'. * That's not really needed but makes for quick and easy execution of the associated fex, without the auto prompting. 4) Live happily ever after... Till 8204...
Why did that change?
Now, I need to remove every '-DEFAULTH' from any fex that receives the variables from my filter page. Or, recreate the filter page in 8204 (which may be the best solution).
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
October 22, 2018, 03:26 PM
CoolGuy
Doug,
Thanks for clarifying in your last post what you've been doing up till now. That does indeed SUCK if that doesn't work anymore... UGH.... #cuzIBI
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
October 22, 2018, 03:30 PM
CoolGuy
UPDATE: Nevermind. You're on 8204M Gen48 I'm guessing. My bad.
Also, what release are you on Doug? Is that "Mg48" mean you're on an early access build of some sort?
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
October 22, 2018, 03:36 PM
CoolGuy
I think we'll be attempting to use the new WF Designer > Page Designer piece once we get to 8205 or 8206. Skipping 8204 probably. Lots to rebuild... *rolls eyes*
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
October 22, 2018, 03:41 PM
Hallway
I remember we had something similar to this happen when moving from 8105 to 8201.
Go to the Admin Console > Configuration > Applications Settings> Parameter Prompting in both environments and compare the settings and make sure that they are the same.
Hallway
Prod: 8202M1
Test: 8202M4
Repository:
OS:
Outputs:
October 23, 2018, 10:37 AM
Doug
Thanks for that possibility. But, they are both the same.
