If you had chatted with Presales or attended a CFW with them, you would need to contact them to get a copy of the transcripts. Besides this thread, the only other interaction with Support is through the case you opened this morning. Please make your updates in the case instead of this thread. We'll revisit this thread to post the resolution.

Microsoft was unable to say definitively if this issue was / is purely a Laserfiche issue. They suspect it may be a combination of cache, LF, SQL and even OS. The following trigger script has been implemented and should stop reversions from occurring.

USE [Workflow]
GO
/****** Object: Trigger [dbo].[insteadofupdate] Script Date: 07/29/2014 10:42:44 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER trigger [dbo].[insteadofupdate] on [dbo].[workflow_code]
Instead of update
as
declare @workflow_id [int],
@version [int],
@last_update datetime,
@temp datetime
select @workflow_id=i.workflow_id from inserted i;
select @version=i.[version] from inserted i;
select @last_update=i.last_update from inserted i;
select @temp = [last_update] from workflow_code where workflow_code.[workflow_id]= @workflow_id

if (@last_update > @temp)
begin
update workflow_code
set
[designer_code]=a.designer_code,
[workflow_assembly]=a.workflow_assembly,
[last_update]= a.last_update,
[version]=a.[version],
[csharp_assembly]=a.[csharp_assembly],
[vb_assembly]=a.[vb_assembly]
from workflow_code u inner join inserted as a on u.workflow_id=a.workflow_id
end
else
rollback