Skip to content

Commit c19b5a9

Browse files
committed
Added services folder
1 parent fa4c732 commit c19b5a9

File tree

3 files changed

+6
-11
lines changed

3 files changed

+6
-11
lines changed
File renamed without changes.
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ In CAP Node.js support for flows is built-in and available out of the box. For C
3232

3333
The following example is taken from the [@capire/xtravels](https://github.com/capire/xtravels) sample application, in which we want to model a status flow for travel requests as depicted below:
3434

35-
![A flow diagram showing three status states connected by arrows. The leftmost oval contains the word Open. An arrow labeled accept points from Open to an oval containing Accepted at the top right. Another arrow labeled reject points from Open to an oval containing Canceled at the bottom right.](assets/flows/xtravels-flow-simple.svg)
35+
![A flow diagram showing three status states connected by arrows. The leftmost oval contains the word Open. An arrow labeled accept points from Open to an oval containing Accepted at the top right. Another arrow labeled reject points from Open to an oval containing Canceled at the bottom right.](../assets/flows/xtravels-flow-simple.svg)
3636

3737
We can easily model this flow in CDS as follows:
3838

@@ -136,7 +136,7 @@ Use the target state `$flow.previous` to return a previous state from a current
136136

137137
The following example introduces a `Blocked` state with two possible previous states, `Open` and `InReview`, and an `unblock` action that restores the previous state.
138138

139-
![The graphic is explained in the accompanying text.](assets/flows/xtravels-flow-previous.svg)
139+
![The graphic is explained in the accompanying text.](../assets/flows/xtravels-flow-previous.svg)
140140

141141
::: code-group
142142
```cds [srv/flow-previous.cds]

menu.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -22,21 +22,16 @@
2222

2323
## [Providing Services](guides/providing-services)
2424

25-
### [Intro: Core Concepts](guides/providing-services#introduction)
25+
### [Core Concepts](guides/providing-services#introduction)
2626
### [Service Definitions](guides/providing-services#service-definitions)
27-
### [Generic Providers](guides/providing-services#generic-providers)
28-
### [Input Validation](guides/providing-services#input-validation)
27+
### [Served out-of-the-box](guides/providing-services#generic-providers)
28+
### [Constraints](guides/services/constraints)
29+
### [Status Flows](guides/services/status-flows)
2930
### [Custom Logic](guides/providing-services#custom-logic)
3031
### [Actions & Functions](guides/providing-services#actions-functions)
3132
### [Serving Media Data](guides/providing-services#serving-media-data)
3233
### [Best Practices](guides/providing-services#best-practices)
3334

34-
35-
## [Constraints](guides/constraints)
36-
37-
## [Status Flows](guides/status-flows)
38-
39-
4035
## [Consuming Services](guides/using-services)
4136

4237
### [Introduction](guides/using-services#introduction)

0 commit comments

Comments
 (0)