Does anyone have any advice on how to use the ETM to return a list of events that were closed 2 years ago. I can get a list of events, I am struggling with the date of closure parameter. I am then going to push these events through another datamapper which will remove sensitive information. I have tried using the “daysFromEventClosure” drop down with no success.
Solved
ETM datamapper - date closure
Best answer by Paul McCulloch
I would use a channel with an assyst REST source, and specify a suitable query to get the events you want to close. The generated import will have 1 record per event & will be simpler and more efficient than using 1 mapper to process the results of another.
Setting an assyst REST Subpath of /events?eventType=INCIDENT&daysFromEventClosure=5475 will bring back incidents that were closed at least 15 years ago.
Here’s what a suitable channel will look like. Note that my CRON Expression specifies that it only runs in the year 2030. This is a way to make channel that only runs when manually triggered.
I would use a channel with an assyst REST source, and specify a suitable query to get the events you want to close. The generated import will have 1 record per event & will be simpler and more efficient than using 1 mapper to process the results of another.
Setting an assyst REST Subpath of /events?eventType=INCIDENT&daysFromEventClosure=5475 will bring back incidents that were closed at least 15 years ago.
Here’s what a suitable channel will look like. Note that my CRON Expression specifies that it only runs in the year 2030. This is a way to make channel that only runs when manually triggered.
I would use a channel with an assyst REST source, and specify a suitable query to get the events you want to close. The generated import will have 1 record per event & will be simpler and more efficient than using 1 mapper to process the results of another.
Setting an assyst REST Subpath of /events?eventType=INCIDENT&daysFromEventClosure=5475 will bring back incidents that were closed at least 15 years ago.
Here’s what a suitable channel will look like. Note that my CRON Expression specifies that it only runs in the year 2030. This is a way to make channel that only runs when manually triggered.
Thanks for this, I am getting the following error when setting up the channel, any ideas?
Configuration ErrorError with source configuration: com.axiossystems.integration.importtool.sources.SourceValidationException: org.apache.camel.http.common.HttpOperationFailedException: HTTP operation failed invoking http://*server*:8080/assystREST/v2/events?eventType=INCIDENT&daysFromEventClosure=5475 with statusCode: 400
How would this work in terms of the datamapper being setup? Would a standard assyst datamapper with the record to update field = inbound.id?
Note sure about the 400 error - that’s coming from assyst REST. The server.log on the core assyst server may explain what went wrong.
If that doesn’t help then use Postman/curl/browser to hit that URL and see if the response gives any clues.
Yes -that’s exactly what you need if you want to update the events that are retrieved.
It occurred to me that you’d probably want a way to avoid double processing events. One option would be to take a User Status action as part of the processing you perform. This makes it fairly easy to exclude such events from subsequent runs.
In may case I take a user status action with action type ID 279. My Channel URL then becomes
/events?eventType=INCIDENT&daysFromEventClosure=5475&userStatusId[exclude]=279
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.