Existing absence approval transactions and draft absences before enabling Redwood

Summary:

Pre-requisites for existing absence approval transactions and draft absences before enabling Redwood

Content (please ensure you mask any confidential information):

Need to confirm pre-requisites for existing absence approval transactions that are pending and absence entries that are marked as draft.

1. For pending absence approval transactions before enabling Redwood - We need to get all transactions completed
2. For absences that were saved in Draft mode no additional action needed, user will be able to edit absence in redwood under existing absences and submit for approval

Please share if the above is correct understanding and any known issues or other observations to consider?