private void updateProperties(TurmsProperties properties) {
        GroupInvitationProperties invitationProperties = properties.getService()
                .getGroup()
                .getInvitation();

        allowRecallPendingInvitationByOwnerAndManager =
                invitationProperties.isAllowRecallPendingInvitationByOwnerAndManager();

        allowRecallPendingInvitationBySender =
                invitationProperties.isAllowRecallPendingInvitationBySender();

        int localMaxContentLength = invitationProperties.getMaxContentLength();
        maxContentLength = localMaxContentLength > 0
                ? localMaxContentLength
                : Integer.MAX_VALUE;

        deleteExpiredInvitationsWhenCronTriggered =
                invitationProperties.isDeleteExpiredInvitationsWhenCronTriggered();

        int localMaxResponseReasonLength = invitationProperties.getMaxResponseReasonLength();
        maxResponseReasonLength = localMaxResponseReasonLength > 0
                ? localMaxResponseReasonLength
                : Integer.MAX_VALUE;
    }
@author James Chen
@implNote The status of group invitations never become EXPIRED in MongoDB automatically (admins
          can specify them to expired manually though) even if there is an expireAfter property
          because Turms will not create a cron job to scan and expire requests in MongoDB.
          Instead, Turms transforms the status of requests when returning them to users or admins
          for less resource consumption and better performance to expire requests.
turms-service/src/main/java/im/turms/service/domain/group/service/GroupInvitationService.java