|Date values not shown in Grid Combo||12.01.2021 16:01|| Workspace: FX_WS_1993 App: 648 Page: 11 Given a grid combo where some date values are being selected (typically in additional fields, but here we just use d and r) should yield a set of date or date/time values.
select to_date ('31.12.2018','DD.MM.YYYY') d, to_date ('31.12.2018','DD.MM.YYYY') r from dual UNION ALL
select to_date ('10.12.2018','DD.MM.YYYY') d, to_date ('10.12.2018','DD.MM.YYYY') r from dual UNION ALL
select to_date ('10.12.2021','DD.MM.YYYY') d, to_date ('10.12.2021','DD.MM.YYYY') r from dual UNION ALL
select to_date ('10.12.2022','DD.MM.YYYY') d, to_date ('10.12.2022','DD.MM.YYYY') r from dual UNION ALL
select DATE'2020-12-01' d, DATE'2020-12-01' r from dual UNION ALL
select to_date ('10.12.2022 00:00:01','DD.MM.YYYY HH24:MI:SS') d, to_date ('10.12.2022 00:00:01','DD.MM.YYYY HH24:MI:SS') r from dual UNION ALL
select to_date ('10.12.2022 00:01:00','DD.MM.YYYY HH24:MI:SS') d, to_date ('10.12.2022 00:01:00','DD.MM.YYYY HH24:MI:SS') r from dual UNION ALL
select SYSDATE d, SYSDATE r from dual UNION ALL
select to_date ('10.12.2022 15:01:00','DD.MM.YYYY HH24:MI:SS') d, to_date ('10.12.2022 15:01:00','DD.MM.YYYY HH24:MI:SS') r from dual
31-DEC-2018 00:00:00 31-DEC-2018 00:00:00
10-DEC-2018 00:00:00 10-DEC-2018 00:00:00
10-DEC-2021 00:00:00 10-DEC-2021 00:00:00
10-DEC-2022 00:00:00 10-DEC-2022 00:00:00
01-DEC-2020 00:00:00 01-DEC-2020 00:00:00
10-DEC-2022 00:00:01 10-DEC-2022 00:00:01
10-DEC-2022 00:01:00 10-DEC-2022 00:01:00
12-JAN-2021 17:52:52 12-JAN-2021 17:52:52
10-DEC-2022 15:01:00 10-DEC-2022 15:01:00
9 rows selected.
In the grid combo though, only the SYSDATE values are shown. How can we ensure that values from date columns always show? We had another issue in that area in FOEX 3.1 https://forum.foex.at/question/grid-combo-date-format-on-foex-31 that was addressed via FXP-3546
|FOEX Non-modal Window behaviour in tabbed region SPA vs. iFrame Mode||09.07.2020 21:07|| Workspace: FX_WS_1993 App: 648 Page: 4000 When opening a window in a tabbed region when in iFrame Mode, the opened window stays within it's original tab and gets hidden when switching to another tab. It becomes visible again when returning to the original tab and the users can then continue working in that window.
When in SPA mode, then window stays in the context of the parent page and does not hide when switching the tab. This can be tested by changing the "Load into Region" setting on the Content Loader of Page 30, where the parent tab panel is located, and calling page 4000 from the menu on page 30 of the Demo upp via "Window" / Window Modes.
Is it possible to have the window hide on tab changes also when the page the region is on is opened in SPA mode?
|Checkmark in FOEX Checkbox (Simple) Form Item||30.06.2020 11:06|| Workspace: FX_WS_1993 App: 874 Page: 13 Some users find the contrast of a checkbox's checkmark too weak and want it adjusted for ergonomic reasons.
When in focus, the check mark is easy to see. How can we change the style of the check mark across the application?
|Selecting a forms field||04.06.2020 17:06|| Workspace: FX_WS_1993 App: 874 Page: 12 We have got to a requirement to select an item after forms load, so that it is highlighted and can be overwritten with the first keystroke.
This can be achieved by adding "selectOnFocus":true in the Field config and then setting the focus on that particular item on Load success. This has got the side effect that the field is then selected every time on focus, not just the first time. Is it possible to select the item value in a dynamic action, in our case a datepicker, programatically where "selectOnFocus" is at the default of false?
|Returning Modal dialog items back to the parent||26.05.2020 14:05|| I'm currently debugging a more complex example of a modal dialog opened with a FOEX Window DA, which is embedded in a content loader grid. In the past, we've been handing items back to the parent page by setting the appropriate page items on the parent; in standard APEX we've been using "Dialog Items to return" as per John Snyders' piece here https://hardlikesoftware.com/weblog/2017/01/05/passing-data-in-and-out-of-apex-dialogs/ (section "Returning Data"). What's the current state of the art in FOEX to do that?
|Setting a hidden item outside a Forms Region with Grid / Page item Binding||02.04.2020 14:04|| Workspace: FX_WS_1993 App: 648 Page: 1500 When setting a hidden page item with the FOEX Row Item / Select Bind Page item Dynamic Action, the page item is not being set if it is in a static content region outside of the FOEX viewport. For example P1500_CREDIT_CARD_CVV on the test page was set fine when it was in the Forms region, and on another page we had an item that was setting OK in a reports region. Do items set with this Dynamic action have to be within the Viewport?
|Grid / Page Item Binding blocks when row is edited in Row Edit Mode||02.04.2020 14:04|| Workspace: FX_WS_1993 App: 648 Page: 1500 When in row edit mode, you can edit rows using the Forms Page items with Grid/Page Item Binding when the row is not currently being edited. If the row is currently being edited, there will be no binding from the Page items to the grid columns or vice versa, until the record is being saved, at which point the values in the edited grid record will be used to update the database and the page items. Is that by design?
The employees grid on the test page has been switched to row edit mode to demonstrate that behaviour.
|Using a content loader with the "RP" directive to reset pagination causes invalid item ID on Refresh in SPA mode||01.04.2020 17:04|| Workspace: FX_WS_1993 App: 874 Page: 11 On the second call to a content loader region where we want the pagination reset, the following error gets shown in the "Errors" section of APEX debug:
ERR-1002 Unable to find item ID for item "RP" in application "874". Unexpected error, unable to find item name at application or page level.
This can be reproduced by pressing the "Load" Button a couple of times on the test page provided. It does not happen in iframe mode.
What's the state of the art of loading in custom vtype libraries with SPA mode? We also want to cater for the page falling back to iframe mode, or to be run in standalone mode, e.g. for testing.
|Forum does not index more recent entries||24.03.2020 16:03|| It seems to me that the forum search is not indexing entries from recent months. For example, when you search for Germany, you get this result set
But not e.g. https://forum.foex.at/question/on-grid-numeric-column-with-no-format-mask-min-x2f-max-set-and-language-german-numbers-get-rounded-to-whole-numbers-and-interpreted-x-100 which also includes the work "Germany" in the Body.
|Setting a decimal number as min value for a grid column||23.03.2020 20:03|| Workspace: FX_WS_1993 App: 648 Page: 1050 When setting a min value for a grid column, I can save the min value just fine - during entry Numbers and the decimal point are enterable, other characters are locked.
When running the page, however, I get an error message. In English:
ora_sqlerrm: ORA-20100: JSON Scanner exception @ line: 1 column: 43 - Unexpected char: . ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 1500 ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 2501 ORA-06512: at "FOEX_040200.FX_P_JSON_PARSER", line 654 ORA-06512: at "FOEX_040200.FX_JSON_T", line 17 ORA-06512: at "FOEX_040200.FX_P_GRID", line 5578 ORA-06512: at "FOEX_040200.FX_P_GRID", line 5770 ORA-06512: at "FOEX_040200.FX_P_GRID", line 6267 ORA-06512: at "FOEX_040200.FX_P_GRID", line 6837 ORA-06512: at line 4 ORA-06512: at "SYS.DBMS_SYS_SQL", line 2120 ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_190100", line 599 ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 2486 ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 1476
component.name: Data Types - Editors
error_backtrace:ORA-06512: at "FOEX_040200.FX_P_JSON_PARSER", line 654
ORA-06512: at "FOEX_040200.FX_JSON_T", line 17
ORA-06512: at "FOEX_040200.FX_P_GRID", line 5578
ORA-06512: at "FOEX_040200.FX_P_GRID", line 5770
ORA-06512: at "FOEX_040200.FX_P_GRID", line 6267
ORA-06512: at "FOEX_040200.FX_P_GRID", line 6837
ORA-06512: at line 4
ORA-06512: at "SYS.DBMS_SYS_SQL", line 2120
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_190100", line 599
ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 2486
ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 1500
ORA-06512: at "APEX_190100.WWV_FLOW_DYNAMIC_EXEC", line 2501
ORA-06512: at "FOEX_040200.FX_P_JSON_PARSER", line 654
ORA-06512: at "FOEX_040200.FX_JSON_T", line 17
|On grid numeric column with no format mask, min/max set and Language German, Numbers get rounded to whole numbers, and interpreted x 100||17.03.2020 12:03|| Workspace: FX_WS_1993 App: 648 Page: 1050 Given a Grid column set to text field, with no format mask and FOEX Settings like this
When you enter a value of 2,73
it gets rounded to 3,00 and we get a violation notice, even though we are well within the speed limit.
Pls have a look into the test case and confirm the situation here. Thank you!
|Decimal Precision on grid column with numeric formatting applied does not match when using German Language||16.03.2020 20:03|| Workspace: FX_WS_1993
When working on an updatable grid with a number format, such as 999G999G999G999G990D0000 applied, and the language set to English, the editable field handles the precision correctly and rounds per the digits set in the Dxxx portion of the format mask.
So when we enter
and tab out of the field, we get
When we switch to German, e.g. by switching the Application Primary Language or using FSP_LANGUAGE_PREFERENCE, and enter
we get the value hardcoded to 2 decimals.
Maybe linked: While working in our instance with the challenges from https://forum.foex.at/question/control-language-of-sencha-messages, we've also noticed some Number Formatting code in the Sencha locale Files, which we had to leave in place for the decimal point handling to work properly when using a non-English Locale.
How can we ensure the rounding behaviour / ability to set a decimal precision in a Grid is the same across all languages?
|Reduce whitespace above fieldset||16.03.2020 11:03|| Workspace: FX_WS_1993 App: 874 Page: 6 Using Triton Mini, there is a large area of whitespace above the fieldset that we would like to reduce
What's the best way to do that?
|Setting of Page Items with Content Loader Region in SPA Mode||13.03.2020 17:03|| Workspace: FX_WS_1993 App: 648 Page: 11310 When a Content Loader Region is set to load into the current Page, the "Set these Items" - "with this values" function does not seem to set the target items. We had expected the behaviour to be the same in SPA mode and iframe mode, particularly as the loader could fall back to iframe mode.
To test: Go to Page 11310 and press the "Refresh Content Loader" Button at the top of the master grid. The field "Target Field" does not show any data. Then change the Content Loader by disabling the "Load into Current Page" Switch. The target page item will be populated / the field will show.
Please confirm what the expected behaviour here is.
|Uncaught TypeError: Cannot read property 'delay' of null on grid refresh||13.03.2020 09:03||
Occasionally, when calling a tab from another page in the same tabpanel in SPA mode, and executing a refresh on a grid using
a DA based on a changed item in the target page, we get this error.
foex.js?v=4.2.0:33755 Uncaught TypeError: Cannot read property 'delay' of null
at HTMLAnchorElement.<anonymous> (foex.js?v=4.2.0:33755)
at HTMLDocument.dispatch (jquery-3.4.1.js?v=19.2.0.00.18:5237)
at HTMLDocument.elemData.handle (jquery-3.4.1.js?v=19.2.0.00.18:5044)
at Object.trigger (jquery-3.4.1.js?v=19.2.0.00.18:8471)
at HTMLAnchorElement.<anonymous> (jquery-3.4.1.js?v=19.2.0.00.18:8549)
at Function.each (jquery-3.4.1.js?v=19.2.0.00.18:367)
at jQuery.fn.init.each (jquery-3.4.1.js?v=19.2.0.00.18:202)
at jQuery.fn.init.trigger (jquery-3.4.1.js?v=19.2.0.00.18:8548)
at Item.refresh (item.js?v=19.2.0.00.18:919)
Unfortunately we can't reproduce this issue in the Trial environment yet, is it possible to determine a potential cause
from the error message?
|Cross-Page communication in SPA Mode||12.03.2020 13:03|| I have a master page 1 with a number of child pages rendered within a tabpanel on Page 1 from a Menu using a content loader in SPA mode.
On many of the child pages, I need to signal some Primary Key and active child tab information back up to page 1 which is used to display information and allow context-sensitive actions like dealing with page-specific notes on a generic form.
What's the best way to catch the tab click and trigger the Dynamic action to push page-specific information up to page 1 (e.g. if I click on Page 2 I want to send P2_PK, on Page 3 P3_PK etc.) if P2/P3 run in SPA mode (but could fall back to iframe mode in case of an error)?
|Export visible rows / filtered data opens new tab||11.03.2020 18:03|| When using export filtered data / visible rows, a new tab gets opened. In the current versions of Chrome and Firefox Quantum on the Mac, the tab gets closed after the file gets downloaded. On Safari, the focus remains on the "Untitled" tab after the first download. The standard csv export does not do that. It would be ideal if the other two types could behave the same. To reproduce, export data using the cookbook page 1140 "Export Grid Data".
|Export csv contains more rows than data when using filtered / visible rows||10.03.2020 14:03|| Workspace: FX_WS_1993 App: 874 Page: 4 When exporting larger datasets with the filtered / visible data options, you get into situations where some of the rows repeat. Possibly a chunking error?
To reproduce, filter for "standard" in the Example page provided. The dataset returns 3552 rows. Then export filtered data. The exported dataset has 3660 rows, whereby the last chunk of the dataset gets repeated after the final correct row
The same happens for the visible rows export with a larger dataset. The standard export works OK.
How can we ensure the correct number of rows gets exported?
|Read-only condition gets evaluated twice, does not render datepicker icon||09.03.2020 17:03|| I have a form that gets called from another form via a content loader in SPA mode, loading into the Top Region. On this forms I have got PL/SQL expressions on many fields. When the read-only condition evaluates to false and my field should be editable, I can indeed edit datepicker fields, but the datepicker icons do not render. This does not happen in iframe mode. I cannot reproduce this on your system. When looking at our debug logs, I can see that the read-only condition gets evaluated twice for each call to the form. On the first call, the form field values which act as inputs into the read-only condition are NULL, and our procedure evaluates the read-only condition to TRUE. On the second call, we have got the correct form field values, and the read-only condition evaluates to false. On one of the read-only conditions we have added
AND NOT fx_p_form_api.is_rendering
which let the datepicker icon render.
Is the double-evaluation of the conditions expected?
What's the correct way of dealing with this situation?
|Row edit buttons obscured by row headings in Row Edit Mode||06.03.2020 21:03|| When there are only 2 rows, the buttons to Update and cancel are obscured by the row headings. To reproduce: On Triton Mini, Chrome/Mac, set the Show row number to 2 and press update on the second row. This reproduces on the hosted cookbook on Page 1110 Conditional Row edit. How can the buttonsbe positioned such that they are fully visible?
|Textarea becomes mandatory field even if required=no when Trim spaces is set||06.03.2020 19:03|| Workspace: FX_WS_1993 App: 648 Page: 2060 Example:
On Page 2060, we set the "Trim Spaces" Setting for Item P2060_STREET_ADDRESS to "Leading and Trailing". Then the Street Address Field becomes required. We would expect it to remain an optional field.
|Cannot read Message Box response||06.03.2020 17:03|| Using a Prompt Message Box or a Textarea Prompt Message Box, the response item is not always available. On our internal systems, we have got a page where we get a response back when we run the page standalone, but not when we run it as it is normally called, which is when the page is called using the FOEX Window plugin. This also reproduces on the Cookbook. Enter some data into the Message Box and hit OK:
The response is blank
On FOEX 3.1, the response gets shown as expected
How can we capture the response properly in FOEX 4.2?
|Return from Grid Combo Selection throws "is not a valid selector".||06.03.2020 15:03|| Workspace: FX_WS_1993 App: 648 Page: 15063 When using a Grid combo in a window, selecting a value and returning from that Grid combo, an error like this is thrown:
ext-all-debug.js?v=22.214.171.12433.00:42108 Uncaught DOMException: Failed to execute 'querySelector' on 'Element': 'td.x-grid-cell.x-grid-cell-P15063_GRID_COMBO-col-THIS_IS_ATTR.1' is not a valid selector.
at constructor.query (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=126.96.36.19933.00:42108:36)
at constructor.selectNode (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=188.8.131.5233.00:42538:25)
at constructor.down (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=184.108.40.20633.00:40533:25)
at constructor.focusPosition (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=220.127.116.1133.00:215679:64)
at constructor.callParent (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=18.104.22.16833.00:13104:32)
at constructor.focusPosition (https://trial.foex.at/i/foex/js/foex.js?v=22.214.171.12433.00:661:12)
at constructor.setPosition (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=126.96.36.19933.00:215641:16)
at constructor.onFocusEnter (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=188.8.131.5233.00:218889:33)
at constructor.onGlobalFocus (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=184.108.40.20633.00:29489:37)
at constructor.fire (https://trial.foex.at/i/foex/ext/resources/js/ext-all-debug.js?v=220.127.116.1133.00:21915:42)
In our environment, when we run in debug mode, we get the above error when opening the grid combo, and when opening it again we got a "duplicate component id" error. In your environment I could only reproduce the error shown above. To reproduce: In the App, go to "Window", open by Grid Column link. Choose an editable record, we chose Code 90. Click on the Grid combo and choose the sample record
Then the |
|Grid autoqueries when tab is re-opened||05.03.2020 10:03|| Workspace: FX_WS_1993 App: 648 Page: 1000 On a page opened in a tabpanel using the SPA content loader, a grid set to load on demand queries instead when shown when it has been previously opened in the same session.
On a copy of the Cookbook, modify the grid on Page 1000 to disable Page-Level refresh and set the grid to Load on Demand. Start the APP. Navigate to the Page (Grid / Readonly Grid). Close the tab. Choose the tab again from the menu. From the second time on, the grid will ignore the "Load on Demand" directive and automatically query anyway. If you direct content loader on Page 30 to Load in iframe mode instead, this will not happen.
A test case is set up in my workspace. How can we ensure that the grid is always loaded on demand only?
|Debugging SPA Content Loader with APEX_DEBUG_MESSAGES||05.03.2020 00:03|| When debugging SPA Content Loader issues, I found it useful to extend the SQL statement used in the documentation
WHERE MESSAGE_LEVEL = 1
AND MESSAGE LIKE 'FOEX SPA Error%'
ORDER BY MESSAGE_TIMESTAMP DESC;
WHERE message LIKE '%FOEX%SPA%Error%'
ORDER BY message_timestamp DESC;
as this helped me to locate further errors of the pattern
"Exception in "FOEX_SPA":
Error Stack: ORA-00907:
in this case it was an extra semicolon on a LOV definition. Those exceptions were in MESSAGE_LEVEL 2
It may be helpful to others to update the documentation accordingly.
|Control Behaviour of Gridcombo Display||26.02.2020 18:02|| Workspace: FX_WS_1993 App: 297 Page: 3 On FOEX 4.2, APEX 19.2 we set up a Gridcombo in a tabbed Form. When the length value for the grid combo display exceeds the size of the field, it is rendered in 3 different ways:
After selection from the Grid - we see the string visible from the end
When we tab back and forward to another tab on the same form - multiple lines get displayed, but content can be trimmed due to lack of space
When re-rendering the form, we see the string from the beginning
How can we control the display behaviour so it's always the same? In this particular use case the users were looking to see it as displayed in this last example, where it's shown from the beginning and truncated towards the end.
|Control Language of Sencha Messages||26.02.2020 15:02|| We are using a combination of an English UI and local language Elements on a client installation running APEX 19.2 and FOEX 4.2. We've got the internal messages under control using the APEX Text messages feature, we'd also like to show the Sencha Messages in English only, and not the language set in APEX / FSP_LANGUAGE_PREFERENCE. What's the easiest way of doing this?
I'm talking about the messages that are in the locale directory, in debug and minfied files, such as
/foex/ext/resources/locale, e.g. in the Dutch
// changing the msg text below will affect the LoadMask
loadingText: 'Bezig met laden...'
|FOEX 4.2: Fewer Standard Messages in German compared to English||26.02.2020 14:02|| When loading the FOEX text messages, a handful of messages do not get loaded in German, for which the text messages appear translated:
WHERE lower (name) LIKE '%foex%'
AND message_language = 'en'
WHERE lower (name) LIKE '%foex%'
AND message_language = 'de';
It would be cool if the number of messages were the same in each language ;-)
|How to provide a Text Area Character Counter / Max Size indicator||10.05.2019 15:05|| I've got a requirement to provide a visual indicator on the amount of characters a user is still able to input into a text area. Ideally with a counter or at least indicating when they have exeeeded the maximum number of characters in the textareas.
I'm running FOEX 3.1 on APEX 5.1. There doesn't seem to be a setting for that in the FOEX Textarea, but there is one in the standard APEX textarea. If I use the standard textarea on a FOEX Form, it diesplays, but the counter doesn't.
Is there currently a way to implement that requirement within FOEX?
|Whitespace trimming||03.01.2019 16:01|| Is there support to trim Whitespaces in relevant page item plugins, such as the FOEX Text field? Similar to the APEX Text field
|Grid Headers do not refresh with State Saving on||15.08.2018 13:08|| Workspace: FX_WS_1993 App: 268 Page: 11 In our production environment running FOEX 3.1, we have issues with the Grid Headers Refresh on IE 11. In Chrome the header refresh works. On the FOEX trial instance, we also experience issues with the Header Headers Refresh DA when we set state saving on, this time it works on IE but does not work on Chrome. I've created an example, press the "Refresh" Headings button and the headings should be refreshed. Note that in our case, the headings are derived dynamically using PL/SQL (in the example using DBMS_RANDOM). |
|Issues with Exporting National Characters in FOEX 3.1, FOEX 4 Beta||06.06.2018 10:06|| When exporting data from a grid, national character set data does not get exported correctly. In our apps, the Globalization Attribute "Automatic CSV Encoding" is set to "Yes". When testing with Standard APEX exports, we get consistently the correct result using vanilla APEX exports when importing into Excel where the Import Character set is set to ANSI (Windows). This is the default on our Windows Test VM; when testing on OS X we select this character set on import rather then the default "Macintosh" setting.
When the Split-Button Export options "Export Visible Rows" or "Export Filtered Data" are selected, the exported characters are incorrect. When a full export is done, or an export is run from a vanilla APEX Classic Report, the exported data is OK. We have built examples in our Trial Workspace, App 268 Page 9 for FOEX export with a split-button and App 268 page 10 for a Standard Classic Report Export.
A similar issue was reported earlier in
https://forum.tryfoexnow.com/en/f?p=1111:20::::20:P20_THREAD:6735 ("How can I get the csv export for filtered results to return data in the same format as the full export? (FXP-2396)") and appeared to be fixed in FOEX 2 (we have no FOEX 2 instance left to verify)
Could you pls let us know how to get the characters exported correctly with all methods. If a bugfix is required, can we have the fix in 3.1 and 4.0 please. Many thanks. |
|4.0 Beta: For Trigger fields located on top of a forms region, the width setting gets ignored||10.05.2018 12:05|| there is no space to enter data |
|4.0 Beta Translated Messages for UI component labels||10.05.2018 11:05|| In 4.0, FOEX Components are now labelled using Text messages, which allows those labels to be translated. The text messages are pre-populated at runtime. In one of our apps we use en-us as a base language, and then let users switch the language at runtime for data only, between different language values. Languages are set using Globalization / Item Preference (use item containing preferences), via :FSP_LANGUAGE_PREFERENCE.
Is there a way to fall back to a default language (e.g. the Application Primary Language) rather than having to maintain a copy of the Text messages for each language in English? Also keeping in mind that if FOEX starts translating those UI component labels into other languages we would not want to display those translated values, but keep showing the UI in English.
On the first start of the app in developer mode, the Messages are seeded. At this point also, :FSP_LANGUAGE_PREFERENCE seems not to be taken into account, so my current workaround is to switch the primary language of the app for an additional language I want to display, start the app, refresh to ensure the labels shown, and eventually switch back to the original primary app. |
|4.0 Beta themes||10.05.2018 10:05|| In FOEX 4.0, the LOV in Component settings show a multitude of Themes, but only the triton themes are installed on the O/S:
triton triton-compact triton-dark triton-mini
Which themes will be supported in 4.0? |
|forceFit (Force Fit) columns and state saving||18.04.2018 17:04|| We have some grids defined with "Force Fit" set to yes. Users can modify the column width and expect to retain their modification using state saving, but on re-opening such a page the customisation Lost. If "Force Fit" does not support state saving: is there a way for the users to see which grids will retain their column width mods and which will ignore them? |
|Using ROWID as a primary key in Grids||18.04.2018 10:04|| When we upgraded to FOEX 3.1 + HFXP-3545, we encountered a few isolated issues where ROWID was set as the primary key, which were of the pattern
ORA-00923 Keyword FROM not found... ON FXP_GRID Line 7821.
These were fixed easily enough by aliasing the rowid in the SELECT query of the grid.
After Application of HFXP-3576, the same queries started causing issues again. We have now isolated 3 different issues and reproduced in our FOEX workspace, APP 268
Scenario 1, Page 5:
Using a query where the rowid column is prefixed with a table alias such as
, 'ABC' AS FIRST_NAME
, 'DEF' AS LAST_NAME
FROM DUAL d
ORA-00904: "ROWID2": invalid identifier
ORA-06512: at "FOEX_030100.FX_P_GRID", line 2969 ORA-06512: at
Scenario 2, Page 6
The same query, but with a column alias like so
SELECT d.rowid d_rowid
, 'ABC' AS FIRST_NAME
, 'DEF' AS LAST_NAME
FROM DUAL d
runs; however when you want to export visibile rows only or filtered data the export does not download the file. Full export works.
Scenario 3, Page 7
On a CRUD Grid with a query like this
,ROWID AS humpty_rowid
, you get
ORA-00923: FROM keyword not found where expected
ORA-06512: at "FOEX_030100.FX_P_GRID", line 2969 ORA-06512: at
Could you kindly check and advise if there are any restrictions to keep in mind when using ROWIDs in grids, and particularly as primary key |
|Session level caching and Deleting expired cache entries||05.04.2018 10:04|| We have session-level application cache activated and "Expire Cache Entries After" set to 10080 minutes.
In FX_T_CACHING, the EXPIRE_ON timestamps are set as expected; however even for active users it seems the expired cache entriesare never deleted. What do we need to set up in order to delete expired cache entires? |
|Application Cache Upgrade||05.04.2018 10:04|| During the upgrade from 2.2 to 3.1, we had an element with significant runtime that was inserting into
FOEX_030100.FX_T_CACHING and selecting from FROM FOEX_020200.FX_T_CACHING
I wonder whether this step could be omitted from future upgrade scripts, as we'd expect the cache to be rebuilt after a major version upgrade |
|LOV does not take pasted value as input when copy/paste is released rapidly (FOEX 3.1)||04.04.2018 15:04|| This has been reported on Windows 7 with IE and Firefox, both for a form-based popup LOV and also popups in grid since the upgrade to FOEX 3.1.
We can reproduce this on your system as well - the GIF attached shows a quick CTRL-V into a field that does not match against the LOV versus a slower CTRL-V release into the same field with the same value.
Pls. advise how we can handle this situation so that any pasted value into the field gets accepted - the users rely heavily on this feature. |
|Date Picker values entered manually not accepted into session state on Windows 10||04.04.2018 12:04|| When querying a grid using a date picker, the following behaviour happens on Windows 10 only on Chrome and IE (others not tested)
When submitting session state for a FOEX datepicker item, and the value was entered into the field directly, the session state does not get updated when the refresh is run with an APEX Refresh DA. It is submitted correctly when using the magnifier glass on the grid search plugin.
It also gets submitted correctly when the date picker calendar has been used, or the date picker is opened and closed after entering the value.
originally we ran into this on
where we are submitting session state via a PL/SQL DA. However on that page the magnifying glass does not work as the session state is not in the "items to submit". |
|FOEX_FEEDBACK_FORM invalid in FOEX demos||29.03.2018 20:03|| Since the upgrade to FOEX 3.1 the object FOEX_FEEDBACK_FORM is invalid. On the trial instance this errors with PLS-00201: identifier 'JSON' must be declared in Line 63 and 73, on my instance this errors with "looping chain of Synonyms".
As I like to keep our instances squeaky clean and as such free from invalid objects, pls. advise what to do with this object :-) |
|Removal of Synonyms after FOEX 3.1 Upgrade||29.03.2018 19:03|| After upgrading to FOEX 3.1 from FOEX 2 and dropping the old FOEX_020200 DB user with the CASCADE option , a bunch of public synonyms got invalid, pointing back to the schema FOEX_020200 which no longer exists.
Please confirm they can be deleted
It would be cool to mention that step in the upgrade guide. |
|Shuttle Multi-Select causes Uncaught TypeError: Cannot read property 'id' of null||24.03.2018 09:03|| On our DEV instance, this happens when users selected records, dragged them to the right and then try to select a group on the right. On Our FOEX Trial instance App 268 Page 4, this also happens when we multi-select on the left hand side of the shuttle.
ext-all-debug.js?v=18.104.22.16845.01:96792 Uncaught TypeError: Cannot read property 'id' of null
at constructor.getKey (ext-all-debug.js?v=22.214.171.12445.01:96792)
at constructor.add (ext-all-debug.js?v=126.96.36.19945.01:96653)
at commit (ext-all-debug.js?v=188.8.131.5245.01:180474)
at constructor.onSelectChange (ext-all-debug.js?v=184.108.40.20645.01:181169)
at constructor.doMultiSelect (ext-all-debug.js?v=220.127.116.1145.01:180484)
at constructor.selectRange (ext-all-debug.js?v=18.104.22.16845.01:180339)
at constructor.onNavigate (ext-all-debug.js?v=22.214.171.12445.01:180245)
at constructor.fire (ext-all-debug.js?v=126.96.36.19945.01:20803)
at constructor.doFireEvent (ext-all-debug.js?v=188.8.131.5245.01:21773)
at constructor.fireEventArgs (ext-all-debug.js?v=184.108.40.20645.01:21626)
getKey @ ext-all-debug.js?v=220.127.116.1145.01:96792
add @ ext-all-debug.js?v=18.104.22.16845.01:96653
commit @ ext-all-debug.js?v=22.214.171.12445.01:180474
onSelectChange @ ext-all-debug.js?v=126.96.36.19945.01:181169
doMultiSelect @ ext-all-debug.js?v=188.8.131.5245.01:180484
selectRange @ ext-all-debug.js?v=184.108.40.20645.01:180339
onNavigate @ ext-all-debug.js?v=220.127.116.1145.01:180245
fire @ ext-all-debug.js?v=18.104.22.16845.01:20803
doFireEvent @ ext-all-debug.js?v=22.214.171.12445.01:21773
fireEventArgs @ ext-all-debug.js?v=126.96.36.19945.01:21626
fireEvent @ ext-all-debug.js?v=188.8.131.5245.01:21585
fireNavigateEvent @ ext-all-debug.js?v=184.108.40.20645.01:181509
onItemClick @ ext-all-debug.js?v=220.127.116.1145.01:181329
fire @ ext-all-debug.js?v=18.104.22.16845.01:20803
doFireEvent @ ext-all-debug.js?v=22.214.171.12445.01:21773
doFireEvent @ ext-all-debug.js?v=126.96.36.19945.01:67523
prototype.doFireEvent @ ext-all-debug.js?v=188.8.131.5245.01:58428
fireEventArgs @ ext-all-de|
|Item Type field in dynamic forms querey||16.03.2018 00:03|| What are the allowed values for item_type in a dynamic form definition query? |
|Grid Combo Date Format on FOEX 3.1||13.03.2018 17:03|| In FOEX 2.2, Date columns in a grid combo were formatted according to :APP_NLS_DATE_FORMAT. In FOEX 3.1, they are formatted in MM/DD/YYYY
I couldn't find a behaviour change in the Release Notes; is this change intentional? We can workaround with to_char, however then the sort would be affected (we'd still have to to_char for date+time; however date only is our standard use case)
A test case is in our workspace 268:3 |
|Combination of Page Level / Component Level Read only behaves unexpectedly||21.02.2018 11:02|| Given a page with the Read-only Page Level evaluating to FALSE with a PL/SQL expression, and from components evaluating to TRUE with a PL/SQL expression, a Grid combo can be selected from when clicking into the field after Forms Load (even though the LOV buttons themselves are hidden) and a FOEX text field can be typed into. After you save the changes, the fields become non-enterable.
To reproduce: On our trial instance https://trial.tryfoexnow.com/ords/f?p=268:2080 query the first employee, then change the Last Name (to ensure you can save), click into the Grid Combo Field for manager and choose a different Manager, click into the Postal Code and change the Postal Code. Save. The Postal Code and Managers get reset to their previous values, the Last Name change gets accepted. After SAVE, both the Manager and Postal Code Field are truly read-only. The expected behaviour was that they will be read-only at all times.
This was tested on MacOS, latest version of Chrome. To reproduce this repeatedly, we had to reload the page after the test above and on one occasion to close the tab and reload the tab. |
|Passing a FOEX Display field with NULL value through a PL/SQL DA raises Uncaught TypeError: Cannot read property 'replace' of undefined||16.02.2018 21:02|| We have a FOEX display Field on an instance with FOEX 3.1 / APEX 5.1 in APEX 5.1 compatibility mode. When the field value is empty, and the value is passed in/out of a PL/SQL DA a couple of times, we run into
server.js?v=5.1.2.00.09:718 Uncaught TypeError: Cannot read property 'replace' of undefined
at HTMLDivElement.<anonymous> (server.js?v=5.1.2.00.09:718)
at Function.each (jquery-2.2.3.js?v=5.1.2.00.09:365)
at jQuery.fn.init.each (jquery-2.2.3.js?v=5.1.2.00.09:137)
at addPageItemsToRequest (server.js?v=5.1.2.00.09:684)
at ajaxCall (server.js?v=5.1.2.00.09:1113)
at callOrQueue (server.js?v=5.1.2.00.09:971)
at Object.server.plugin (server.js?v=5.1.2.00.09:154)
at Object.da.executePlSqlCode (dynamic_actions.js?v=5.1.2.00.09:239)
at Object.da.doAction (dynamic_actions_core.js?v=5.1.2.00.09:577)
at Object.da.doActions (dynamic_actions_core.js?v=5.1.2.00.09:363)
We did not run into this in our FOEX 2.2 / APEX 5.0 instance
On https://trial.tryfoexnow.com/ords/f?p=268:60015 , press the "Press Me" button a couple of times. Run into the issue. Then either set a source/default value for the display item or change the display item to a FOEX test item. Repeat the test, the error should have gone away |
|Grid Combos with Grid custom config "loadOnSearchOnly":true do not reset when parent value changes||15.02.2018 15:02|| Given 2 grid combos in a cascading LOV relationship, the values of the child grid combo do not clear if the first grid combo is reset or the parent value changes. This could lead to invalid values selected from the LOV.
This happens when "loadOnSearchOnly":true is set which is a grid config attribute we like to use for performance reasons. It's not an issue when the attribute is not set as the grid combo then refreshes automatically
To reproduce, go to our app https://trial.tryfoexnow.com/ords/f?p=268:60012, select values in the Tables and Column grid combos; then reset the table grid combo and open the column grid combo again. The colum grid combo will still contain the LOV values relevant to the now reset parent value. |