You can now reuse field IDs in Fotoware Alto, which previously was not possible on the same schema or on child schemas after the field had been deleted. To do so, you see a badge in Settings in the Main Menu that leads to the Status Page, where you find the new index for Content and List Items. There, you can trigger updates to Content and List Items.

Fotoware Alto now cleans up the data, preventing the reuse of a field, independent of the schema update. Therefore, indexes are asynchronously updated once the editor deletes a Field that references other schemas or fields. The update-on-request might prevent a ListItem from being deleted due to a stale reference, but it speeds up schema updates. The trigger point for this update is a manual start by the user after changing the schema configuration, indicated with a badge next to the settings menu.

This way, the admin controls when Content and List Items are updated, rather than having to update all items after every change. The significant advantage is the ability to perform multiple changes across multiple schemas without waiting for an update of all items after each change. However, the drawback is that some Items may contain obsolete information until the update is triggered:

• The calculated value for a calculated string field that is not up to date (if its template changed in the schema).
• A reference to a Tagbox or a Relation to a Content Item that is no longer in place, e.g., if the editor removed the Tagbox from the Layer and Content Items had this Layer, and multiple tags were added.
• After the admin's update, outdated items are updated again, and the system cleans the IDs of removed fields, allowing previously used IDs to be reused.

The Status Page in the Settings section of the Main Menu shows the state of Content and List Items: up to date, in progress, or outdated. For the outdated state, the Update button at the end of the page triggers the update. 

It is not required to update the schema immediately after every edit, but the content authority should trigger an update once the schema edits are complete. Otherwise, the search may find Content Items by tags that are no longer available in their metadata profile.

The display pattern configuration across all schema types will trigger an update to this status. An admin can start reindexing affected items after changing existing display patterns, as indicated by a badge in the main menu. The reindexing of all items in the platform is not automatically triggered after updating display patterns, to prevent long wait times for admins updating several display patterns at once. The admin can proactively start re-rendering after all changes are done.

This re-rendering is now handled by a dedicated service provider, deployed on a dedicated instance, to significantly improve performance on high-volume instances.

Bear in mind that the removal of a field does not affect the Display Pattern status, so a broken Display Pattern due to missing field values can not be detected at this point.

The Search Indices referring to the index in Elastic Search where all data is saved to. There are two indices:

1. RootListItemSearchIndex - this index holds all list items.
2. RootContentSearchIndex - this index holds all content items.

When you double-click to open, you see the lists or virtual / file types contained. The index is always updated when field values change.