Skip to content

Commit f61c868

Browse files
authored
Merge pull request #4 from s1seven/omitjson
Omit JSON II
2 parents 78515bb + adc51ac commit f61c868

File tree

2 files changed

+18
-26
lines changed

2 files changed

+18
-26
lines changed

content/setup/README.md

+18-26
Original file line numberDiff line numberDiff line change
@@ -4,31 +4,19 @@
44

55
<!-- code_chunk_output -->
66

7-
- [Table of Content](#table-of-content)
8-
- [SAP System Setup](#sap-system-setup)
9-
- [System Setup with /UBC/S17\_SETUP](#system-setup-with-ubcs17_setup)
10-
- [Proxy Setup with /UBC/S17\_SETUP\_PROXY](#proxy-setup-with-ubcs17_setup_proxy)
11-
- [Certificate Configuration/Implementation instructions](#certificate-configurationimplementation-instructions)
12-
- [Outbound case - issuing/notarizing Certificates](#outbound-case---issuingnotarizing-certificates)
13-
- [Print program/freestyle integration](#print-programfreestyle-integration)
14-
- [IDOC integration](#idoc-integration)
15-
- [Inbound case - receiving Certificates](#inbound-case---receiving-certificates)
16-
- [Connectivity](#connectivity)
17-
- [Direct communication with S1SEVEN](#direct-communication-with-s1seven)
18-
- [SAP to S1SEVEN API for outbound messages](#sap-to-s1seven-api-for-outbound-messages)
19-
- [S1SEVEN to SAP for inbound messages](#s1seven-to-sap-for-inbound-messages)
20-
- [Messages via REST webservice calls](#messages-via-rest-webservice-calls)
21-
- [Messages via MQTT over Websocket](#messages-via-mqtt-over-websocket)
22-
- [Indirect Communication with S1SEVEN via Middleware](#indirect-communication-with-s1seven-via-middleware)
23-
- [SAP Integration Suite/Cloud Platform Integration (CPI)](#sap-integration-suitecloud-platform-integration-cpi)
24-
- [Integration Package/iFlow](#integration-packageiflow)
25-
- [Open Connector](#open-connector)
26-
- [SAP to S1SEVEN API for outbound messages](#sap-to-s1seven-api-for-outbound-messages-1)
27-
- [S1SEVEN to SAP for inbound messages](#s1seven-to-sap-for-inbound-messages-1)
28-
- [Monitoring](#monitoring)
29-
- [Authorization](#authorization)
30-
- [Data Archiving](#data-archiving)
31-
- [Compatibility](#compatibility)
7+
1. [SAP System Setup](#sap-system-setup)
8+
1. [System Setup with /UBC/S17_SETUP](#system-setup-with-ubcs17_setup)
9+
2. [Proxy Setup with /UBC/S17_SETUP_PROXY](#proxy-setup-with-ubcs17_setup_proxy)
10+
2. [Certificate Configuration/Implementation instructions](#certificate-configurationimplementation-instructions)
11+
1. [Outbound case - issuing/notarizing Certificates](#outbound-case---issuingnotarizing-certificates)
12+
2. [Inbound case - receiving Certificates](#inbound-case---receiving-certificates)
13+
3. [Connectivity](#connectivity)
14+
1. [Direct communication with S1SEVEN](#direct-communication-with-s1seven)
15+
2. [Indirect Communication with S1SEVEN via Middleware](#indirect-communication-with-s1seven-via-middleware)
16+
4. [Monitoring](#monitoring)
17+
5. [Authorization](#authorization)
18+
6. [Data Archiving](#data-archiving)
19+
7. [Compatibility](#compatibility)
3220

3321
<!-- /code_chunk_output -->
3422

@@ -158,7 +146,11 @@ S1SEVEN DMP allows to configure more than one type of certificate in the system:
158146
1. Construct a new Mapper implementation in method `create_mapper_certificate`, which inherits from the matching super class, see below. It is intended to map all the fields based on your input (IDOC/print program/freestyle) to a certificate structure.
159147
1. The method `process_notarized_certificate` is called after the successful notarization. It is intended to be used for follow-up actions like "storing PDF at SAP object level".
160148

161-
> JSON data is transmitted besides the PDF document by default. This behavior can be changed and controlled for a specific customer, see example implementations mentioned below and method `/ubc/if_s17_bo~should_omit_json( )`.
149+
**Omit JSON**
150+
JSON data is transmitted besides the PDF document by default. This behavior can be changed and controlled for a specific customer, see example implementations mentioned below and method `/ubc/if_s17_bo~should_omit_json( )`. If you want to omit the JSON for a specific customer, redefine the mentionend method. Our best practice is to read the flag from a predefined Customizing table which needs to be filled, see the example implementations.
151+
For maintaining the Attribute for a specific Customer, please have a look at `/UBC/CUSTOMIZING` -> "S1SEVEN" -> "Customer Attributes".
152+
![Customizing of Customers - Omit JSON](./assets/figure_49.png)
153+
The customizing should be pretty straightforward. Please note that empty cells for **Company id** or **Customer** can be seen as a "wildcard".
162154

163155
#### Print program/freestyle integration
164156

content/setup/assets/figure_49.png

6.02 KB
Loading

0 commit comments

Comments
 (0)