When we configure a Vendor Assesment to recurrence after 30 days, its seems that Eramba will clone the original Vendor Assessment from the state the original Vendor Assessment has been left.
So if we configure a Vendor Assessment and an Auditee doesn’t submit or finish the VA before 30 days. The “new” cloned VA is in the same state as the original unfinished VA.
Hope this makes sense?
A work-around would be to ensure that all ongoing VA’s are submitted within the recurrence period, but that would just be even more administrative work in coordinating and keeping track on ongoing VA’s.
Suggestion: Remember to initialize the cloned VA object - unless it actually is on purpose that the cloned VA should have the same state as the unfinished original VA?