Too much placeholders in the Page Tree Creators "Create Page Tree" Popup

[Thomas Landua]

Hi Community,

I have a problem with the instantiation popup of the Page Tree Creator.

The problem only appears, when there are further templates which can be instatiated by "Create page tree"-buttons that are placed on the superordinate template I instantiate.

Situation 1 - works fine:

• I have a template called "KB Article"  with come placeholders: "kb_article_title", "kb_article_type", "kb_article_short_description.
• I create a Button to add a workitem under an existing page.
• As expected the "Create page tree" popup appears and asks for the values to fill the placeholders.

The page is instantiatet and looks as expected.

Situation 2 - works, but asks for too much placeholders

• I have a template which works as overview with some placeholders.  "KB Area" with a placeholders "kb_name".
• The template contains a "Page tree creator" button to instantiate "KB Article"s from Situation 1.
• To instantiate different "KB Area"s, I have a "Page tree creator" button on the KB overview page.
• If I click on the button to instantiate a new "KB Area" the "Page tree creator" popup appears as expected, but the placeholders that are requested from the popup are not only these from the "KB Area" but those more from the "KB Article".

If I ignore the additional placeholders and click on "Create" the new page is created as expected. Do I have required fields in the subordinated template, I can leave a blank in the affected field and the engine works also as expected - however, it is very annoying when the additional placeholders appear for less involved employees :-)

Strangely enough, in this case not all placeholders of the "KB Article" are displayed, in other cases, all of them are requested from the subordinate template. On this screenshot it possible looks as there are only required fields affected, but I can confirm, that in other templates even not required fields do appear in the placeholder popup.

Until a few weeks ago, "Situation 2" works without any issues. How can I avoid these behavior, what changed in the templates engine and is there any workaround?

We have this "Situation 2" in many other use-cases for the "Page Tree Creator" - even with some more complex and a higher number of placeholders.

Do you have any expierience with this behavior?

Many thanks in advance,

Best regards, Thomas