Sorry I meant is there a way to attach the source email to the event as a .eml file?Same goes if it’s an update - I’d like the source .eml file to be attached to the action.
My kind apologies everyone - after importing the channels from the wiki and looking into the config… I didn’t bother looking at the Source menu. I see it now - thank you Paul and KevinM for your kind replies. I’ll be playing around with it some more to see if I can figure everything out. :)
Thank you so much Paul - this is really helpful.
Did you upgrade the DBArchive package that is included in the installation package? It is version specific.Also - you may need to apply the required schema change.Hope this helps.
Hi Is this what you are looking for? https://wiki.axiossystems.com/assyst11-5Wiki/index.php/Integrations:assystREST_More_Examples#Attachments I saw this but it did not provide an example on how to use it within a LUA script. For example adding a new attachement with assystREST in lua is:ASSYSTREST:new_attachmentWhat would be the GET command for retrieving attachment information?We tried get_attachment, getattachment, and other combinations that didn’t work.
No sweat Duncan, glad to help!We are running only one instance at a time - sending 5000 events per run. It looks like our batch size is setup to 50.Our automated program will send 5000 events to the Archive Utility, once complete wait 5 minutes and then continue on with another run… it will continue this loop until we stop the process.It actually has been running okay with no DB disconnects since 2pm Nov 1st…. running non stop it has deleted 565455 actual events in 58 hours - this is in our TEST environment.
Hi Duncan,We are currently working with IFS for an automated archive solution as we have millions of records to delete as well.We had extremely slow performance where deleting 200 events would take 45 minutes.They identified an index that could be added…. and we lowered the processing time from 45 minutes to 2.5 minutes to delete 200 events.I can’t seem to find the index information however… But just quote our incident number in working with IFS which is 369418. Perhaps you’re DB would benefit from that same index… or at least you could test it in non-prod to see if it helps.One thing to note though - when running multiple batches, archiving so many events is causing our DB to temporarily disconnect. We are still working on that one…. :(Cheers.Martin
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
