fnCreateInstance = function() {
						var oInstance;

						if (bViewRootNode) {
							oInstance = oView;
							if (!bAsync) {
								// oParseConfig.settings: the settings object that is given to the factory method
								// mSettings: the settings object that contains the properties parsed from View tag
								//
								// In sync case, mSettings is applied before the oParseConfig.settings. In order to make
								// the mSettings win against the oParseConfig.settings, the properties that exist in
								// both objects are merged into the oParseConfig.settings with the value taken from
								// mSettings and they are then deleted from mSettings.
								if (oParseConfig && oParseConfig.settings) {
									Object.keys(mSettings).forEach(function(sKey) {
										if (oParseConfig.settings.hasOwnProperty(sKey)) {
											oParseConfig.settings[sKey] = mSettings[sKey];
											delete mSettings[sKey];
										}
									});
								}
							}
							oView.applySettings(mSettings);
						} else {
							// the scoped runWithOwner function is only during ASYNC processing!
							oInstance = scopedRunWithOwner(function () {
								var oInstance;
								if (node.getAttributeNS(UI5_INTERNAL_NAMESPACE, "unstash") === "true") {
									oInstance = ElementRegistry.get(mSettings.id);
									// If the placeholder has a visible property we set it to false to hide the placeholder.
									// We must reset the setting to true to make it visible again or reflect the new settings.
									if (oInstance.setVisible) {
										oInstance.setVisible(true);
									}
									oInstance.applySettings(mSettings);
								} else {
									oInstance = new oClass(mSettings);
								}
								return oInstance;
							});
						}

						// check if we need to hand the ExtensionPoint info to the ExtensionProvider
						pProvider = fnTriggerExtensionPointProvider(oInstance, mAggregationsWithExtensionPoints, bAsync);

						return oInstance;
					}
@deprecated because the 'Sequential' Mode is used by default and it's the only mode that will be supported
in the next major release

Pass processingMode to any fragments except JS
XML / HTML fragments: might include nested views / fragments,
 which are processed asynchronously. Therefore the processingMode is needed
JS fragments: might include synchronously or asynchronously created content. Nevertheless, the execution of the
 content creation is not in the scope of the xml template processor, therefore the processing mode is not needed