On Oct 1, 2014, at 3:08 PM, Falcon ICT Pty Ltd <[email protected]> wrote:
> @Jacopo > > The thruDate is used to establish when the subscription is scheduled > to expire, so cannot also be used to determine that the service has > run, which can happen whenever it is scheduled. Hence the need for > another field. Ok, I was imagining something similar; then your proposal makes sense to me even if maybe we could name the new field "expirationDate" or "effectiveExpirationDate" or "expirationCompletedDate" or similar rather than "serviceNameOnExpiryRunDate". Jacopo
