The User Help for RapidResponse 9.5 includes an example:
This is also available in the User Help PDF.
Does this help?
Manager, User Education
I feel the documentation has never been very helpful to configure this. We figured out how to do this at Flextronics via "trial & error".
My understanding is that this should be configured by an administrator since everything that you refer to in the "Post Processing" specification must be accessible to the RapidResponse AlertService process. At least in our configuration, this process is owned by a local service account that has no access to anything outside of the Data Server. That is, it can't see anything on your workstation, any other Users workstation or even a network drive. If it's not on the Data Server then it does not exist for the Alert Service Task and will fail. Note that even file system permissions can cause you nightmares since, again, this is a local system account that may not be granted access to write to the output folder you've specified. I don't feel that this is a failure in the Kinaxis design but simply the burden of more secure modern networks.
We use this feature heavily at Flextronics but only to transfer the export file generated by the AlertService Task from the Data Server back to a Site's ERP, Site's File Server (allow Users to access), Customer or Supplier FTP sites.
Here's how we've configured this:
Good luck to you since this has been a wonderful feature for us since 2002. We couldn't function without it since e-mail is a horrible delivery mechanism. I haven't checked the knowledgebase but Kinaxis Support may already offer a better presentation & perspective than I. Hopefully, a future version will improve the presentation of this so that configuration will be more intuitive.
Our approach was very similar but dumbed down a step so a non-techy like me understood it!
Step 1. We created a .bat file to do ... whatever it is we needed to do. This file along with any vb script/.txt etc that the bat called out were all kept in our 'downloads' folder, same as the .tab file that resulted from the alert run:
Step 2. In alert properties, advanced function, just call out the .bat file for post processing:
again .. ultimately no different from the previous example, maybe just one step simpler from a power user poin-of-view rather than system admin!
There are a couple of steps we have taken and one we intend to take:
1. We have closed down the downloads folder to general end-users (no longer a shared folder).
2. To the more techy end-users we allow them exceptional access to the downloads folder to create their bat files etc.. VERY limited, I'd say we have maybe 5 people/applications that are allowed in.
3. Our technical admin created a vb job that every 15minutes copies all .tab and .xls files from downloads to a shared public folder
4. We do have a couple of critical production jobs (ex. closed loop to our erp) that rely on the downloads folder, our intent is to create a seperate completely sealed off downloads location just for those jobs so there is absolutely no exposure to anyone other than the technical and data admin.
Hope this was useful.