Document Logs
Change log:
...
eventDate: Time of cancellation of the Application. Ekspres Bank expects a non-null value for eventDate. Hence, the action will use current date if eventDate supplied in the input is null.
brandId: Used to read the Branded parameters. The URL of the webservice at Ekspres bank and some additional required arguments are specified in the parameter tree. So brand Id is used on a branded environment.
...
eventDate: Time of physical shipment of the goodsbrandId: Used to read the Branded parameters. The URL of the webservice at Ekspres bank and some Ekspres Bank expects a non-null value for eventDate. Hence, the action will use current date if eventDate supplied in the input is null.
brandId: Used to read the Branded parameters. The URL of the webservice at Ekspres bank and some additional required arguments are specified in the parameter tree. So brand Id is used on a branded environment.
...
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.
4 - Logging
...
3.2 - Exceptions thrown by Workflow Actions
Following exceptions can be thrown by Ekspres Bank workflow actions:
- com.CDRator.billing.financial.ekspresbank.action.result.exception.ResultNullException: Extends from java.lang.Exception. This exception is thrown when null response is received from Ekspres Bank.
- com.CDRator.billing.financial.ekspresbank.action.result.exception.InvalidApplicationGUIDException: Extends from java.lang.Exception. If the ApplicationGUID supplied in the input parameters is null/empty, then the action throws this exception. ApplicationGUID is mandatory to invoke Status poll/cancel/capture functions of Ekspres Bank API.
- java.lang.Exception: Sysexceptions due to missing parameter tree entries or other checked exceptions are grouped here
- java.lang.RuntimeException: Any runtime exception
4 - Logging
The project uses the rator-soap-monitoring to log request and response to the SOAP_CLIENT_LOG table. In order for this logging to work, two parameters must be added to the parameter tree. See section Configuration.
...
Some of the Parameters are mandatory and some are optional. The mandatory parameters must always be created and should contain proper values. The Optional parameters can be omitted. If an optional parameter is not present, a default value (if available) is used instead. Default values (if any) for optional parameters are mentioned in the table. If the default value does not meet the requirements, then the corresponding optional parameter can be created and set to desired value as per business requirements.
Parameters Used for communicating with Ekspres bank :
...
Value of eventRecordPassKey input parameter used in FeedbackService.putEventRecord method calls. This is supplied by Ekspres Bank
...
requirements.
Parameters Used for communicating with Ekspres bank :
| Parameter Path/Type | Mandatory? | Value | Description | ||
|---|---|---|---|---|---|
| FINANCIAL.EKSPRESBANK.PARTNER_ID | |||||
| Number | YES | To be provided by Ekspres Bank | A unique Id supplied by Ekspresbank to identify the Partner. | ||
| FINANCIAL.EKSPRESBANK.EVENT_RECORD_PASS_KEY | |||||
| String | YES | To be provided by Ekspres Bank | Value of eventRecordPassKey input parameter used in FeedbackService.putEventRecord method calls. This is supplied by Ekspres Bank | ||
| FINANCIAL.EKSPRESBANK.CANCEL_SIGNAL_EVENT_TYPE | |||||
Number | NO | Default value: 401 | Value of eventType input parameter passed to the FeedbackService.putEventRecord method for canceling an Application. This parameter is created for flexibility that if this value changes in future, then it can be configured via the parameter. Note: Cancel can be initiated via the FeedbackService.putEventRecord call, ONLY if the order has NOT yet been shipped i.e. ship signal is not yet sent. | ||
| FINANCIAL.EKSPRESBANK.SHIP_SIGNAL_EVENT_TYPE | |||||
| Number | NO | Default value: 401282
| Value of eventType input parameter passed to the FeedbackService.putEventRecord method for canceling an Application.sending 'Order Shipped' (i.e. Capture) signal to Ekspres Bank This parameter is created for flexibility that if this value changes in future, then it can be configured via the parameter.Note: Cancel can be initiated via the FeedbackService.putEventRecord call, ONLY if the order has NOT yet been shipped i.e. ship signal is not yet sentvia the parameter. | ||
| String | YES | FINANCIAL.EKSPRESBANK.SHIPFEEDBACK_SIGNAL_EVENT_TYPE | |||
| Number | NO | Default value: 282
| Value of eventType input parameter passed to the FeedbackService.putEventRecord method for sending 'Order Shipped' (i.e. Capture) signal to Ekspres Bank This parameter is created for flexibility that if this value changes in future, then it can be configured via the parameter. | ||
| FINANCIAL.EKSPRESBANK.FEEDBACK_SERVICE_ENDPOINT | |||||
| SERVICE_ENDPOINT | |||||
| String | YES | URL to access the Ekspres Bank webservice FeedbackService The URL to access FeedbackService Test service(Note: This is the value to be the configured in this parameter entry on TEST environment): https://preprodservices.ekspresbanktest.com/feedback/FeedbackService.svc The URL to access FeedbackService Production service(Note: This is the value to be the configured in this parameter entry on PRODUCTION environment): https://services.ekspresbank.com/feedback/FeedbackService.svc
| Endpoint URL to connect to the Ekspres Bank FeedbackService. In case the WSDLs need to be accessed, here are the links (do not use these URLs in this parameter tree entry value) For Test FeedbackService WSDL: https://preprodservices.ekspresbanktest.com/feedback/FeedbackService.svcwsdl For Production FeedbackService WSDL path:https://preprodservicesservices.ekspresbanktestekspresbank.com/feedback/FeedbackService.wsdl | Endpoint URL to connect to the Ekspres Bank FeedbackService | |
Parameters Required for Logging SOAP request, response XMLs to the SOAP_CLIENT_LOG
...
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 |
...