The use case is that users are filing permits and then using a custom object to track the permit lifecycle. Permits usually have expiration dates and it's common to file for extensions that necessarily result in new expiration dates. I want them to have one field displaying the current expiration date, but also be able to see the original and any other extensions. Just tracking field history won't give enough context around the date changes. My current thought is this:
- Original Expiration Date: date field populated when record is created
- Current Expiration Date: date field that shows the most current date. Will mirror above field if no extensions are made
- Detail object for tracking extension date and extension status. When extension is approved, Expiration Date on master record is automatically updated.
Any feedback or suggestions are much appreciated!
Sounds like you could do this with a pretty simple screen flow on the record page or being called by a quick action on your permit record page.
So when your users click "file extension" you can pull in the expiration date of the current record and then display the details of the other extensions related to the permit in a data table.
The screen flow can then finish by creating the new extension record.
