Comments
-
Thank you both for your replies. I didn't think there was any issue, but it seemed odd that the documentation had it as a separate policy. I knew it worked in the same policy. I just was curious if there was a specific reason that the documentation showed it as a separate policy.