Comment 1 Jürn Brodersen 2016-04-20 15:50:22 CEST

I also got this error.
This happens if the object you want to create has no wizard and the cache is empty. For example creating a new policy has no wizard but creating a user has.

Note on how to clear the cache:
"""
cache = require('umc/modules/udm/cache');
cache.reset()
"""

Code snippet from udm.js:
"""
if (this._newObjectDialog) {
	var getFromDetailPage = {
		properties: this._detailPage.propertyQuery,
		template: this._detailPage.templateQuery
	};
	all(getFromDetailPage).then(lang.hitch(this, function(results) {
		var properties = results.properties;
		var template = results.template && results.template.result;
		if (template && template.length > 0) {
			template = template[0];
		} else {
			template = null;
		}
		this._newObjectDialog.setDetails(this._detailPage, template, properties);
	}));
} else {
	this.selectChild(this._detailPage);
}
"""

while the code waits for "all(getFromDetailPage)" the "this._newObjectDialog" object gets deleted because NewObjectDialog.js doesn't find a wizard.
If the cache isn't empty the "all(getFromDetailPage)" call gets resolved immediately and "this._newObjectDialog" still exists.

Comment 2 Florian Best 2016-04-21 08:59:57 CEST

Ok this sounds reasonable. But is it an error / does it has effects e.g. that there is no dialog to choose a template, etc? (i think there are only user templates so that because users have a wizard this might have no effect).

this._newObjectDialog gets deleted because it is in that case not necessary to have it because the detail page should be opened directly. But maybe this is wrong and we have to wait for that deferred "all(getFromDetailPage)" to decide if we can remove this._newObjectDialog?

Comment 3 Stefan Gohmann 2019-01-03 07:23:17 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.