Validator Logic

This article explains how Validator behaves in different scenarios to provide an understanding of when Validator can be used and when Validator does not apply. 

Updating a slide enabled for Validator

In this case the Space owner enables a slide for Validator, and an end-user creates and saves a presentation that contains the locked slide. Afterwards, the admin makes changes to the slide. The following logic applies:

1. The end-user reopens a presentation that containing  the Validator enabled slide.
2. Templafy checks in the server on this specific slide.
3. Templafy finds the slide.
4. Templafy detects the changes made by the admin.
5. Templafy sends back the changes and prompts the end-user.  
6. Upon accepting the changes, the slide is updated and remains locked. 

Deleting a slide enabled for Validator 

In this case the Space owner enables a slide for Validator, and an end-user creates and saves a presentation that contains the locked slide. Then the Space owner deletes the slide that is locked by Validator. The following logic applies:

1. The end-user reopens the presentation containing the Validator enabled slide.
2. Templafy checks in the server on this specific slide.
3. Templafy cannot find the slide as it has been deleted.
4. The end-user presentation cannot be updated and the slide stays locked.

Adding a new slide and enabling it for Validator

In this case the Space owner enables slides for Validator, and an end-user creates and saves a presentation that contains the locked slide. Afterwards, the Space owner adds new a new slide to the presentation template and enables it for Validator. The following logic applies: 

1. The end-user reopens the presentation containing Validator enabled slides.
2. The newly added slide in the Admin Center does not exist in the end-user presentation.
3. Templafy cannot check in the server for this specific slide as it doesn’t exist in the end-user presentation.
4. The end-user presentation cannot be updated. 

Disabling a slide for Validator

In this case the Space owner enables slides for Validator, and an end-user creates and saves a presentation containing the locked slide. Afterwards, the Space owner disables Validator again for the specific slide in the admin center. The following logic applies: 

1. User reopens a presentation containing Validator enabled slides.
2. Templafy checks in the server on this specific slide.
3. Templafy cannot find the slide as it was disabled for Validator.
4. The end-user presentation cannot be updated and the slide stays locked.