If this is scheduled I assume that the WOs will be the same and CIs will be the same. If this is the case, just modify the "template" used in the import mapping to include workorders with the necessary configuration items.
You are correct. This is quarterly maintenance which will have the same 5 WO's and the same related CI's per each WO.
I finally got it working from the cmd line. I created the SC template with a WO template and CI template. I'm on 4.5 SP with a known error (restart services for template changes) once I did this, the CI now appears on the related WO.
My next build will have different CI's monthly but I haven't received all requirements.
I'm hoping you might be able to help. I got the sd_event to work in my test environment but when I try to run it from a cmd line in the production envir, it takes up all resources where my end-user can not open the client or anything in a open client appl.
cmd line: %sd%\sd_event.exe -f pm.ini -v sid=1400
I have SC import file with attached 4 WO's with related CI's (anywhere from 1 to 6 ci's)
I didn't receive any errors and log file showed "server_response=server didn't return any messages: check your appl server".
Since that works in your test environment there must be something else that make it fail on the production environment.
By default sd_event communicates with the application server on the port 30980 (open the server settings editor and have a look at the tab http. This must be activated for sd_event to work and the machine where you run sd_event must be able to communicate with the application server on that port.