You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+9-14Lines changed: 9 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,29 +36,26 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
36
36
- Fixed handling of unmanaged composition of many
37
37
- Proper casing of the operation enum type
38
38
39
-
40
39
### Changed
41
40
42
41
- Added warning and mitigation for multi-tenant deployments with MTX
43
42
- Added a disclaimer of upcoming new version having a minimum requirement of CDS 8.6 for multitenancy fix
44
43
- Changed the default limit on non-HANA databases from 255 to 5000 characters for all String values
45
44
- Updated peer dependency from CDS7 to CDS8
46
45
47
-
48
46
## Version 1.0.7 - 20.08.24
49
47
50
48
### Added
51
49
52
-
- A global switch to preserve change logs for deleted data
53
-
- For hierarchical entities, a method to determine their structure and a flag to indicate whether it is a root entity was introduced. For child entities, information about the parent is recorded.
54
-
50
+
- A global switch to preserve change logs for deleted data
51
+
- For hierarchical entities, a method to determine their structure and a flag to indicate whether it is a root entity was introduced. For child entities, information about the parent is recorded.
55
52
56
53
### Fixed
57
54
58
55
- CDS 8 does not support queries for draft-enabled entities on the application service anymore. This was causing: SqliteError: NOT NULL constraint failed: (...).DraftAdministrativeData_DraftUUID
59
56
- CDS 8 deprecated cds.transaction, causing change logs of nested documents to be wrong, replaced with req.event
60
57
- CDS 8 rejects all direct CRUD requests for auto-exposed Compositions in non-draft cases. This was affecting test cases, since the ChangeView falls into this category
61
-
- req._params and req.context are not official APIs and stopped working with CDS 8, replaced with official APIs
58
+
- req.\_params and req.context are not official APIs and stopped working with CDS 8, replaced with official APIs
62
59
- When running test cases in CDS 8, some requests failed with a status code of 404
63
60
- ServiceEntity is not captured in the ChangeLog table in some cases
64
61
- When modeling an inline entity, a non-existent association and parent ID was recorded
@@ -70,22 +67,21 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
70
67
- Data marked as personal data using data privacy annotations won't get change-tracked anymore to satisfy product standards
71
68
- Restructured Documentation
72
69
73
-
74
70
## Version 1.0.6 - 29.04.24
75
71
76
72
### Fixed
77
73
78
-
- Storage of wrong ObjectID in some special scenarios
79
-
- Missing localization of managed fields
80
-
- Views without keys won't get the association and UI facet pushed anymore
74
+
- Storage of wrong ObjectID in some special scenarios
75
+
- Missing localization of managed fields
76
+
- Views without keys won't get the association and UI facet pushed anymore
81
77
82
78
### Added
83
79
84
-
- A method to disable automatic generation of the UI Facet
80
+
- A method to disable automatic generation of the UI Facet
85
81
86
82
### Changed
87
83
88
-
- Improved documentation of the @changelog Annotation
84
+
- Improved documentation of the @changelog Annotation
89
85
90
86
## Version 1.0.5 - 15.01.24
91
87
@@ -112,7 +108,7 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
112
108
113
109
### Added
114
110
115
-
- Added note about using `SAPUI5 v1.120.0` or later for proper lazy loading of the *Change History* table.
111
+
- Added note about using `SAPUI5 v1.120.0` or later for proper lazy loading of the _Change History_ table.
116
112
- In README, add warning about tracking personal data.
117
113
118
114
### Changed
@@ -141,4 +137,3 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,11 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be repor
10
10
11
11
We use GitHub to manage reviews of pull requests.
12
12
13
-
* If you are a new contributor, see: [Steps to Contribute](#steps-to-contribute)
13
+
- If you are a new contributor, see: [Steps to Contribute](#steps-to-contribute)
14
14
15
-
* Before implementing your change, create an issue that describes the problem you would like to solve or the code that should be enhanced. Please note that you are willing to work on that issue.
15
+
- Before implementing your change, create an issue that describes the problem you would like to solve or the code that should be enhanced. Please note that you are willing to work on that issue.
16
16
17
-
* The team will review the issue and decide whether it should be implemented as a pull request. In that case, they will assign the issue to you. If the team decides against picking up the issue, the team will post a comment with an explanation.
17
+
- The team will review the issue and decide whether it should be implemented as a pull request. In that case, they will assign the issue to you. If the team decides against picking up the issue, the team will post a comment with an explanation.
18
18
19
19
## Steps to Contribute
20
20
@@ -28,11 +28,11 @@ You are welcome to contribute code in order to fix a bug or to implement a new f
28
28
29
29
The following rule governs code contributions:
30
30
31
-
* Contributions must be licensed under the [Apache 2.0 License](./LICENSE)
32
-
* Due to legal reasons, contributors will be asked to accept a Developer Certificate of Origin (DCO) when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses [the standard DCO text of the Linux Foundation](https://developercertificate.org/).
31
+
- Contributions must be licensed under the [Apache 2.0 License](./LICENSE)
32
+
- Due to legal reasons, contributors will be asked to accept a Developer Certificate of Origin (DCO) when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses [the standard DCO text of the Linux Foundation](https://developercertificate.org/).
33
33
34
34
## Issues and Planning
35
35
36
-
* We use GitHub issues to track bugs and enhancement requests.
36
+
- We use GitHub issues to track bugs and enhancement requests.
37
37
38
-
* Please provide as much context as possible when you open an issue. The information you provide must be comprehensive enough to reproduce that issue for the assignee.
38
+
- Please provide as much context as possible when you open an issue. The information you provide must be comprehensive enough to reproduce that issue for the assignee.
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,8 @@ Usage of this plugin requires a valid subscription of the [SAP Print Service](ht
23
23
To use this plugin to print documents there are two main steps:
24
24
25
25
1. Add required annotations to your CDS model.
26
-
a. Entity
27
-
b. Action
26
+
a. Entity
27
+
b. Action
28
28
2. Configure print queues to select from available options. (Optional, but recommended)
29
29
30
30
### Annotations in CDS model
@@ -47,6 +47,7 @@ entity Incidents : cuid {
47
47
-`@print.fileName`: Annotates the field containing the name of the document
48
48
49
49
#### Annotation of actions
50
+
50
51
Sending a print request works via bound actions annotated with `@print`. The parameter of the action are used to define the print job details.
51
52
52
53
```cds
@@ -72,7 +73,7 @@ service IncidentService {
72
73
qnameID: String,
73
74
@print.numberOfCopies
74
75
@UI.ParameterDefaultValue : 1
75
-
copies: Integer
76
+
copies: Integer
76
77
);
77
78
};
78
79
}
@@ -82,7 +83,8 @@ service IncidentService {
82
83
-`@print.queue`: Annotates the parameter specifying the print queue. It is recommended to use a value help for this parameter to select from available print queues. See TOOD
83
84
-`@print.numberOfCopies`: Annotates the parameter specifying the number of copies to print
84
85
85
-
### Queues
86
+
### Queues
87
+
86
88
Every print request needs to specify a print queue it is send to. It is recommended to provide a value help for the print queue selection. To enbale this, define an entity as projection on the `Queues` entity provided by the print service. When this projection is in place, the plugin automatically provides the available print queues coming from the print service.
cds.error(`Print action ${action.name} is missing required annotations. Make sure @print.numberOfCopies, @print.queue are present in the action and @print.fileName and @print.fileContent are present in the entity.`);
`Print action ${action.name} is missing required annotations. Make sure @print.numberOfCopies, @print.queue are present in the action and @print.fileName and @print.fileContent are present in the entity.`,
0 commit comments