With traditional web-based applications, it was often necessary to refresh entire screens to repopulate individual fields according to various triggering of business rules, such as populating a child list with values based upon a change in its parent value. ExtraView has maintained a rich set of features in addition to the management of parent-child relationships, such as visible if<\/b> and required if<\/b>. As powerful as many of these features were, they required ExtraView to execute the feature by returning the values from the browser to the server where the logic was used to send a complete page of information back to the browser. This is known as a \u201cscreen refresh\u201d and whilst it is capable of executing complex logic, the process takes time, from a half-second to four or more seconds, depending on a variety of factors. These factors include the speed of the network and the speed of the hardware as well as the size and complexity of the ExtraView layouts that are being processed.<\/p>\n
Using a technology known as Ajax, most screen refreshes are eliminated and the processing time is typically an order of magnitude less than the time for an entire screen refresh. The key places where ExtraView takes advantage of Ajax while processing issues on add<\/em> and edit<\/em> layouts are:<\/p>\n The screen layout renderer in ExtraView always removes rows of fields where there is no visible content. This avoids unsightly gaps in the screen for your users. If you have a row that is entirely suppressed, and there are one or more fields on that row which are invisible due to a visible if cell attribute, then the row is not generated at all when the field or fields do not meet the criteria to become visible.<\/p>\n In this circumstance where the entire row is not rendered, there is insufficient information in the layout to use Ajax to populate the field when it becomes visible. As a result, ExtraView will revert to a full screen refresh. Thus the functionality is correct, but Ajax is not and cannot be used to make the field visible. If keeping the speed of the Ajax refresh is important to your application, consider altering your layout to include a field which will be visible at all times on the row of your layout so that something is always visible. This could even be a label field with a blank value. Although there is no obvious effect from this, it is actually visible.<\/p>\n","protected":false},"excerpt":{"rendered":" With traditional web-based applications, it was often necessary to refresh entire screens to repopulate individual fields according to various triggering of business rules, such as populating a child list with values based upon a change in its parent value. ExtraView has maintained a rich set of features in addition to the management of parent-child relationships,…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":23937,"menu_order":5,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-23969","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n\n
\n\tAJAX Limitations<\/h3>\n