Skip to content
GitLab
Explore
Sign in
This project is archived. Its data is
read-only
.
Changes
Page history
contracting:customer decision added
authored
Dec 09, 2015
by
Sebastian Schlicht
Hide whitespace changes
Inline
Side-by-side
data-workflow.md
View page @
420902a9
...
@@ -5,7 +5,11 @@
...
@@ -5,7 +5,11 @@
Capitol provides a REST API that accepts JSON data to start the process.
Capitol provides a REST API that accepts JSON data to start the process.
2.
[
out] [contract data
](
bvis/contracting/contract-data
)
(
insurance
benefits may have been added)
2.
[
out] [contract data
](
bvis/contracting/contract-data
)
(
insurance
benefits may have been added)
BVIS provides a REST endpoint that accepts JSON data.
BVIS provides a REST endpoint that accepts JSON data.
3.
[]
**???**
3.
[in] customer decision
**TODO**
Capitol provides a REST endpoint that accepts JSON data.
*
contract id
*
signing flag (indicates if the customer accepted the contract)
*
insurance benefits (see
[
contract data
](
bvis/contracting/contract-data
)
) (indicates which insurance benefits the customer accepted, may be empty)
### Accident
### Accident
1.
[
in] [accident data
](
bvis/accident/accident-data
)
1.
[
in] [accident data
](
bvis/accident/accident-data
)
...
@@ -27,7 +31,7 @@
...
@@ -27,7 +31,7 @@
2.
[
out] contact BVIS if accident is a liability case [liability information
](
bvis/accident/liability-information
)
2.
[
out] contact BVIS if accident is a liability case [liability information
](
bvis/accident/liability-information
)
BVIS provides a REST endpoint that accepts JSON.
BVIS provides a REST endpoint that accepts JSON.
*
process id
*
transaction key
*
contract id
*
contract id
*
liability flag
*
liability flag
...
...
...
...