The goal of this ticket was to update the reinstatement task page so it includes the license status. We previously implemented an additional field that was originally intended to contain all of the content that would exist above the status component however, after talking to the Contant team, we realize this additional field was not needed. Therefore, we deleted it all reinstatements in the file. Separately, we added the necessary previews and enabled the search functionality over the default fields.
Steps to Test
Notes
Code author checklist
[x] I have rebased this branch from the latest main branch
[x] I have performed a self-review of my code
[x] I have created and/or updated relevant documentation on the engineering documentation website
[x] I have not used any relative imports
[x] I have pruned any instances of unused code
[x] I have not added any markdown to labels, titles and button text in config
[x] If I added/updated any values in userData (including profileData, formationData etc), then I added a new migration file
[x] I have checked for and removed instances of unused config from CMS
[x] If I added any new collections to the CMS config, then I updated the search tool and cmsCollections.ts (see CMS Additions in Engineering Reference/FAQ on the engineering documentation site)
[x] I have updated relevant .env values in both .env-template and in Bitwarden
…time Action
Description
Ticket
https://www.pivotaltracker.com/story/show/188079164
Approach
The goal of this ticket was to update the reinstatement task page so it includes the license status. We previously implemented an additional field that was originally intended to contain all of the content that would exist above the status component however, after talking to the Contant team, we realize this additional field was not needed. Therefore, we deleted it all reinstatements in the file. Separately, we added the necessary previews and enabled the search functionality over the default fields.
Steps to Test
Notes
Code author checklist
userData
(includingprofileData
,formationData
etc), then I added a new migration filecmsCollections.ts
(see CMS Additions in Engineering Reference/FAQ on the engineering documentation site).env
values in both.env-template
and in Bitwarden