Would this behavior differ for Workflow SDK scripts?

I've been using WF to test the code, but instead of an Export event I just end up with a separate View Document event for each page.

I verified the Export event is being tracked and I can get it to appear if I use that account directly in the Client, just not in the Workflow SDK Script.

I've tried establishing a separate session in the script without using the RASession, but now I'm wondering if Workflow SDK scripts behave differently.

For the custom audit events, I found that section of the documentation, thank you.

Can you post the script?

Miruna,

Below is a "bare bones" version of the script without the search function or the logic to decide between read and export.

RepositoryRegistration repository = new RepositoryRegistration(serverName,repoName);
Session session = new Session();
session.LogIn(userName,password,repository);

// Set output path and file name
string fileName = "Test File";
string outputPath = @"\\TEST\D$\";

// Retrieve document
DocumentInfo doc = Document.GetDocumentInfo(entry,session);
bool hasEdoc = doc.IsElectronicDocument;

// If no electronic document found, generate PDF
int pageCount = doc.PageCount;

// Create document exporter and apply settings
DocumentExporter dExp = new DocumentExporter();
dExp.CompressionQuality = 75;
dExp.IncludeAnnotations = true;
dExp.BlackoutRedactions = true;
dExp.PageFormat = DocumentPageFormat.Jpeg;

// Set export options
PdfExportOptions ExportOptions = new PdfExportOptions();
ExportOptions = PdfExportOptions.IncludeText | PdfExportOptions.RenderAnnotationsAsImage;

// Attempt to generate the PDF
try {
    // Generate PDF document
    dExp.ExportPdf(doc, doc.AllPages, ExportOptions, outputPath + fileName + ".pdf");
}
finally {
    session.LogOut();
}

Thank you both. I was getting the impression that manually reporting the audit event I wanted would be necessary based on my results so far.

It looks to me like the SDK is pulling each page and then generating the PDF externally, therefore it doesn't register as an export event.

This would explain why all I'm seeing is a separate "View Document" event for each page when it is running the DocumentExporter code.

Hi Robert,

We have a vendor building out another similar process for a new system that uses the Java SDK. Is the Java SDK also capable of reporting standard Audit Events?

I looked through the Java SDK documentation and saw that there is a ReportAuditEvent method for Custom events, but I didn't see an equivalent to the .NET AuditEvent.

JRA has the CustomAuditEvent class, set the properties on that object and call reportAuditEvent().

Just to be 100% clear, the CustomAuditEvent class in the JRA does not allow reporting of standard auditing events, correct?

If that is the case, I'll need to use a custom event in both the .NET and Java applications to ensure both are reporting the same event.

I've tested the .NET version of the CustomAuditEvent, but Audit Trail is not showing any of the custom audit event class information.

Additionally, when I attempt to add both a description and an Entry, it will only include the first one added in the database (only prop_index is 0).

The audit_custom table seems to be empty. When I execute the code and log the custom event ID I get a value, but it doesn't appear to be logging it in the database, which I'm assuming is why the reports don't show any additional data.

Here is the code I used to create the event:

CustomAuditReason customEvent = new CustomAuditReason(session);
customEvent.EventName = "PDF Generated";
customEvent.Save();

And here is the code I've been using to report the event:

CustomAuditReasonReader reader = new CustomAuditReasonReader(session);
while (reader.Read())
{
    if (reader.Item.EventName == "PDF Generated")
    {
        CustomAuditReason reason = reader.Item;
        CustomAuditEvent e = new CustomAuditEvent(reason,session);
        
        // verified that the correct reason is selected
        Console.WriteLine(reason.EventName + ": " + reason.Id);
       
        e.AddEntry(entry); // works
        e.Add("TEST","Value"); // does not work
        e.AddTrustee(Account.GetInfo(username,session)); // works
        e.ReportAuditEvent();
    }