Relativity Classic Forms Deprecation
The Use Relativity Forms setting on an object type determines whether Relativity Forms will be used. Depending on the configuration of this field, the behavior may be different during the deprecation phases of Classic forms deprecation.
The possible setting values are:
- Yes: use Relativity Forms to render the Layout (view, edit, and new) pages for objects of this type. This option is selected by default.
- No: do not use Relativity Forms for objects of this type.
- Unset: the DefaultUseRelativityFormsValue Instance Setting will be used.
The deprecation of Classic Forms will take place in two phases. The first phase will change the behavior of an object type when Use Relativity Forms is unset. The second phase will cause the Use Relativity Forms value to be ignored.
The first phase will begin on May 31, 2022. Before the changes in this phase are applied, an unset Use Relativity Forms value would cause an object type to be rendered using the classic forms rendering engine, as shown in the example below:
After the changes in this phase are applied, an unset Use Relativity Forms value would cause an object type to be rendered using the Relativity Forms rendering engine, as shown in the example below:
The rendering behavior for object types with Use Relativity Forms values of Yes and No will remain unchanged after the first phase. i.e. Yes will Relativity Forms for rendering and No will not use Relativity Forms for rendering objects of that type.
For many object types this will not be cause for concern, but there are some key differences between the functionality of classic forms and Relativity Forms, as described in Migrating applications to Relativity Forms.
The second phase of the migration will occur in September 2022. This phase will cause all object types to display using the Relativity Forms rendering engine, regardless of the value set for Use Relativity Forms.
Classic Forms Deprecation Compliance Identification Tool
To assist in the migration from Classic Forms to Relativity Forms, we are providing an identification tool to determine if an object type will be negatively impacted by the migration. By default, this identification tool attempts to return every object type in every workspace, listing whether at least one .NET PageInteractionEventHandler, Pre-Load event handler, or Console event handler is present. The presence of these three event handlers on a Classic Forms page indicates action may be necessary to migrate to Relativity Forms.
Note: This Identification tool is only provided for convenience. Do not rely on this tool for comprehensive reporting or absolute accuracy.
To use the provided tool:
- Download the SQL script provided at https://community.relativity.com/s/contentdocument/0691T00000I9d8jQAB (Note: Relativity Community login is required to access this resource)
- Create a new Relativity Script in the Relativity Script Library and copy the contents of the SQL script you downloaded in Step 1 into your new script.
- Give the script a name and description, provide other settings as needed, and set the timeout value to 180 seconds.
- The script can be freely used in the Relativity Script Library on the admin level
In the Modifiable Filters section at the start of the script, four variables are available that you can change to 1 or 0 to filter the list down to relevant results. Once the results appear, you can export them to a CSV file for further manipulation and filtering. Note that Relativity-provided objects will be included in the results and do not require action on your part, provided that you have not added your own custom event handlers to those Relativity-provided objects.