@sapui5/sap.suite.ui.generic.template 1.136.6 → 1.136.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sapui5/sap.suite.ui.generic.template",
3
- "version": "1.136.6",
3
+ "version": "1.136.7",
4
4
  "description": "SAPUI5 Library sap.suite.ui.generic.template",
5
5
  "keywords": [
6
6
  "sapui5",
@@ -7,7 +7,7 @@
7
7
 
8
8
  (c) Copyright 2009-2015 SAP SE. All rights reserved
9
9
  </copyright>
10
- <version>1.136.6</version>
10
+ <version>1.136.7</version>
11
11
 
12
12
  <documentation>Library with generic Suite UI templates.</documentation>
13
13
 
@@ -8,7 +8,7 @@
8
8
  "i18n": "i18n/i18n.properties",
9
9
  "applicationVersion": {
10
10
  "__comment": "applicationVersion oder componentversion??",
11
- "version": "1.136.6"
11
+ "version": "1.136.7"
12
12
  },
13
13
  "title": "{{TITLE}}",
14
14
  "description": "{{DESCRIPTION}}",
@@ -8,7 +8,7 @@
8
8
  "i18n": "i18n/i18n.properties",
9
9
  "applicationVersion": {
10
10
  "__comment": "applicationVersion oder componentversion??",
11
- "version": "1.136.6"
11
+ "version": "1.136.7"
12
12
  },
13
13
  "title": "Canvas",
14
14
  "description": "Canvas Page",
@@ -84,12 +84,12 @@ sap.ui.define([
84
84
  var aPageVariantControlStateWrappers = []; // controls handled from page variant management if used: smartTable, searchfield, partly multiple views
85
85
 
86
86
  // SmartTable state: Table Settings and (in case of control level variant management) selected variant and whether it's dirty
87
- // In case of multipleViews with multiple tables (mode "multi"), each tab has an own table or chart, which has an own state, so multipleViewsHandler has to take care of
87
+ // In case of multipleViews with multiple tables (mode "multi"), each tab has an own table or chart, which has an own state, so multipleViewsHandler has to take care of
88
88
  // storing/restoring their states (in its part of the appState stored in genericData.tableTabData)
89
- // In this case, mutliViewsHandler exchanges oState.oPresentationControlHandler (setting it always to the current visible one), so don't rely on that to get the wrapper.
89
+ // In this case, mutliViewsHandler exchanges oState.oPresentationControlHandler (setting it always to the current visible one), so don't rely on that to get the wrapper.
90
90
  // Using the id (without providing optional parameter sQuickVariantKey) returns the smartTable only in single table case.
91
91
  var oSmartTable = oController.byId(StableIdHelper.getStableId({type: "ListReportTable", subType: "SmartTable"}));
92
- if (oSmartTable){ // in multipleViews case (with multiple tables) currently multipleViews handler handles complete state information
92
+ if (oSmartTable){ // in multipleViews case (with multiple tables) currently multipleViews handler handles complete state information
93
93
  aControlStateWrappers.push(oTemplateUtils.oCommonUtils.getControlStateWrapper(oSmartTable));
94
94
  }
95
95
 
@@ -128,7 +128,7 @@ sap.ui.define([
128
128
 
129
129
  // List of handlers to react on (app or adaptation) extension state changes. Only one entry expected (handler in SFB wrapper). Currently, extensions are only possible in
130
130
  // SFB - if extensions at other places are needed, the similar handler might differ depending on whether page variant management is used.
131
- var aExtensionStateChangeHandlers = [];
131
+ var aExtensionStateChangeHandlers = [];
132
132
  function customAppStateChange() {
133
133
  aExtensionStateChangeHandlers.forEach(function(fnHandler) {
134
134
  fnHandler();
@@ -239,7 +239,7 @@ sap.ui.define([
239
239
 
240
240
 
241
241
  // Wrapper to control whether data is loaded
242
-
242
+
243
243
  function fnGetDataLoadedWrapper(){
244
244
  // Wrapper to control whether data is expected to be loaded - controls the state, but does not trigger loading data on restore!
245
245
  var oTemplatePrivateModel = oTemplateUtils.oComponentUtils.getTemplatePrivateModel();
@@ -247,15 +247,15 @@ sap.ui.define([
247
247
  // - startup with iAppState: anyway setState will be called
248
248
  // - other startup cases: applyInitialLoadBehavior calls setState explicitly
249
249
  // - navigation
250
-
250
+
251
251
  function fnSetState(bState){
252
252
  oTemplatePrivateModel.setProperty("/generic/bDataAreShownInTable", bState);
253
253
  }
254
-
254
+
255
255
  function fnGetState(){
256
256
  return oTemplatePrivateModel.getProperty("/generic/bDataAreShownInTable");
257
257
  }
258
-
258
+
259
259
  function fnSetDataShown(bDataShown, fnHandler){
260
260
  if (bDataShown === fnGetState()){
261
261
  return;
@@ -263,7 +263,7 @@ sap.ui.define([
263
263
  fnSetState(bDataShown);
264
264
  fnHandler();
265
265
  }
266
-
266
+
267
267
  return {
268
268
  getLocalId: function(){
269
269
  return "$dataLoaded";
@@ -271,7 +271,7 @@ sap.ui.define([
271
271
  setState: fnSetState,
272
272
  getState: fnGetState,
273
273
  attachStateChanged: function(fnHandler){
274
- // changing from data not loaded to data loaded:
274
+ // changing from data not loaded to data loaded:
275
275
  // - when SFB triggers search
276
276
  oState.oSmartFilterbar.attachSearch(fnSetDataShown.bind(null, true, fnHandler));
277
277
 
@@ -286,7 +286,7 @@ sap.ui.define([
286
286
  }
287
287
  };
288
288
  }
289
-
289
+
290
290
  var oDataLoadedWrapper = fnGetDataLoadedWrapper();
291
291
  aControlStateWrappers.push(oDataLoadedWrapper);
292
292
  // oDataLoadedWrapper.attachStateChanged(changeIappState);
@@ -396,7 +396,7 @@ sap.ui.define([
396
396
  if (Device.system.phone) {
397
397
  collapseHeader();
398
398
  }
399
- // Ideally, oDataLoadedWrapper should ensure to keep its state correct. However, currently we have no means to attach to the command - i.e. oDataLoadedWrapper only
399
+ // Ideally, oDataLoadedWrapper should ensure to keep its state correct. However, currently we have no means to attach to the command - i.e. oDataLoadedWrapper only
400
400
  // attaches to SFB's search event, which is only triggered when user presses the go button. When keyboard shortcut is used instead, this handler would be called (as it
401
401
  // is attached to the command), but SFB's search event would not be triggered. As workaround, we additionally set data loaded state to true here and inform explicitly
402
402
  // the the state has changed.
@@ -440,7 +440,7 @@ sap.ui.define([
440
440
  }
441
441
  }
442
442
  }
443
-
443
+
444
444
  /*
445
445
  This method is called when an LR app is the target of an external navigation and the XAppState data contains a presentationVariant.
446
446
  The sorting from this presentationVariant is then applied to the table.
@@ -460,13 +460,13 @@ sap.ui.define([
460
460
  fnAdaptOtherControlsToAppState(oAppData.controlStates);
461
461
  if (areDataShownInTable()){
462
462
  // fnAdaptOtherControlsToAppState only (synchronously) sets the state including the information whether data should be loaded - if this is the case, the actual loading
463
- // (which happens asynchronous of course) still needs to be triggered
463
+ // (which happens asynchronous of course) still needs to be triggered
464
464
  loadData();
465
465
  } else {
466
466
  // hide placeholder already here, if no data is to be loaded - in case data is loaded, it will be hidden in data received event
467
467
  oTemplateUtils.oComponentUtils.hidePlaceholder();
468
- }
469
-
468
+ }
469
+
470
470
  // special case: when restoring an old app state with data loaded, but in the meantime a filter not set in that state has been changed to mandatory, SFB.search would not
471
471
  // trigger a request (but instead only mark that filter) - thus hiding placeholder now to avoid it to stay forever
472
472
  // TODO: refactor: Still in that case our internal data shows data are loaded - ideally, that should not be the case
@@ -603,7 +603,7 @@ sap.ui.define([
603
603
 
604
604
  function fnAdaptToAppStateStartUpWithParameters(oAppData, oURLParameters, sPreferredQuickVariantSelectionKey){
605
605
  handleVariantIdPassedViaURLParams(oURLParameters);
606
-
606
+
607
607
  var oSFBUiState = oState.oSmartFilterbar.getUiState();
608
608
  var oSFBSemanticDates = oSFBUiState.getSemanticDates();
609
609
  //oStartupObject to be passed to the extension where urlParameters and selectedQuickVariantSelectionKey are optional
@@ -766,23 +766,24 @@ sap.ui.define([
766
766
  default:
767
767
  throw new FeError(sClassName, "Invalid navigation type: " + sNavType);
768
768
  }
769
-
769
+
770
770
  // common to all startup cases (except iAppState)
771
771
  if (areDataShownInTable()){
772
772
  // trigger search if needed
773
773
  oState.oSmartFilterbar.search();
774
- // For desktop devices, expand the header for Standard and Custom variants and for tablet and mobile devices,
774
+ // For desktop devices, expand the header for Standard and Custom variants and for tablet and mobile devices,
775
775
  // collapse the header only if search is triggered.
776
776
  if (Device.system.desktop) {
777
777
  oTemplateUtils.oCommonUtils.getControlStateWrapper(oController.byId(StableIdHelper.getStableId({type: "ListReportPage", subType: "DynamicPage"}))).setHeaderState(oController, true);
778
778
  } else {
779
779
  collapseHeader();
780
780
  }
781
- } else {
782
- // if no data are loaded, place holder has to be hidden now - otherwise it will be hidden when data is received
781
+ }
782
+ if (!areDataShownInTable() || Object.keys(oState.oSmartFilterbar.verifySearchAllowed()).length > 0) {
783
+ // if no data are loaded or search is not allowed, place holder has to be hidden now - otherwise it will be hidden when data is received
783
784
  oTemplateUtils.oComponentUtils.hidePlaceholder();
784
785
  }
785
-
786
+
786
787
  // ensure first iAppState is created
787
788
  changeIappState();
788
789
  }
@@ -999,14 +1000,14 @@ sap.ui.define([
999
1000
  }
1000
1001
 
1001
1002
  // provide data load settings including defaulting
1002
- // ideally, this should be implemented in a generic way in template assembler, so that generated getters also return default values for objects if not explicitely set in
1003
+ // ideally, this should be implemented in a generic way in template assembler, so that generated getters also return default values for objects if not explicitely set in
1003
1004
  // manifest (i.e. it should be sufficient to define the default in component - no need to individually implement defaulting!)
1004
1005
  function getDataLoadSettings(){
1005
1006
  // general default
1006
1007
  var oDefaultDataLoadSettings = {loadDataOnAppLaunch: "ifAnyFilterExist"};
1007
1008
 
1008
1009
  // intension is boolean, but unfortunately faulty values are (historically) not treated consistently
1009
- var bEnableAutoBindingMultiViews = oState.oMultipleViewsHandler.getOriginalEnableAutoBinding();
1010
+ var bEnableAutoBindingMultiViews = oState.oMultipleViewsHandler.getOriginalEnableAutoBinding();
1010
1011
 
1011
1012
  // if multiple views settings is not defined (also the case in single views case), general default is taken. Unlike other faulty values, null is treated like undefined
1012
1013
  if (bEnableAutoBindingMultiViews !== undefined && bEnableAutoBindingMultiViews !== null){
@@ -1016,13 +1017,13 @@ sap.ui.define([
1016
1017
 
1017
1018
  var oManifestDataLoadSettings = oController.getOwnerComponent().getDataLoadSettings();
1018
1019
  // (historically) explicit setting empty string (not an allowed value according to definition in component!) is treated like undefined (including adopting multiple views
1019
- // settings. Other not allowed values (any other sting) were ignored, i.e. returning undefined from getInitialLoadBehaviourSettings, thus setting undefined to
1020
- // oSmartVariantManagement.setExecuteOnStandard (which actually only sets the default) and finally using the value returned from
1020
+ // settings. Other not allowed values (any other sting) were ignored, i.e. returning undefined from getInitialLoadBehaviourSettings, thus setting undefined to
1021
+ // oSmartVariantManagement.setExecuteOnStandard (which actually only sets the default) and finally using the value returned from
1021
1022
  // oSmartVariantManagement.getExecuteOnStandard (only different from overall default (false), if user has explicitly set it)
1022
1023
  if (oManifestDataLoadSettings && oManifestDataLoadSettings.loadDataOnAppLaunch === ""){
1023
1024
  oManifestDataLoadSettings.loadDataOnAppLaunch = undefined;
1024
1025
  }
1025
-
1026
+
1026
1027
  // explicit setting has highest priority
1027
1028
  return extend(oDefaultDataLoadSettings, oManifestDataLoadSettings);
1028
1029
  }
@@ -1031,7 +1032,7 @@ sap.ui.define([
1031
1032
  // - sets default value for flag whether standard variant should be execute on select
1032
1033
  // - determines whether we actually should load data
1033
1034
  function applyInitialLoadBehavior(bDataLoadCausedByNavigation){
1034
- // cases definitely determining to load data initially
1035
+ // cases definitely determining to load data initially
1035
1036
  // - worklist
1036
1037
  // - livemode
1037
1038
  // - master detail (i.e. bLoadListAndFirstEntryOnStartup is set)
@@ -1040,17 +1041,17 @@ sap.ui.define([
1040
1041
 
1041
1042
  var sLoadBehaviour = getDataLoadSettings().loadDataOnAppLaunch;
1042
1043
  if (!oSmartVariantManagement || oController.getOwnerComponent().getVariantManagementHidden()){
1043
- // No VM ->
1044
+ // No VM ->
1044
1045
  bShouldDataBeLoaded = bShouldDataBeLoaded || sLoadBehaviour === "always";
1045
1046
  bShouldDataBeLoaded = bShouldDataBeLoaded || (sLoadBehaviour === "ifAnyFilterExist" && oSmartFilterbar.getFiltersWithValues().length > 0);
1046
1047
  // behavior of last patch set would translate to the following - seems not to be correct (in case of setting ifAnyFilterExist but no filters provided)
1047
1048
  // bShouldDataBeLoaded = bShouldDataBeLoaded || sLoadBehaviour !== "never";
1048
1049
  } else {
1049
- // in case of a (visible) SVM, we need to set the default value
1050
- // default value for standard variant
1050
+ // in case of a (visible) SVM, we need to set the default value
1051
+ // default value for standard variant
1051
1052
  // - true if one of the conditions above is fulfilled
1052
- // - or for any manifest setting but "never"
1053
- // (Remark: "ifAnyFilterExist" leads to mark the standard variant true, even if no filter is provided - this looks ok for startup, as the text shown to the user
1053
+ // - or for any manifest setting but "never"
1054
+ // (Remark: "ifAnyFilterExist" leads to mark the standard variant true, even if no filter is provided - this looks ok for startup, as the text shown to the user
1054
1055
  // contains the condition, but if reselecting the standard variant, it will also select without filters!
1055
1056
  // TODO: check, how to solve that inconsistency)
1056
1057
  // - but in both cases not, if a mandatory filter is missing
@@ -8,7 +8,7 @@
8
8
  "i18n": "i18n/i18n.properties",
9
9
  "applicationVersion": {
10
10
  "__comment": "applicationVersion oder componentversion??",
11
- "version": "1.136.6"
11
+ "version": "1.136.7"
12
12
  },
13
13
  "title": "{{TITLE}}",
14
14
  "description": "{{DESCRIPTION}}",
@@ -6,7 +6,7 @@
6
6
  "type": "component",
7
7
  "i18n": "i18n/i18n.properties",
8
8
  "applicationVersion": {
9
- "version": "1.136.6"
9
+ "version": "1.136.7"
10
10
  },
11
11
  "title": "{{TITLE}}",
12
12
  "description": "{{DESCRIPTION}}",
@@ -6,7 +6,7 @@
6
6
  "type": "component",
7
7
  "i18n": "i18n/i18n.properties",
8
8
  "applicationVersion": {
9
- "version": "1.136.6"
9
+ "version": "1.136.7"
10
10
  },
11
11
  "title": "{{TITLE}}",
12
12
  "description": "{{DESCRIPTION}}",
@@ -6,7 +6,7 @@
6
6
  "type": "component",
7
7
  "i18n": "i18n/i18n.properties",
8
8
  "applicationVersion": {
9
- "version": "1.136.6"
9
+ "version": "1.136.7"
10
10
  },
11
11
  "title": "{{TITLE}}",
12
12
  "description": "{{DESCRIPTION}}",
@@ -950,7 +950,7 @@ sap.ui.define([
950
950
  * @public
951
951
  * @extends sap.ui.core.UIComponent
952
952
  * @author SAP SE
953
- * @version 1.136.6
953
+ * @version 1.136.7
954
954
  * @name sap.suite.ui.generic.template.lib.AppComponent
955
955
  */
956
956
  var oAppComponent = UIComponent.extend("sap.suite.ui.generic.template.lib.AppComponent", {
@@ -3216,7 +3216,7 @@ sap.ui.define(["sap/ui/base/Object",
3216
3216
  * @param {sap.suite.ui.generic.template.lib.AppComponent} oAppComponent The AppComponent instance
3217
3217
  * @public
3218
3218
  * @extends sap.ui.base.Object
3219
- * @version 1.136.6
3219
+ * @version 1.136.7
3220
3220
  * @since 1.30.0
3221
3221
  * @alias sap.suite.ui.generic.template.lib.NavigationController
3222
3222
  */
@@ -66,7 +66,7 @@ sap.ui.define([
66
66
  interfaces: [],
67
67
  controls: [],
68
68
  elements: [],
69
- version: "1.136.6",
69
+ version: "1.136.7",
70
70
  extensions: {
71
71
  //Configuration used for rule loading of Support Assistant
72
72
  "sap.ui.support": {