Thanks a ton Ruth. Yes, I do require help on sd_event as this is first time I will be working on the same.
My requirement is like this... Whenever A service call with a classification- Create email account is resolved, I need a change ticket to be logged with some of the field details from the service call automatically and assigned to the change team.
You also have the option of using sd_dataform to create the ticket, if you want the new ticket to be displayed on the screen of the user who resolved the Service call. In this case, use a UI rule instead.
1) Create an application that runs sd_dataform.bat 2) Create a smart action that uses that application. The parameters will include: a) the name of the form to use to display the change b) -forcenew, to make sure that a new change is created c) += (repeated as often as required).
For example, if you want to set the Title of the Change to the Title of the Service Call, then
The usage of sd_dataform.bat is fairly well documented in the manual.
3) Create a UI rule to run the smart action. Typically, you would use a boolean field formatted as a button. Click the button to run the UI rule.
If you are using service pages a UI rule will not fire and so as Josh says, you will need to use a DB rule. But then you cannot use sd_dataform as DB rules obey on the server not the client.
This means you will have to use the sd_event approach.
To use sd_event to set up a change, first set up a chnage record template which has the settings you want. Then set up an import mapping for a change which uses this template and define attribute mappings for the fields you want to take across from the SC; for example, deswc for Description, inf for Information etc.
Then try an sd_event to set up a change: sd_event -s Server -p Port -a account/password -x mapping -c class -v desc=[Description] inf=[Information] ...