There are standard change orders that are used to take place regularly. Can SDM schedule reoccurring change orders based on a schedule?
You can use bop_cmd or webservices to automaticaly create change order. For sheduling purposes you can use default OS scheduler.
Personally, I would do this using a PAM process launched by a scheduled task. You will want to launch the recurring changes by creating them from a template – PAM can access the full range of functionality needed to do that.
Yes i agree that this may be the simplest solution. So in this case we will have Executeble->PAM ->WebServices?
That’s correct – launching the desired PAM process through the PAM web service.
So then it is not so easy:
Executable will use PAM WS to launch PAM process, that will use SDM WS to create the ticket. I think then it much easier and more generic method to call WS directly.
I'm wondering if one could just do a PAM process in a loop, runs a operator (SDM Web Service call to create an SDM CO), waits until the next scheduled time and goes again.
Maybe this way we can remove the external executable scheduling aspect using this approach?
Guys, no need of an executable. Way to complicated. Everything you need is ootb in PAM. Take a look at these steps.
PS: As usual, i'm using a french version so maybe the terms i use are not the exact translation.
1 -Create a simple process to create a change order.
2 -Create a calendar in PAM
3 -Create a Planification
4 -Add some planification element by double clicking your process in the list on the left
5 -Click on the little button (properties) at the right of the planification item that just appeared, and in inclusion calendar, select the calendar that you've created at step 2.
6 -You will have two tabs in your planification element, select the second one, specific. Process dataset initialisation code.
7 -Type here the value you'll need to create your change (Process.category="Standard";Process.Assignee="peterPan001";)
Cool! One of the things I like most about the community is when someone points out some functionality that I’ve never looked at.
why wouldn't we just use the pdm_text_cmd to create a Change based on that , you could batch job the command and use windows scheduler to create the ticket based on the schedule there , less work and more cleaner , it seems the requirement is to flat out just create a change and nothing fancy.
I've had clients do the above for event driven tickets (Incidents) all the time ....
Example: Use an Input File to Create Multiple Changes
The following example demonstrates creating multiple changes with one input file. This command can be helpful creating test data on a test system.
%DESCRIPTION=This is Test 1.
%DESCRIPTION=This is Test 2.
%DESCRIPTION=This is Test 3.
To process this file, assuming its full path is c:\testdata.txt, issue the following command:
pdm_text_cmd -t Change –u ServiceDesk -f c:\testdata.txt
You could also use a change template as a parameter to the input file by using the syntax of
Retrieving data ...