...
FQCN of the action class: com.CDRator.billing.financial.ekspresbank.action.GetApplicationStatusAction
This action will poll for the status of an application referenced by the supplied ApplicationGUID.
Input Arguments
The action takes three arguments:
...
This action returns an object of type ApplicationStatusResult. Helper methods exposed by this object can be used to map the result to relevant outcomes based on business requirements. The table below describes all helper methods that can be invoked on this result object with a description of the return value for each of these methods.
| method | return type | Description | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| getApplicationStatusOutputExceptionIfNull() | GetApplicationStatusOutput (package path: dk.ekspresbank.feedbackservice._2014._01) | Returns a reference to the actual result object returned by the FeedbackService.getApplicationStatus call. This object can be used in case the helper methods available in ApplicationStatusResult object are not enough to meet the requirements. This method throws a RuntimeException if the GetApplicationStatusOutput object returned by FeedbackService call is null. All the helper methods describes in the next rows of this table are actually calling the corresponding getter methods on this GetApplicationStatusOutput object. Some times the helper methods perform some internal conversions/formatting for easy use. For ex:
| ||||||||||||||||||||||||||||||
| isStatusResultOk() | boolean | true: The currentStatus and latestEvent value in the response can be trusted false: Something went wrong, so the response values cannot be trusted | ||||||||||||||||||||||||||||||
| isHasGoAhead() | boolean | true/false Returns the value of hasGoAhead property | ||||||||||||||||||||||||||||||
| isHasShipped() | boolean | true/false Returns the value of hasShipped property | ||||||||||||||||||||||||||||||
| getRequestId() | String | Returns the requestId returned by Ekspresbank in getApplicationStatus response | ||||||||||||||||||||||||||||||
| getApplicationGuid() | String | Returns the applicationGUID returned by Ekspresbank in getApplicationStatus response. This will be same as the applicationGUID supplied in the input | ||||||||||||||||||||||||||||||
| getApplicationId() | Integer | Returns the applicationId returned by Ekspresbank in getApplicationStatus response. | ||||||||||||||||||||||||||||||
| getCurrentStatus() | Integer | Gets the Current status of the application. Below is a list of all possible values for CurrentStatus:
| ||||||||||||||||||||||||||||||
| getCurrentStatusDate() | Date | Date on which the application reached current status | ||||||||||||||||||||||||||||||
| getLatestEvent() | Integer | Gets the value of the latestEvent. Below is a list of all possible values for latestEvent property:
| ||||||||||||||||||||||||||||||
| getLatestEventDate() | Date | Returns the date of latestEvent | ||||||||||||||||||||||||||||||
| getContractUrl() | JAXBElement<String> | Gets the value of the contractUrl |
If anything unexpected happens, an exception is thrown. It is possible to map an Exception to an outcome on the Action GUI on the workflow builder.
...
FQCN of the action class: com.CDRator.billing.financial.ekspresbank.action.CancelAction
This action is used to send a Cancel signal to Ekspresbank to cancel the sale. Cancel can be initiated via this action only if the Ship Signal for this application is not yet sent to Ekspres Bank.
Input Arguments
This action takes in three arguments:
...
FQCN of the action class: com.CDRator.billing.financial.ekspresbank.action.CaptureAction
This action is used to send a Ship signal to Ekspresbank, and the payout process is initiated.
Input Arguments
This action takes in three arguments:
...
Version | Released | Changes |
|---|---|---|
| 2.0 | xx-10-2016 | The Ekspres Bank Integration project is updated to integrate to New API of Ekspres Bank. The Ekspres Bank has moved to a new API, and this is different from old API that there are changes in input parameters and output parameters and request response types. So we have developed new Workflow Actions. The old Actions/Components are no longer available. |
1.1 | 12-09-2013 15:51:13 | Fixed an issue where request response was stored in soap_monitoring. It will now store it in soap_client_log |
1.0 | First stable release |
...