The way the get latest revision tool works today does not enable us to use the functionality. When the event is written to the commonLifecycleEventLog table we have assumed the glr was complete and all specs were connected to the latest version of the consumed spec. In fact, the event is written and the revision happens at a later time. Can you write another event to the table after all the revisions have been repointed?
We used the event as a queue to update the print model, but we cannot do this, because the spec tree changes after the event is written to the commonLifecycleEventLog table.