This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
nocode:transactions [2019/08/12 13:58] 740803864 [Response processing] |
nocode:transactions [2020/03/29 11:34] 77.75.78.163 ↷ Links adapted because of a move operation |
||
---|---|---|---|
Line 6: | Line 6: | ||
See chapters below for details. | See chapters below for details. | ||
- | ===== Set up ===== | + | ===== Setup ===== |
- | At first, transaction must be prepared and sent to ADUCID Binder. ADUCID Binder accepts transaction HTTP requests at ''/ | + | At first, transaction must be prepared and sent to ADUCID Binder. ADUCID Binder accepts transaction HTTP requests at ''/ |
^ Name ^ Values ^ Mandatory ^ Description ^ | ^ Name ^ Values ^ Mandatory ^ Description ^ | ||
| transactionId | String | Yes | transaction unique identifier | | | transactionId | String | Yes | transaction unique identifier | | ||
Line 16: | Line 16: | ||
| udi | String | No | if defined, security attack check is realized | | | udi | String | No | if defined, security attack check is realized | | ||
| peigId | String | No | if defined, mobile push notification is realized | | | peigId | String | No | if defined, mobile push notification is realized | | ||
- | **It is neccessary to add '' | + | **It is neccessary to add '' |
We must also remember to provide generated transaction identifier to web view, e.g. Ajax JSON response or JSP expression language. | We must also remember to provide generated transaction identifier to web view, e.g. Ajax JSON response or JSP expression language. | ||
===== Transaction itself ===== | ===== Transaction itself ===== | ||
- | When transaction data are successfully uploaded, we can start transaction itself. It can be done with use of [[web-integration: | + | When transaction data are successfully uploaded, we can start transaction itself. It can be done with use of [[web-integration: |
<code javascript> | <code javascript> | ||
Line 32: | Line 32: | ||
===== Response processing ===== | ===== Response processing ===== | ||
- | User is now redirected to '' | + | User is now redirected to '' |
+ | |||
+ | ==== Positive response ==== | ||
+ | When transaction was successful | ||
<code javascript> | <code javascript> | ||
Line 42: | Line 45: | ||
</ | </ | ||
- | Transaction can be also unsuccessful. There are two types of failures - failure directly on AIM and second level failure. Failure on AIM can be: | + | ==== Negative response ==== |
+ | Transaction can be also unsuccessful | ||
<code javascript> | <code javascript> | ||
Line 59: | Line 63: | ||
</ | </ | ||
- | In case of AIM failure, values '' | + | In case of AIM failure, values '' |
+ | |||
+ | Secondary level failure can look like: | ||
+ | |||
+ | <code javascript> | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }, | ||
+ | " | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In this case, value '' |