All Slate users should always take advantage of the latest offerings in Slate as they provide much more functionality and efficiencies. Occasionally, a pre-existing feature may benefit from a comprehensive update to its user experience.
All Slate users should take advantage of the latest offerings in Slate as they provide much more functionality and efficiencies for all users. When newer versions of a feature in Slate that offer more capabilities are made available, the former version is labeled as "Legacy." Tools labeled "legacy tool." These features are:
- Remain functional and supported
- Discouraged in favor of using the latest features and functionality
- Not deprecated without prior announcement or complete feature parody
|Legacy Feature||New Feature|
|Branding Bookmarklet||Branding Editor|
|Microsoft Outlook Add-in||Email to Slate Gateway|
|Slate Template Library||Template Library|
Reader Review Forms
Reader Tab Groups
Reader Tab Materials
|Release Decisions||Release Decisions|
|Event Landing Pages||Portal Events Widget|
When newer versions of a feature in Slate that offer more capabilities are made available, the former version is labeled as "Deprecated." These features are:
- Remain functional - are no longer supported
- Highly discouraged in favor of using the latest features and functionality available to all Slate users.
- Will not be removed from the Slate Community without prior announcement
Historically deprecated features have never been removed from the Slate interface.
For example, it was announced in 2013 that Custom SQL triggers would be "deprecated" in favor of the rules editor. The 'Triggers (deprecated)" tool remains available today in Database. Another example is "Essays (deprecated)." This feature was deprecated many years ago in favor of a process that can be managed using custom application-page scoped forms with material upload widgets.
|Deprecated Feature||New Feature||Details|
Slate application essays should now be managed using Application Page scoped forms with material upload widgets.
|Teasers||Custom Applicant Status Portals||New functionality is available when using the portal editor. You can utilize Content Blocks and Liquid Markup to conditionally show information within a Portal, such as a Custom Applicant Status Portal.|
|Retention Policies||Retention Policies||
The prior version utilizes Local and Slate Template Library query bases, while all retention policies are built on the configurable join query bases in the new version. The new version also utilizes a group structure which enables you to organize policies to execute the deletion of like data.
Triggers have been deprecated and should no longer be used. As communicated throughout 2013 and 2014, custom SQL triggers would be retired and were formally deprecated on September 1, 2014. Rules provide much more efficient, comprehensive functionality. Existing custom SQL triggers continue to function in a limited capacity as final migrations to rules are completed.