#include <outboxstojobs.h>
Inheritance diagram for HBCI::OutboxJobDeleteStandingOrder:
Public Methods | |
OutboxJobDeleteStandingOrder (Pointer< Customer > c, Pointer< Account > a, const StandingOrder &order2Delete) | |
~OutboxJobDeleteStandingOrder () | |
const StandingOrder & | standingOrder () const |
bool | createHBCIJobs (Pointer< MessageQueue > mbox, int n=0) |
bool | evaluate () |
bool | stillMessagesToSend (int nextMsg) const |
bool | commit (int msgNumber=HBCI_COMMIT_WHOLE_JOB) |
string | description () const |
JobProgressType | type () const |
list< int > | resultCodes () const |
Static Public Methods | |
int | minDaysBeforeDelete (const Bank &forBank) |
int | maxDaysBeforeDelete (const Bank &forBank) |
bool | deletionTerminable (const Bank &forBank) |
bool | isSupported (Pointer< Account > forAccount) |
Checks if deleting a standing order is supported for the specified account. |
This job deletes an existing standing order. If the bank does not support terminable deletions, you should set StandingOrder::setExecutionDate() to Date() (a zero-date), otherwise it has to be a future execution date.
|
|
|
|
|
Call this method to commit changes to the system. Since Jobs do not change the system you may call this method to commit the changes. A job for getting the balance for example may decide to store the retrieved balance in the corresponding account.
Implements HBCI::OutboxJob. |
|
Let the job create the "real" jobs and add them to the message queue given.
Implements HBCI::OutboxJob. |
|
Bank-information - needed to create a valid deletion-job |
|
Return a short description of what the job is supposed to do.
Implements HBCI::OutboxJob. |
|
Let the job check the result and set the flags. Let the job check the result. This means checking the results of all Jobs involved (which otherwise is not done automatically). This method sets its status and result accordingly -- otherwise the status and result flags might not be up-to-date.
Implements HBCI::OutboxJob. |
|
Checks if deleting a standing order is supported for the specified account.
If this method returns <false>, your application should provide a way to allow this job anyway because some banks just don't tell you that they support this job for the specified account. Only if <true> is returned, you can be sure this job is supported. |
|
Bank-information - needed to create a valid deletion-job |
|
Bank-information - needed to create a valid deletion-job |
|
Returns a list of result codes of this job. This can be used to get more detailed information if the result of this job was HBCI_JOB_RESULT_FAILED. In that case, you can traverse this list, checking for resultcodes >= 9000. Each of those can be the source of the job failure, so you can react accordingly. HBCI spec suggests that the most important of them can be found at the front() already, but that depends on your bank. Note: A resultcode >= 9000 does not automatically mean an error, see MessageQueue::getResult().
Implements HBCI::OutboxAccountJob. |
|
Return the order this job is/was supposed to delete. |
|
Returns true if there are still messages to be sent. Checks if there are still messages to be sent. This is needed because some jobs don't know the number of messages they consist of, until they are executed.
Reimplemented from HBCI::OutboxJob. |
|
Return the JobProgressType of this job.
Implements HBCI::OutboxJob. |