FirstSpirit and a continous handling of mandatory fields in Java- and WebClient

Dear FirstSpirit community,

we want to strengthen a feature request for FirstSpirit, that guarantees a common behaviour for mandatory system fields in Java- and WebClient. Actually, they behave different, e.g. when editing site store labels:

  • in WebEdit, the site store display name is mandatory for the master language (see screenshot below)
  • in JavaClient, the display name is complete optional (see screenshot below)

The goal: FirstSpirit should behave the same way here independent of the used FirstSpirit client.



1 Comment
Crownpeak employee
Crownpeak employee

Hello Holger

thank you for your idea to improve FirstSpirit. It is important for us to learn from the experiences of our customers and partners. For this reason we appreciate feedback and any suggestion.

We have evaluated the issue once again and we think that this issues is outdated by the ContentCreator.

You can find more details about our feature selection process in our Features Policy.

Best regards