pp108 : GetSchedulesBetweenDate

GetSchedulesBetweenDate


This method is used to retrieve schedules that are set to run between the specified dates. GetSchedulesBetweenDate is a part of the Methodset Scheduler 1.0 in the Cordys Scheduler application package.

SOAP Request

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
        <GetSchedulesBetweenDate xmlns="http://schemas.cordys.com/scheduler/1.0">
            <fromdate>2012-04-04 00:00:00</fromdate>
            <todate>2013-04-04 00:00:00</todate>
        </GetSchedulesBetweenDate>
    </SOAP:Body>
</SOAP:Envelope>
Request Parameters

Parameter

Description

Mandatory

Accepted Input Values

fromdate

Start date to retrieve the schedules, which get executed after this date

Yes

yyyy-mm-dd hh:mm:ss

todate

End date to retrieve the schedules, which get executed before this date

Yes

yyyy-mm-dd hh:mm:ss

SOAP Response

<data>
    <GetSchedulesBetweenDateResponse
        xmlns="http://schemas.cordys.com/scheduler/1.0" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
        <dataset xmlns="http://schemas.cordys.com/scheduler/1.0">
            <tuple>
                <old>
                    <schedule count="-1" templateid="002481F0-8E9F-11E2-EF63-176C417E7BA6">
                        <scheduleid>002481F0-8E9F-11E2-EF66-DC7B9E075BA6</scheduleid>
                        <name>testSc</name>
                        <organizationalcontext>o=system,cn=cordys,cn=test,o=test.com</organizationalcontext>
                        <datetime>
                            <daily>
                                <time>5:00</time>
                            </daily>
                            <starttime>2013-02-20 13:54:07</starttime>
                            <endtime>-1</endtime>
                        </datetime>
                        <scheduleat>2013-02-21 05:00:00</scheduleat>
                        <listener/>
                        <parameters>
                            <ExecuteProcess xmlns="http://schemas.cordys.com/bpm/execution/1.0">
                                <type>definition</type>
                                <receiver>Test</receiver>
                                <source>Scheduler Engine</source>
                                <modelSpace/>
                                <message>
                                    <Message>No Message</Message>
                                </message>
                            </ExecuteProcess>
                        </parameters>
                        <owner>cn=tester,cn=organizational users,o=system,cn=cordys,cn=test,o=test.com</owner>
                    </schedule>
                </old>
            </tuple>
            <tuple>
                <old>
                    <schedule count="1" templateid="002481F0-8E9F-11E2-EF66-D48159379BA6">
                        <scheduleid>002481F0-8E9F-11E2-EF68-3BAD3F6B7BA6</scheduleid>
                        <name>runnow</name>
                        <organizationalcontext>o=system,cn=cordys,cn=test,o=test.com</organizationalcontext>
                        <datetime>
                            <date>20</date>
                            <day>-1</day>
                            <month>1</month>
                            <year>2013</year>
                            <hour>15</hour>
                            <minute>12</minute>
                            <second>50</second>
                            <starttime>2013-02-20 15:12:50</starttime>
                            <endtime>-1</endtime>
                        </datetime>
                        <scheduleat>2013-02-20 15:12:50</scheduleat>
                        <listener/>
                        <parameters>
                            <GetCaseModel xmlns="http://schemas.cordys.com/casemanagement/modeladministration/1.0">
                                <model name="test" space="organization"/>
                                <status>
                                    <status/>
                                </status>
                            </GetCaseModel>
                        </parameters>
                        <owner>cn=tester,cn=organizational users,o=system,cn=cordys,cn=test,o=test.com</owner>
                    </schedule>
                </old>
            </tuple>
        </dataset>
    </GetSchedulesBetweenDateResponse>
</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 defined conditions such as a specified duration.

templateid

ID of the schedule model

name

Name of the schedule

organizationalcontext

Organization in which the schedule is set to run

datetime

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

scheduleat

Date and time when 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.