pp108 : DeleteSchedule

DeleteSchedule


This method is used to delete a schedule. DeleteSchedule is a part of the Methodset Scheduler 1.0 in the Cordys Scheduler application package.

SOAP Requests

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
        <DeleteSchedule xmlns="http://schemas.cordys.com/scheduler/1.0">
            <tuple>
                <old>
                    <schedule count="3" templateid="7F0EDCA7-E3FD-482D-A206-53813B926334">
                        <scheduleid>B87D16D2-95FB-4369-B4A8-80145144E0A5</scheduleid>
                        <name>HourlySchedule</name>
                        <organizationalcontext>o=system,cn=cordys,o=vanenburg.com</organizationalcontext>
                        <datetime>
                            <hourly>
                                <minutes>0</minutes>
                                <minutes>30</minutes>
                            </hourly>
                            <starttime>2007-03-07 12:00:00</starttime>
                            <endtime>-1</endtime>
                        </datetime>
                        <scheduleat>2007-03-07 12:00:00</scheduleat>
                        <listener>cn=Northwind Service,cn=soap nodes,o=system,cn=cordys,o=test.com</listener>
                        <parameters>
                            <GetEmployee xmlns="http://schemas.cordys.com/1.0/demo/northwind">
                                <EmployeeID>101</EmployeeID>
                            </GetEmployee>
                        </parameters>
                        <owner>cn=Jdoe,cn=organizational users,o=system,cn=cordys,o=test.com</owner>
                    </schedule>
                </old>
            </tuple>
        </DeleteSchedule>
    </SOAP:Body>
</SOAP:Envelope>
Request Parameters

Parameter

Description

 Mandatory Accepted Input Values

scheduleid

 ID of the schedule Yes GUID

count

Number of times the schedule instance will be executed:

  • A positive value indicates the number of times the instance will be executed.
  • A value of '-1' indicates that the schedule instance will execute infinitely based on the defined conditions such as a specified duration.
 No

templateid

ID of the schedule model

 No

name

Name of the schedule model

 No

organizationalcontext

Organization in which the schedule is set to run

 No

datetime

Details of the schedule types as defined in the schedule model. For example, hourly, daily, weekly, monthly, firstdayofmonth, lastdayofmonth, firstweekday, lastweekday, fortnightly, and so on. If the schedule model is defined only for manual execution, then the value will be 'runnow'.

 No Provide the following datetime values:
  • <hourly> - accepts <minutes> in the 'mm' format
  • <daily> - accepts <time> in the 'mm:ss' format
  • <weekly> - accepts <weekday> in the 'dd hh:mm' format
  • <monthly> - accepts <time> in the 'hh:mm:ss' format
  • <firstdayofmonth> - accepts <time> in the 'hh:mm' format
  • <lastdayofmonth> - accepts <time> in the 'hh:mm' format
  • <firstweekday> - accepts <time> in the 'hh:mm' format
  • <lastweekday> - accepts <time> in the 'hh:mm' format.
  • <fortnightly> - accepts <time> in the 'hh:mm' format

scheduleat

Date and time at which the schedule will run next

 Yes yyyy-mm-dd hh:mm:ss

listener (deprecated)

DN of the service container, which must participate when the schedule is executed at the specified time. The value of the listener is based on the actions defined in the schedule model.

Do not depend on the value of the listener as it is deprecated.

 No

parameters

SOAP request that will be considered for triggering the action at the scheduled time

 No

owner

User who instantiated the schedule. If the 'auto-deploy' is on, then the user will be the same as the user who deployed the model. If the 'auto-deploy' is off, then it will be the user who activated the schedule.

 No

SOAP Response

<data>
    <DeleteScheduleResponse
        xmlns="http://schemas.cordys.com/scheduler/1.0" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
        <tuple xmlns="http://schemas.cordys.com/scheduler/1.0">
            <old>
                <schedule count="3" templateid="7F0EDCA7-E3FD-482D-A206-53813B926334">
                    <scheduleid>B87D16D2-95FB-4369-B4A8-80145144E0A5</scheduleid>
                    <name>HourlySchedule</name>
                    <organizationalcontext>o=system,cn=cordys,o=test.com</organizationalcontext>
                    <datetime>
                        <hourly>
                            <minutes>0</minutes>
                            <minutes>30</minutes>
                        </hourly>
                        <starttime>2007-03-07 12:00:00</starttime>
                        <endtime>-1</endtime>
                    </datetime>
                    <scheduleat>2007-03-07 12:00:00</scheduleat>
                    <listener>cn=Northwind Service,cn=soap nodes,o=system,cn=cordys,o=test.com</listener>
                    <parameters>
                        <GetEmployee xmlns="http://schemas.cordys.com/1.0/demo/northwind">
                            <EmployeeID>101</EmployeeID>
                        </GetEmployee>
                    </parameters>
                    <owner>cn=Jdoe,cn=organizational users,o=system,cn=cordys,o=test.com</owner>
                </schedule>
            </old>
        </tuple>
    </DeleteScheduleResponse>
</data>

Response Parameters

Parameter

Description

count

Number of times the schedule instance will be executed:

  • A positive value indicates the number of times the instance will be executed.
  • A value of '-1' indicates that the schedule instance will execute infinitely based on the other conditions that were defined such as the specified duration.

templateid

ID of the schedule model

scheduleid

ID of the schedule

name

Name of the schedule model

organizationalcontext

Organization in which the schedule is set to run

datetime

Details of the schedule types as defined in the schedule model. For example, hourly, daily, weekly, monthly, firstdayofmonth, lastdayofmonth, firstweekday, lastweekday, fortnightly, and so on. If the model is defined only for manual execution, then the value will be 'runnow'.

scheduleat

Date and time at which the schedule will run next

listener (deprecated)

DN of the service container, which must participate when the schedule is executed at the specified time. The value of the listener is based on the actions defined in the schedule model.

Do not depend on the value of the listener as it is deprecated.

parameters

SOAP request that will be considered for triggering the action at the scheduled time

owner

User who instantiated the schedule. If the 'auto-deploy' is on, then the user will be the same as the user who deployed the model. If the 'auto-deploy' is off, then it will be the user who activated the schedule.