diff --git a/docs/developer/01. Onboarding/01. Invite/01. Summary.md b/docs/developer/01. Onboarding/01. Invite/01. Summary.md index af200f666..3213b857d 100644 --- a/docs/developer/01. Onboarding/01. Invite/01. Summary.md +++ b/docs/developer/01. Onboarding/01. Invite/01. Summary.md @@ -2,7 +2,7 @@
-image +image
Scenario: New Member gets an individual invite by the CX Organization or Operator diff --git a/docs/developer/01. Onboarding/01. Invite/03. Invite Company_Create Application.md b/docs/developer/01. Onboarding/01. Invite/03. Invite Company_Create Application.md index f41feadf3..00b786bae 100644 --- a/docs/developer/01. Onboarding/01. Invite/03. Invite Company_Create Application.md +++ b/docs/developer/01. Onboarding/01. Invite/03. Invite Company_Create Application.md @@ -4,7 +4,7 @@ The invitation is the starting point of a company onboarding. A user of the company is getting invited by the CX Admin and the invitation endpoint is triggering in the backend the creation of the identity relevant elements.

-image +image

diff --git a/docs/developer/01. Onboarding/02. Registration/01. Login.md b/docs/developer/01. Onboarding/02. Registration/01. Login.md index 33e6216a2..fb93fbd20 100644 --- a/docs/developer/01. Onboarding/02. Registration/01. Login.md +++ b/docs/developer/01. Onboarding/02. Registration/01. Login.md @@ -16,12 +16,12 @@ Pre-condition: The authorized organization onboarding party must have received a After receiving the CX invite email (incl. registration login URL and one-time-password), the user can directly start the login to the company registration.
-image +image
After selecting the company for login; the user can login via the email and password (first time; the one-time-password shared via email) -image +image
After the successful login; the user can directly start to proceed with the company registration form. @@ -38,7 +38,7 @@ Based on the fetched status; the frontend logic will decide how the user proceed 1. If the status is any status before "SUBMITTED" (< id "7"); the company registration form gets displayed; starting with the introduction screen. If company registration data have been previously added/saved already, the data will be displayed inside the registration form; otherwise an empty registration form will be displayed. 2. If the status is in status "SUBMITTED" (= id "7"); the information screen "application in validation" screen is getting displayed. - image + image 3. If the status is in status "APPROVED" (= id "8"); the user should get redirected to the portal "home" page diff --git a/docs/developer/01. Onboarding/02. Registration/02. Add Company Data.md b/docs/developer/01. Onboarding/02. Registration/02. Add Company Data.md index df582472c..c430a4732 100644 --- a/docs/developer/01. Onboarding/02. Registration/02. Add Company Data.md +++ b/docs/developer/01. Onboarding/02. Registration/02. Add Company Data.md @@ -19,7 +19,7 @@ Below you can find the sub-chapter overview for an easy navigation ## Functional View
-image +image
In step 1 of the registration application, the company administrator need to add the legal company details. 2 Options are available @@ -41,7 +41,7 @@ In step 1 of the registration application, the company administrator need to add Flow diagram for option a) and b)
-image +image

@@ -182,7 +182,7 @@ The unique identifier is a location based attribute; means, after the user enter initially when opening the registration form step 1 "company data"; the unique identifier section is not displayed. Only when entering the country code; the unique id section is getting displayed (see screen below) -image +image ```dif ! GET /api/registration/company/country/{alpha2Code}/uniqueidentifiers @@ -207,11 +207,11 @@ Response Body ###### Result on UI -image +image Translation of technical api response keys to human readable titles: - image + image
**NOTE** @@ -235,14 +235,14 @@ In case that multiple identifier are submitted, the user needs to be able to sel Below you can find an example of the implemented design for "multiple identifier"
-image +image

###### Implemented Pattern -image +image

diff --git a/docs/developer/01. Onboarding/02. Registration/03. Add Additional Users.md b/docs/developer/01. Onboarding/02. Registration/03. Add Additional Users.md index 02b37cdd1..b0065ff9a 100644 --- a/docs/developer/01. Onboarding/02. Registration/03. Add Additional Users.md +++ b/docs/developer/01. Onboarding/02. Registration/03. Add Additional Users.md @@ -5,7 +5,7 @@ ## Add Aditional Users
-image +image
As part of the registration and onboarding process a number of users will be needed to support diff --git a/docs/developer/01. Onboarding/02. Registration/04. Company Role & Consent.md b/docs/developer/01. Onboarding/02. Registration/04. Company Role & Consent.md index 6e3e29e02..570f904b1 100644 --- a/docs/developer/01. Onboarding/02. Registration/04. Company Role & Consent.md +++ b/docs/developer/01. Onboarding/02. Registration/04. Company Role & Consent.md @@ -5,7 +5,7 @@ ## Select company role & sign terms and conditions
-image +image
For the company role selection the Company Admin can select the company role within the network
diff --git a/docs/developer/01. Onboarding/02. Registration/05. Document Upload.md b/docs/developer/01. Onboarding/02. Registration/05. Document Upload.md index 9ae51b363..48e9101a3 100644 --- a/docs/developer/01. Onboarding/02. Registration/05. Document Upload.md +++ b/docs/developer/01. Onboarding/02. Registration/05. Document Upload.md @@ -5,7 +5,7 @@ ## Upload registration relevant documents
-image +image
In Step 4, the users are asked to upload the company identification.
diff --git a/docs/developer/01. Onboarding/02. Registration/07. Error Scenarios.md b/docs/developer/01. Onboarding/02. Registration/07. Error Scenarios.md index 8a3d58c85..1ff03e720 100644 --- a/docs/developer/01. Onboarding/02. Registration/07. Error Scenarios.md +++ b/docs/developer/01. Onboarding/02. Registration/07. Error Scenarios.md @@ -12,7 +12,7 @@ In case the registration login/initial registration form load endpoints run on a Example:
-image +image

@@ -25,7 +25,7 @@ If the login can not get confirmed, the login will display the following error: Example:
-image +image

@@ -39,17 +39,17 @@ Error scenarios: - error incorrect added country code - Snackbar - image + image - error incorrect bpn added - input field error - image + image - error bpn not found - input field error - image + image - error on saving company data @@ -75,7 +75,7 @@ Error scenarios: - Agreement pre-saved data load unsuccessful - Agreement saved unsuccessfully - Snackbar - image + image

@@ -92,7 +92,7 @@ Error scenarios: - Documents upload unsuccessful - Dropzone error - image + image

diff --git a/docs/developer/01. Onboarding/03. Registration Approval/02. View Company Application(s).md b/docs/developer/01. Onboarding/03. Registration Approval/02. View Company Application(s).md index dc9d6b8db..49e72d8e6 100644 --- a/docs/developer/01. Onboarding/03. Registration Approval/02. View Company Application(s).md +++ b/docs/developer/01. Onboarding/03. Registration Approval/02. View Company Application(s).md @@ -85,7 +85,7 @@ Endpoints supports pagination and search via companyName ## 2 Get Application Details
-image +image

Additionally to the endpoint of #1 where application key data are included, the GET application details endpoint is used to provide additional details to the operator / application approval buddy. @@ -168,7 +168,7 @@ The API is downloading the document which is selected by the user.

-image +image


diff --git a/docs/developer/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md b/docs/developer/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md index 374447808..6c2587c9c 100644 --- a/docs/developer/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md +++ b/docs/developer/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md @@ -6,12 +6,12 @@ Acting user: CX Admin (Operator)

-image +image By clicking on one of the process steps, the overlay wth process step details gets displayed. Depending on the status, the user can execute a number of action / next steps. In general 3 action states are possible and defined below -image +image

@@ -49,31 +49,31 @@ IMPORTANT: the "retriggerable" attribute is relevant / important for the FE busi ##### #1 Registration Validation
-image +image
##### #2 BPN Creation
-image +image
##### #3 Managed Identity Wallet
-image +image
##### #4 Clearinghouse
-image +image
##### #5 Self Description LP
-image +image

@@ -87,7 +87,7 @@ The list below shows an overview of all application approval steps:

-image +image

@@ -134,7 +134,7 @@ The endpoint can only get triggered/executed if the application is in the status ##### Scenario: Decline
-image +image
The endpoint "decline" sets the "Registration_Verification" checklist item to "FAILED" incl. a time stamp, as well as the decline message added by the operator. @@ -331,7 +331,7 @@ Standard validations apply:

-image +image

@@ -384,7 +384,7 @@ The "Clearinghouse Check" is getting automatically triggered when the following - application is in status "submitted"
-image +image
The interface is an asynchronous interface - due to this the application checklist item associates with two process steps; the interface is explained below in two steps @@ -594,7 +594,7 @@ With the execution of the application activation, the system will:
The bpn can get manually added (as a workaround) if the registration company request doesn't have a business partner number added and the registration request is in the status "submitted".
-image +image
BPNs can only get added by CX Admins. As mentioned above, the implementation is a workaround only and will get replaced by the actual bpn connection as soon as the reference implementation is available. diff --git a/docs/developer/01. Onboarding/03. Registration Approval/04. Decline Application.md b/docs/developer/01. Onboarding/03. Registration Approval/04. Decline Application.md index bb7b25899..12d639c89 100644 --- a/docs/developer/01. Onboarding/03. Registration Approval/04. Decline Application.md +++ b/docs/developer/01. Onboarding/03. Registration Approval/04. Decline Application.md @@ -4,7 +4,7 @@ While the company application is processing the application validations; the adm To decline the application the "Cancel Application" Button is enabled for all applications which did not reach the "CONFIRMED" / "DECLINED" status so far.
-image +image
##### API Implementation diff --git a/docs/developer/01. Onboarding/03. Registration Approval/index.md b/docs/developer/01. Onboarding/03. Registration Approval/index.md index d096cb548..6f823779a 100644 --- a/docs/developer/01. Onboarding/03. Registration Approval/index.md +++ b/docs/developer/01. Onboarding/03. Registration Approval/index.md @@ -8,14 +8,14 @@ Acting user: CX Admin (Operator) The board supports filter, search and the actual approval / validation function of new company registration requests.

-image +image

## Functional Details -image +image

@@ -32,7 +32,7 @@ With using the application details button, application details such as - details to the approval flow status
-image +image

diff --git a/docs/developer/02. Technical Integration/01. Connector Registration/02. View Connector.md b/docs/developer/02. Technical Integration/01. Connector Registration/02. View Connector.md index 809d59ad7..73e3a4735 100644 --- a/docs/developer/02. Technical Integration/01. Connector Registration/02. View Connector.md +++ b/docs/developer/02. Technical Integration/01. Connector Registration/02. View Connector.md @@ -18,7 +18,7 @@ Status uses the chipcard instead of the status icon. API response data mapping explained below: -image +image
@@ -26,7 +26,7 @@ Status uses the chipcard instead of the status icon. API response data mapping e MUI Element/Icon used to display status based on the API response: -image +image In the scenario where the documentId is NULL; tooltip is implemented with an additional information about the self-description status. @@ -36,7 +36,7 @@ In the scenario where the documentId is NULL; tooltip is implemented with an add Host displayed based on the API response: - image + image

diff --git a/docs/developer/02. Technical Integration/01. Connector Registration/05. Self Description.md b/docs/developer/02. Technical Integration/01. Connector Registration/05. Self Description.md index 70b46117e..b2fb0ed84 100644 --- a/docs/developer/02. Technical Integration/01. Connector Registration/05. Self Description.md +++ b/docs/developer/02. Technical Integration/01. Connector Registration/05. Self Description.md @@ -15,7 +15,7 @@ In case the self-description interface failed; the connector registration is in ### Implementation Details

-image +image


diff --git a/docs/developer/02. Technical Integration/01. Connector Registration/06. Delete Connector.md b/docs/developer/02. Technical Integration/01. Connector Registration/06. Delete Connector.md index 0d29229c1..ca538ded3 100644 --- a/docs/developer/02. Technical Integration/01. Connector Registration/06. Delete Connector.md +++ b/docs/developer/02. Technical Integration/01. Connector Registration/06. Delete Connector.md @@ -5,7 +5,7 @@ Delete own connector. The deletion will disable the discovery service for the co

-image +image


diff --git a/docs/developer/03. User Management/01. User Account/03. Create new user account (single) - UPDATE NEEDED.md b/docs/developer/03. User Management/01. User Account/03. Create new user account (single) - UPDATE NEEDED.md index a86210566..dce64ae58 100644 --- a/docs/developer/03. User Management/01. User Account/03. Create new user account (single) - UPDATE NEEDED.md +++ b/docs/developer/03. User Management/01. User Account/03. Create new user account (single) - UPDATE NEEDED.md @@ -3,13 +3,13 @@ User with the respective user management rights can access the user management via the top right user navigation. As soon as the user management is displayed, the user can direct via the button "Identity User Management" or scroll down the page to get to the Identity User Management section where new user accounts can get created. -Select the "Add User" Button image to trigger the new user account creation dialog. +Select the "Add User" Button image to trigger the new user account creation dialog. Inside the dialog, add the users first name, last name and email. Additionally to the user information, a network role need to get selected. Based on the network role, the user will be able to have a certain permissions inside the portal.

-image +image
diff --git a/docs/developer/03. User Management/02. Edit User Account/01. Summary.md b/docs/developer/03. User Management/02. Edit User Account/01. Summary.md index 556031098..8be4f9026 100644 --- a/docs/developer/03. User Management/02. Edit User Account/01. Summary.md +++ b/docs/developer/03. User Management/02. Edit User Account/01. Summary.md @@ -9,7 +9,7 @@ The "User Account Details" function is a detailed view of one user, which the co
-image +image # My CX Account @@ -22,7 +22,7 @@ The "My User Account Details" function is a detailed view of your own user accou
-image +image ## NOTICE diff --git a/docs/developer/03. User Management/02. Edit User Account/02. Password Reset.md b/docs/developer/03. User Management/02. Edit User Account/02. Password Reset.md index bfe8f2b07..e77e86aeb 100644 --- a/docs/developer/03. User Management/02. Edit User Account/02. Password Reset.md +++ b/docs/developer/03. User Management/02. Edit User Account/02. Password Reset.md @@ -5,7 +5,7 @@ The picture below includes the service details

-image +image ### Error message handling for password reset diff --git a/docs/developer/03. User Management/02. Edit User Account/03. User Permissions.md b/docs/developer/03. User Management/02. Edit User Account/03. User Permissions.md index 66fdd7559..b0aa80996 100644 --- a/docs/developer/03. User Management/02. Edit User Account/03. User Permissions.md +++ b/docs/developer/03. User Management/02. Edit User Account/03. User Permissions.md @@ -18,7 +18,7 @@ Assigned users portal role are visible, additionally, with the necessary rights,

-image +image


@@ -74,7 +74,7 @@ Using the data of endpoint #1 and the data from the endpoint "Fetch Portal roles

-image +image


@@ -131,7 +131,7 @@ To change user assigned app roles, open the "User Management" -> "App Access Man

-image +image


@@ -259,7 +259,7 @@ Select/Unselect the respective roles for the user and click confirm to submit th

-image +image


diff --git a/docs/developer/03. User Management/02. Edit User Account/04. Manage user assigned BPN.md b/docs/developer/03. User Management/02. Edit User Account/04. Manage user assigned BPN.md index d4d90aee2..74ca54646 100644 --- a/docs/developer/03. User Management/02. Edit User Account/04. Manage user assigned BPN.md +++ b/docs/developer/03. User Management/02. Edit User Account/04. Manage user assigned BPN.md @@ -2,7 +2,7 @@

-image +image

@@ -37,7 +37,7 @@

-image +image

diff --git a/docs/developer/03. User Management/02. Edit User Account/06. Delete User.md b/docs/developer/03. User Management/02. Edit User Account/06. Delete User.md index 239651e38..6ec0fe4ed 100644 --- a/docs/developer/03. User Management/02. Edit User Account/06. Delete User.md +++ b/docs/developer/03. User Management/02. Edit User Account/06. Delete User.md @@ -17,7 +17,7 @@ More details to the audit logging can get found here: [Audit Log Details](/docs/

-image +image

@@ -25,7 +25,7 @@ More details to the audit logging can get found here: [Audit Log Details](/docs/

-image +image

@@ -33,7 +33,7 @@ More details to the audit logging can get found here: [Audit Log Details](/docs/

-image +image

diff --git a/docs/developer/03. User Management/03. Technical User/03. Create Technical User.md b/docs/developer/03. User Management/03. Technical User/03. Create Technical User.md index c291e36b8..41ba36046 100644 --- a/docs/developer/03. User Management/03. Technical User/03. Create Technical User.md +++ b/docs/developer/03. User Management/03. Technical User/03. Create Technical User.md @@ -4,7 +4,7 @@ User with the respective user management rights can access the user management v As soon as the user management is displayed, a button "Technical User Management" shows up to switch from real users to technical users.
-image +image

@@ -23,7 +23,7 @@ On the FE side, for role assignment, only the composite roles will be visible fo Data flow details are drawn below
-image +image
```diff diff --git a/docs/developer/03. User Management/03. Technical User/04. Delete Technical User.md b/docs/developer/03. User Management/03. Technical User/04. Delete Technical User.md index 4fa198938..df9262163 100644 --- a/docs/developer/03. User Management/03. Technical User/04. Delete Technical User.md +++ b/docs/developer/03. User Management/03. Technical User/04. Delete Technical User.md @@ -3,7 +3,7 @@ Technical users created under the same company id can get deleted by user administrators. To delete an user, just open up the user details and click the "delete" button. -image +image

diff --git a/docs/developer/03. User Management/04. App Access Management/02. Assign App Role Page Overview.md b/docs/developer/03. User Management/04. App Access Management/02. Assign App Role Page Overview.md index 7da53e9a0..1a2a19fce 100644 --- a/docs/developer/03. User Management/04. App Access Management/02. Assign App Role Page Overview.md +++ b/docs/developer/03. User Management/04. App Access Management/02. Assign App Role Page Overview.md @@ -78,13 +78,13 @@ App Access Management user list as well as the app assign role user list is usin Example:
-image +image

In case the api is responding with an empty array, the UI will display following messages: -image +image

diff --git a/docs/developer/04. Apps/01. Marketplace/02. App Details.md b/docs/developer/04. Apps/01. Marketplace/02. App Details.md index 020dd9cad..7f190b843 100644 --- a/docs/developer/04. Apps/01. Marketplace/02. App Details.md +++ b/docs/developer/04. Apps/01. Marketplace/02. App Details.md @@ -94,7 +94,7 @@ Response Body Subscription Status Management: The "Subscribe" button shows different state and color depending on the company subscription status. Below the button states are shown: -image +image

@@ -103,13 +103,13 @@ The "Subscribe" button shows different state and color depending on the company Based in the API response the respective app privacy information will get displayed in the app details page -image +image
Expected result: -image +image

diff --git a/docs/developer/04. Apps/02. App Release Process/App Release Process.md b/docs/developer/04. Apps/02. App Release Process/App Release Process.md index 08eb7e90f..f82885b82 100644 --- a/docs/developer/04. Apps/02. App Release Process/App Release Process.md +++ b/docs/developer/04. Apps/02. App Release Process/App Release Process.md @@ -12,21 +12,21 @@ The app publishing process includes the submission of relevant app details, addi Option 1: Via the app management page -image +image

Option 2: Via the App Release Process -image +image

#### Step 1 - App Card Details -image +image In the Step 1 of the publishing process, the app card details are getting filled first @@ -91,7 +91,7 @@ Response Body Get use cases api endpoint is used to provide the user a dropdown function in which the provider can select which use cases the respective app serves -image +image ```diff ! GET /api/administration/staticdata/usecases @@ -277,7 +277,7 @@ Endpoint exception handling: #### Step 2 - App Page Details -image +image In the Step 2 of the publishing process, the app detail page is getting filled @@ -406,20 +406,20 @@ following translation for the privacy policy tags Design: -image +image
In case the privacy policies can not get loaded, the response will look like defined below: -image +image

#### Step 3 - Terms & Conditions / Consent -image +image Depending on the response of the endpoint #1 GET agreements, the user will be enabled to download related documents from the portal to read through the relevant agreement details. Expected formats are pdf, however other formats can get supported as well. @@ -451,13 +451,13 @@ Style If documentId inside response body is != NULL display the respective agreement as link - example: -image +image
If the documentId is NULL, the agreement is displayed without link (as currently implemented) - example: -image +image

@@ -508,14 +508,14 @@ Important: the deletion is not reversible - since the app is still under DRAFT,

-image +image

The Role Upload is a mandatory app release process step where the app provider can upload a csv file (template attached) to load user roles and description. With uploading the csv via the dropzone, a preview section will display the respective roles to be uploaded.

-image +image

With approving the upload with the button "Create App Roles" the roles are stored in the portal DB. Keycloak is untouched, since role creation in Keycloak will only be relevant if the app instance/client is getting created. @@ -561,7 +561,7 @@ Request Body #### Step 5 - Beta Test Runs -image +image
@@ -572,7 +572,7 @@ Only a preview for now #### Step 6 - Validate & Submit for Publishing check -image +image diff --git a/docs/developer/04. Apps/03. App Release Approval/01. App Approval Board Overview.md b/docs/developer/04. Apps/03. App Release Approval/01. App Approval Board Overview.md index 0943d2afb..cb7b3f7a8 100644 --- a/docs/developer/04. Apps/03. App Release Approval/01. App Approval Board Overview.md +++ b/docs/developer/04. Apps/03. App Release Approval/01. App Approval Board Overview.md @@ -5,7 +5,7 @@ The Page "App Approval Board" is accessible via the top main menu for CX Admins. The main focus / scope of the page is to enable the operator to manage apps releases for the CX marketplace.
-image +image

@@ -44,14 +44,14 @@ Response Body Details to the data mapping: -image +image
#### Sorting
-image +image
Sorting by "Newest First": {hostname}/api/apps/AppReleaseProcess/inReview?page=0&size=15&sorting=DateDesc @@ -62,7 +62,7 @@ Sorting by "App Title A-Z": {hostname}/api/apps/AppReleaseProcess/inReview?page= #### Views
-image +image
All: {hostname}/api/apps/AppReleaseProcess/inReview?page=0&size=15&sorting=DateDesc diff --git a/docs/developer/04. Apps/03. App Release Approval/02. App Details.md b/docs/developer/04. Apps/03. App Release Approval/02. App Details.md index b9580b457..e6a896b3e 100644 --- a/docs/developer/04. Apps/03. App Release Approval/02. App Details.md +++ b/docs/developer/04. Apps/03. App Release Approval/02. App Details.md @@ -6,7 +6,7 @@ To display the details the app data get displayed by clicking on the app card on

-image +image


@@ -107,13 +107,13 @@ App documents can get downloaded by clicking on the document name highlighted in Based in the API response the respective app privacy information will get displayed in the detail page -image +image
Expected result: -image +image

diff --git a/docs/developer/04. Apps/03. App Release Approval/03. Approve App Release.md b/docs/developer/04. Apps/03. App Release Approval/03. Approve App Release.md index 9947247ac..65b4bf465 100644 --- a/docs/developer/04. Apps/03. App Release Approval/03. Approve App Release.md +++ b/docs/developer/04. Apps/03. App Release Approval/03. Approve App Release.md @@ -4,7 +4,7 @@ With the app release approval, the app is getting activated for the app marketpl The approval is triggered by clicking on the approval icon inside the app card:
-image +image

diff --git a/docs/developer/04. Apps/03. App Release Approval/04. Decline App Release.md b/docs/developer/04. Apps/03. App Release Approval/04. Decline App Release.md index 1e732e7ee..6bf6585a4 100644 --- a/docs/developer/04. Apps/03. App Release Approval/04. Decline App Release.md +++ b/docs/developer/04. Apps/03. App Release Approval/04. Decline App Release.md @@ -4,7 +4,7 @@ The app release decline icon can get triggered by clicking on the decline icon i

-image +image


@@ -44,7 +44,7 @@ Details regarding the notification can get found in the notification service doc ##### Email Example -image +image ## NOTICE diff --git a/docs/developer/04. Apps/04. App Provider Management Board(s)/01. App Board.md b/docs/developer/04. Apps/04. App Provider Management Board(s)/01. App Board.md index 8605abc5b..6bae10f11 100644 --- a/docs/developer/04. Apps/04. App Provider Management Board(s)/01. App Board.md +++ b/docs/developer/04. Apps/04. App Provider Management Board(s)/01. App Board.md @@ -13,7 +13,7 @@ The page includes following functions

-image +image

@@ -47,7 +47,7 @@ Response Body Details to the data mapping: -image +image

@@ -82,7 +82,7 @@ Response Body Details to the data mapping: -image +image

diff --git a/docs/developer/04. Apps/05. App Subscription/01.App Subscription Request Management.md b/docs/developer/04. Apps/05. App Subscription/01.App Subscription Request Management.md index 3c440ade9..48c4852ed 100644 --- a/docs/developer/04. Apps/05. App Subscription/01.App Subscription Request Management.md +++ b/docs/developer/04. Apps/05. App Subscription/01.App Subscription Request Management.md @@ -123,7 +123,7 @@ The endpont shows all subscription requests and active subscriptions. Data mapping details:

- image + image


diff --git a/docs/developer/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md b/docs/developer/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md index a17076624..19ad62944 100644 --- a/docs/developer/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md +++ b/docs/developer/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md @@ -30,7 +30,7 @@ Its planned to change this as soon as a search engine is implemented. Filters provide two different views which can get easily switched by the user -image +image Endpoints - for "Dataspace Service": {host/domain}/api/Services/active?page=0&size=15&serviceTypeId=DATASPACE_SERVICE @@ -68,7 +68,7 @@ Only those services in status "ACTIVE" are getting displayed.
Data Mapping View: -image +image
diff --git a/docs/developer/05. Service(s)/01. Service Marketplace/02. Service Details.md b/docs/developer/05. Service(s)/01. Service Marketplace/02. Service Details.md index 4b72e8d79..6cb1424ec 100644 --- a/docs/developer/05. Service(s)/01. Service Marketplace/02. Service Details.md +++ b/docs/developer/05. Service(s)/01. Service Marketplace/02. Service Details.md @@ -24,7 +24,7 @@ When selecting an offered service, the service details are getting fetched. Data mapping logic: -image +image
@@ -88,7 +88,7 @@ Details regarding active subscriptions will be included in the get service detai
Details on the UI implementation -image +image

diff --git a/docs/developer/05. Service(s)/02. Service Release Process/02. Service Detail Page.md b/docs/developer/05. Service(s)/02. Service Release Process/02. Service Detail Page.md index f54e9e4d0..853f2e933 100644 --- a/docs/developer/05. Service(s)/02. Service Release Process/02. Service Detail Page.md +++ b/docs/developer/05. Service(s)/02. Service Release Process/02. Service Detail Page.md @@ -2,7 +2,7 @@
-image +image In the Step 2 of the publishing process, the service detail page is getting filled diff --git a/docs/developer/05. Service(s)/02. Service Release Process/03.Terms&Conditions.md b/docs/developer/05. Service(s)/02. Service Release Process/03.Terms&Conditions.md index 0dd9a4175..fef58c047 100644 --- a/docs/developer/05. Service(s)/02. Service Release Process/03.Terms&Conditions.md +++ b/docs/developer/05. Service(s)/02. Service Release Process/03.Terms&Conditions.md @@ -2,7 +2,7 @@
-image +image Depending on the response of the endpoint #1 GET agreements, the user will be enabled to download related documents from the portal to read through the relevant agreement details. Expected formats are pdf, however other formats can get supported as well. @@ -36,13 +36,13 @@ Style If documentId inside response body is != NULL display the respective agreement as link - example: -image +image
If the documentId is NULL, the agreement is displayed without link (as currently implemented) - example: -image +image

diff --git a/docs/developer/05. Service(s)/02. Service Release Process/05.Verify & Submit.md b/docs/developer/05. Service(s)/02. Service Release Process/05.Verify & Submit.md index cee865977..ed4e3482e 100644 --- a/docs/developer/05. Service(s)/02. Service Release Process/05.Verify & Submit.md +++ b/docs/developer/05. Service(s)/02. Service Release Process/05.Verify & Submit.md @@ -5,7 +5,7 @@ In case any information are incorrectly stored, use the back button on the botto
-image +image #### Implementation Details diff --git a/docs/developer/05. Service(s)/03. Service Release Approval/01. Service Approval Board Overview.md b/docs/developer/05. Service(s)/03. Service Release Approval/01. Service Approval Board Overview.md index ff2172e6f..a26886c8d 100644 --- a/docs/developer/05. Service(s)/03. Service Release Approval/01. Service Approval Board Overview.md +++ b/docs/developer/05. Service(s)/03. Service Release Approval/01. Service Approval Board Overview.md @@ -52,7 +52,7 @@ image to be added #### Sorting
-image +image
Sorting by "Newest First": {hostname}/api/services/serviceRelease/inReview?page=0&size=15&sorting=DateDesc diff --git a/docs/developer/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md b/docs/developer/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md index 124acc064..f8e1bf779 100644 --- a/docs/developer/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md +++ b/docs/developer/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md @@ -4,7 +4,7 @@ With the service release approval, the service is getting activated for the serv The approval is triggered by clicking on the approval icon inside the service card:
-image +image

diff --git a/docs/developer/05. Service(s)/03. Service Subscription/01. Service Subscription.md b/docs/developer/05. Service(s)/03. Service Subscription/01. Service Subscription.md index e30b2d0f4..6808e9507 100644 --- a/docs/developer/05. Service(s)/03. Service Subscription/01. Service Subscription.md +++ b/docs/developer/05. Service(s)/03. Service Subscription/01. Service Subscription.md @@ -23,7 +23,7 @@ Via api, the agreements will get fetched from the backend to display them to the Data mapping: -image +image
diff --git a/docs/developer/05. Service(s)/03. Service Subscription/01.Service Subscription Request Management.md b/docs/developer/05. Service(s)/03. Service Subscription/01.Service Subscription Request Management.md index 1c3ed9757..4c975ffce 100644 --- a/docs/developer/05. Service(s)/03. Service Subscription/01.Service Subscription Request Management.md +++ b/docs/developer/05. Service(s)/03. Service Subscription/01.Service Subscription Request Management.md @@ -123,7 +123,7 @@ The endpont shows all subscription requests and active subscriptions. Data mapping details:

- image + image


diff --git a/docs/developer/05. Service(s)/04. Service Provider Management Board(s)/01. App Board.md b/docs/developer/05. Service(s)/04. Service Provider Management Board(s)/01. App Board.md index dcac1e8cd..8bb5eedd2 100644 --- a/docs/developer/05. Service(s)/04. Service Provider Management Board(s)/01. App Board.md +++ b/docs/developer/05. Service(s)/04. Service Provider Management Board(s)/01. App Board.md @@ -15,7 +15,7 @@ The page includes following functions

-image +image


@@ -66,7 +66,7 @@ To display the details the service data get displayed by clicking on the app car #### Scenario: Service in Status "ACTIVE" or "INACTIVE"

-image +image


@@ -74,7 +74,7 @@ To display the details the service data get displayed by clicking on the app car #### Scenario: Service in Status "IN PROGRESS"

-image +image


diff --git a/docs/developer/Technical Documentation/Architecture/Building block view.md b/docs/developer/Technical Documentation/Architecture/Building block view.md index 6782a9389..51082e709 100644 --- a/docs/developer/Technical Documentation/Architecture/Building block view.md +++ b/docs/developer/Technical Documentation/Architecture/Building block view.md @@ -2,7 +2,7 @@ The Portal as an overall product is a complex composition of several interacting solution building blocks, each comprised of a backend (including api and db) and frontend component, depicted in the following blackbox-illustration: -image +image Beyond this view, the portal allows for component integration of other (sub-products) that need to expose user-faced ui-functionality to the Catena-X community members (company and user level). diff --git a/docs/developer/Technical Documentation/Architecture/Whitebox Overall System.md b/docs/developer/Technical Documentation/Architecture/Whitebox Overall System.md index dfa67eedb..9b81381d2 100644 --- a/docs/developer/Technical Documentation/Architecture/Whitebox Overall System.md +++ b/docs/developer/Technical Documentation/Architecture/Whitebox Overall System.md @@ -3,7 +3,7 @@ ## Summary
-image +image

@@ -13,31 +13,31 @@
Integration: Portal, Marketplace, Backend, Wallets, BPDM, SD Factory, AutoSetup, Discovery and more: -image +image

### Registration (Company Onboarding)
-image +image

### Central IdP & Shared IdP
-image +image

-image +image

### Marketplace
-image +image

diff --git a/docs/developer/Technical Documentation/DB Views and Details/App - DB - View.md b/docs/developer/Technical Documentation/DB Views and Details/App - DB - View.md index b20afb2b7..1010fef98 100644 --- a/docs/developer/Technical Documentation/DB Views and Details/App - DB - View.md +++ b/docs/developer/Technical Documentation/DB Views and Details/App - DB - View.md @@ -3,7 +3,7 @@ #### App DB Connection
-image +image

@@ -54,7 +54,7 @@ Table relation use_cases - 1:m - app_assigned_use_cases - m:1 - offers

-image +image


diff --git a/docs/developer/Technical Documentation/DB Views and Details/Connector - DB - View.md b/docs/developer/Technical Documentation/DB Views and Details/Connector - DB - View.md index 4542a849f..c33231279 100644 --- a/docs/developer/Technical Documentation/DB Views and Details/Connector - DB - View.md +++ b/docs/developer/Technical Documentation/DB Views and Details/Connector - DB - View.md @@ -1,6 +1,6 @@ ## Connector DB -image +image

diff --git a/docs/developer/Technical Documentation/DB Views and Details/Data Management.md b/docs/developer/Technical Documentation/DB Views and Details/Data Management.md index b31ce6ed2..2cb9edfe7 100644 --- a/docs/developer/Technical Documentation/DB Views and Details/Data Management.md +++ b/docs/developer/Technical Documentation/DB Views and Details/Data Management.md @@ -4,7 +4,7 @@ The CX Portal & Network Services system stores different types of data in the sa

-image +image



@@ -124,7 +124,7 @@ Central Keycloak Instance

-image +image - Technical Users diff --git a/docs/developer/Technical Documentation/DB Views and Details/Documents - DB - View.md b/docs/developer/Technical Documentation/DB Views and Details/Documents - DB - View.md index f80299c67..1f9ef6500 100644 --- a/docs/developer/Technical Documentation/DB Views and Details/Documents - DB - View.md +++ b/docs/developer/Technical Documentation/DB Views and Details/Documents - DB - View.md @@ -14,7 +14,7 @@ Mainly 4 tables are used for the documents itself
-image +image

diff --git a/docs/developer/Technical Documentation/DB Views and Details/Subscription - DB - View.md b/docs/developer/Technical Documentation/DB Views and Details/Subscription - DB - View.md index e6ec7621d..185beef01 100644 --- a/docs/developer/Technical Documentation/DB Views and Details/Subscription - DB - View.md +++ b/docs/developer/Technical Documentation/DB Views and Details/Subscription - DB - View.md @@ -2,7 +2,7 @@ ### Subscription DB Connection -image +image

diff --git a/docs/developer/Technical Documentation/Dev Process/Multi Language.md b/docs/developer/Technical Documentation/Dev Process/Multi Language.md index 73304fde2..8be9714dd 100644 --- a/docs/developer/Technical Documentation/Dev Process/Multi Language.md +++ b/docs/developer/Technical Documentation/Dev Process/Multi Language.md @@ -32,7 +32,7 @@ i18next provides following add-ons: There is a locales folder in src which contains subfolders according to respective language codes as shown in the screenshot shared, like 'de'(German), 'en'(English). These folders contain the translation.json file used for translations.
-image +image We can add additional translation files if needed for any additional language.
@@ -42,7 +42,7 @@ We can add additional translation files if needed for any additional language. Inside the CX Portal, the locales are divided by pages.
-image +image
There is one main file holding the generic translation for often used items (e.g. "approval button", headlines,...) and a file for each specific page to translate not often used values. diff --git a/docs/developer/Technical Documentation/Interface Contracts/BPDM (2).md b/docs/developer/Technical Documentation/Interface Contracts/BPDM (2).md index 1a64df000..a306da9f1 100644 --- a/docs/developer/Technical Documentation/Interface Contracts/BPDM (2).md +++ b/docs/developer/Technical Documentation/Interface Contracts/BPDM (2).md @@ -12,7 +12,7 @@ This document describes the details of the interface spec between BPDM and Porta ## Architecture Overview
-image +image

diff --git a/docs/developer/Technical Documentation/Interface Contracts/Managed Wallets.md b/docs/developer/Technical Documentation/Interface Contracts/Managed Wallets.md index 43bcefb26..d1c96eed7 100644 --- a/docs/developer/Technical Documentation/Interface Contracts/Managed Wallets.md +++ b/docs/developer/Technical Documentation/Interface Contracts/Managed Wallets.md @@ -21,7 +21,7 @@ The Portal / Managed Service connection is implemented in 2 functions #### #1 Company Registration
-image +image

@@ -36,7 +36,7 @@ The Portal / Managed Service connection is implemented in 2 functions

-image +image

diff --git a/docs/developer/Technical Documentation/Interface Contracts/Offer-Autosetup.md b/docs/developer/Technical Documentation/Interface Contracts/Offer-Autosetup.md index 121776618..07baea293 100644 --- a/docs/developer/Technical Documentation/Interface Contracts/Offer-Autosetup.md +++ b/docs/developer/Technical Documentation/Interface Contracts/Offer-Autosetup.md @@ -17,7 +17,7 @@ Following interfaces are relevant to enable the autosetup ### #1 Highlevel Architecture picture -image +image

@@ -36,7 +36,7 @@ The PUT service url is enabling the service / app provider to store/hold the ser Logic: the service provider/app provider (must be an cx member) can trigger the endpoint to store the autosetup endpoint.
-image +image
diff --git a/docs/developer/Technical Documentation/Interface Contracts/Self Description.md b/docs/developer/Technical Documentation/Interface Contracts/Self Description.md index 23a16136d..258b33a4e 100644 --- a/docs/developer/Technical Documentation/Interface Contracts/Self Description.md +++ b/docs/developer/Technical Documentation/Interface Contracts/Self Description.md @@ -23,7 +23,7 @@ In the current implementation level, self-descriptions are considered in the fol ## Architecture Overview
-image +image

diff --git a/docs/developer/Technical Documentation/Others/Document Management.md b/docs/developer/Technical Documentation/Others/Document Management.md index 084f02938..972343d45 100644 --- a/docs/developer/Technical Documentation/Others/Document Management.md +++ b/docs/developer/Technical Documentation/Others/Document Management.md @@ -13,7 +13,7 @@ In the DB table we have differentiated between documents which are uploaded by a Example User Flow which is supported by the document controller: -image +image

@@ -34,7 +34,7 @@ Mainly 4 tables are used for the documents itself
-image +image

@@ -68,7 +68,7 @@ Based on the reasons above, the document deletion is handled in 2 different func Uploading documents is limited to 8MB. The configuration for the maximum file size is set in ingress (nginx). See the last line in the screenshot below:
-image +image Additionally document size validation on FE was implemented lately where the size depends on the process. Inside the registration sizes can be following: diff --git a/docs/developer/Technical Documentation/Others/Email Templates.md b/docs/developer/Technical Documentation/Others/Email Templates.md index 3688e3677..8d325c723 100644 --- a/docs/developer/Technical Documentation/Others/Email Templates.md +++ b/docs/developer/Technical Documentation/Others/Email Templates.md @@ -51,8 +51,8 @@ currently under change Email Trigger: Invite of a new Business Partner by the CX Admin
-image -image +image +image


@@ -70,7 +70,7 @@ Email Trigger: Invite of a team member to the registration process by the compan Email Trigger: User clicked "Submit" button in the last step of the Registration Flow
-image +image


diff --git a/docs/developer/Technical Documentation/Others/Notifications.md b/docs/developer/Technical Documentation/Others/Notifications.md index e503190b3..4e6b0c4b2 100644 --- a/docs/developer/Technical Documentation/Others/Notifications.md +++ b/docs/developer/Technical Documentation/Others/Notifications.md @@ -8,7 +8,7 @@ In CX, the idea of push notification to a mobile device is something which is cu ## Architecture -image +image

@@ -17,7 +17,7 @@ In CX, the idea of push notification to a mobile device is something which is cu ##### Elements -image +image ++ highlight messages which have read status "false" ++ enable urls inside the message @@ -32,39 +32,39 @@ In CX, the idea of push notification to a mobile device is something which is cu Scenario 1 If unread messages are "0" the notification icon wont show up. Instead only the user icon will be displayed -image +image
Scenario 2 If unread messages are > 0 AND the actionRequired are = 0; the user icon with notification "false" state will get displayed. Inside the notification count bubble the number of "unread" messages will be shown. -image +image
Scenario 3 If unread messages are > 0 AND the actionRequired are > 0; the user icon with notification "true" state will get displayed. Inside the notification count bubble the number of "actionRequired" messages will be shown. -image +image
###### Notification Screen -image +image
###### Filtering -image +image
###### Deletion Process for "Action Required" Notifications -image +image
@@ -75,7 +75,7 @@ If unread messages are > 0 AND the actionRequired are > 0; the user icon with no ### Database -image +image
@@ -251,7 +251,7 @@ Unread first: {hostname}/api/Notification?page=0&size=15& notificationTopic=ACTI ....
-image +image
diff --git a/docs/user/01. Onboarding/01. Registration Invite/01. Summary.md b/docs/user/01. Onboarding/01. Registration Invite/01. Summary.md index b07e59edc..bd7e8c036 100644 --- a/docs/user/01. Onboarding/01. Registration Invite/01. Summary.md +++ b/docs/user/01. Onboarding/01. Registration Invite/01. Summary.md @@ -16,7 +16,7 @@ To ensure that the operator can support with the invite; please share for the in #### Operator Invite Flow
-image +image ## NOTICE diff --git a/docs/user/01. Onboarding/01. Registration Invite/02. FAQ.md b/docs/user/01. Onboarding/01. Registration Invite/02. FAQ.md index 539ac6a16..9e6121929 100644 --- a/docs/user/01. Onboarding/01. Registration Invite/02. FAQ.md +++ b/docs/user/01. Onboarding/01. Registration Invite/02. FAQ.md @@ -22,7 +22,7 @@ Normal users can not identify companies which are currently in the registration If you go to the partner network and search for a company, check out the membership icon. If the CX icon is displayed (example see screenshot below) the company is member of Catena-X.

-image +image

diff --git a/docs/user/01. Onboarding/02. Registration/01. Login.md b/docs/user/01. Onboarding/02. Registration/01. Login.md index 423d07d1a..3dcc8b0e3 100644 --- a/docs/user/01. Onboarding/02. Registration/01. Login.md +++ b/docs/user/01. Onboarding/02. Registration/01. Login.md @@ -16,12 +16,12 @@ Pre-condition: The authorized organization onboarding party must have received a After receiving the CX invite email (incl. registration login URL and one-time-password), the user can directly start the login to the company registration.
-image +image
After selecting the company for login; the user can login via the email and password (first time; the one-time-password shared via email) -image +image
After the successful login; the user can directly start to proceed with the company registration form. diff --git a/docs/user/01. Onboarding/02. Registration/02. Add Company Data.md b/docs/user/01. Onboarding/02. Registration/02. Add Company Data.md index ebde388e6..5b9e26958 100644 --- a/docs/user/01. Onboarding/02. Registration/02. Add Company Data.md +++ b/docs/user/01. Onboarding/02. Registration/02. Add Company Data.md @@ -7,7 +7,7 @@ Two options are available: - use your business partner number (if known) to auto fill the company data
-image +image
In case the manual data entering is used, the user will need to enter diff --git a/docs/user/01. Onboarding/02. Registration/03. Add Additional User(s).md b/docs/user/01. Onboarding/02. Registration/03. Add Additional User(s).md index 15f1697f6..2e22e7b5d 100644 --- a/docs/user/01. Onboarding/02. Registration/03. Add Additional User(s).md +++ b/docs/user/01. Onboarding/02. Registration/03. Add Additional User(s).md @@ -5,14 +5,14 @@ The 2nd step inside the registration form is optional. Means, the user can invite additional company members if support in the registration is needed. Normally this should only be relevant if an user is not authorized to finish the registration in the name of the company. E.g. missing rights to agree to terms and conditions or similar scenarios.
-image +image +image

diff --git a/docs/user/01. Onboarding/02. Registration/04. Company Role & Consent.md b/docs/user/01. Onboarding/02. Registration/04. Company Role & Consent.md index ca3b9be84..c39e7d1eb 100644 --- a/docs/user/01. Onboarding/02. Registration/04. Company Role & Consent.md +++ b/docs/user/01. Onboarding/02. Registration/04. Company Role & Consent.md @@ -4,7 +4,7 @@ Under step 3 "Company Roles & Agreements" the applicator is requested to select The role can get easily enhanced in future by enhancing or reducing the role inside the company configuration (available inside the CX Portal).
-image +image

diff --git a/docs/user/01. Onboarding/02. Registration/05. Document Upload.md b/docs/user/01. Onboarding/02. Registration/05. Document Upload.md index b667f86e4..f1ed3eb74 100644 --- a/docs/user/01. Onboarding/02. Registration/05. Document Upload.md +++ b/docs/user/01. Onboarding/02. Registration/05. Document Upload.md @@ -5,7 +5,7 @@ In Step 4, the users are asked to upload the company identification. All documents uploaded under the same application register form are shown. If a second user has already uploaded a doc, the user will be able to see as well as delete this document as well; as long as the users belong to the same company application.
-image +image

diff --git a/docs/user/01. Onboarding/02. Registration/06. Verify Registration Data.md b/docs/user/01. Onboarding/02. Registration/06. Verify Registration Data.md index fc0eef56e..32f269dd1 100644 --- a/docs/user/01. Onboarding/02. Registration/06. Verify Registration Data.md +++ b/docs/user/01. Onboarding/02. Registration/06. Verify Registration Data.md @@ -7,7 +7,7 @@ The user can revalidate if al data are correctly added. In case anything is wron With the submit of the application, the application form is getting closed and the company application data are submitted for review to the platform operator. The application verification will run through a number of identification validations as well as technical setup to enable the company to participate inside the dataspace.
-image +image

diff --git a/docs/user/01. Onboarding/03. Registration Approval/02. View Company Application(s).md b/docs/user/01. Onboarding/03. Registration Approval/02. View Company Application(s).md index 59fbd84aa..22f3275ba 100644 --- a/docs/user/01. Onboarding/03. Registration Approval/02. View Company Application(s).md +++ b/docs/user/01. Onboarding/03. Registration Approval/02. View Company Application(s).md @@ -8,7 +8,7 @@ Inside the offered board; the user can - download identification document - view the application approval process status -image +image

@@ -27,7 +27,7 @@ With using the application details button, application details such as are displayed.
-image +image
Additionally the user can easily download the document by clicking on the document title (inside the overlay or on the main page) diff --git a/docs/user/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md b/docs/user/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md index 8afe908d9..e5b0cc546 100644 --- a/docs/user/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md +++ b/docs/user/01. Onboarding/03. Registration Approval/03. Registration Approval Process.md @@ -8,7 +8,7 @@ The list below shows an overview of all application approval steps:

-image +image

@@ -27,12 +27,12 @@ In case of an failed scenario; the error code (if available) is getting recorded ### Checklist Stepper -image +image By clicking on one of the process steps, the overlay wth process step details gets displayed. Depending on the status, the user can execute a number of action / next steps. In general 3 action states are possible and defined below -image +image

@@ -63,7 +63,7 @@ The endpoint can only get triggered/executed if the application is in status "su ###### Scenario: Decline
-image +image
The administrator can decline the application if the application data are incorrect or incomplete. @@ -149,7 +149,7 @@ The "Clearinghouse Check" is getting automatically triggered when following prer - application is in status "submitted"
-image +image
The interface is an asyncron interface - due to this; the interface is explained below in two steps @@ -305,7 +305,7 @@ With the execution of the application activation, the system will:
The bpn can get manually added (as an workaround) if the registration company request doesn't have a business partner number added and the registration request is in status "submitted".
-image +image
BPNs can only get added by CX Admin's. As mentioned above, the implementation is a workaround only and will get replaced by the actual bpn connection as soon as the reference implementation is available. diff --git a/docs/user/01. Onboarding/03. Registration Approval/04. Decline Application.md b/docs/user/01. Onboarding/03. Registration Approval/04. Decline Application.md index 888cf0f7b..5561e7858 100644 --- a/docs/user/01. Onboarding/03. Registration Approval/04. Decline Application.md +++ b/docs/user/01. Onboarding/03. Registration Approval/04. Decline Application.md @@ -4,7 +4,7 @@ While the company application is processing the application validations; the adm To decline the application the "Cancel Application" Button is enabled for all applications which did not reach the "CONFIRMED" / "DECLINED" status so far.
-image +image

diff --git a/docs/user/01. Onboarding/03. Registration Approval/index.md b/docs/user/01. Onboarding/03. Registration Approval/index.md index 006f21bba..77777b5dc 100644 --- a/docs/user/01. Onboarding/03. Registration Approval/index.md +++ b/docs/user/01. Onboarding/03. Registration Approval/index.md @@ -8,7 +8,7 @@ Acting user: CX Admin (Operator) The board supports filter, search and the actual approval / validation function of new company registration requests.

-image +image

diff --git a/docs/user/01. Onboarding/index.md b/docs/user/01. Onboarding/index.md index fe2493e80..59457c7a3 100644 --- a/docs/user/01. Onboarding/index.md +++ b/docs/user/01. Onboarding/index.md @@ -9,7 +9,7 @@ In this section the registration process and approval is in focus.

-image +image


diff --git a/docs/user/02. Technical Integration/01. Connector Registration/01. Connector Overview.md b/docs/user/02. Technical Integration/01. Connector Registration/01. Connector Overview.md index 45ab91468..ddaff7e28 100644 --- a/docs/user/02. Technical Integration/01. Connector Registration/01. Connector Overview.md +++ b/docs/user/02. Technical Integration/01. Connector Registration/01. Connector Overview.md @@ -16,13 +16,13 @@ Additionally the user can register easily new connectors. #### SelfDescription Status
-image +image
#### Connector Status
-image +image
#### Connector Providers diff --git a/docs/user/02. Technical Integration/01. Connector Registration/02. Connector Registration.md b/docs/user/02. Technical Integration/01. Connector Registration/02. Connector Registration.md index 6e5d253d4..3c4adc9f0 100644 --- a/docs/user/02. Technical Integration/01. Connector Registration/02. Connector Registration.md +++ b/docs/user/02. Technical Integration/01. Connector Registration/02. Connector Registration.md @@ -8,7 +8,7 @@ Select the option "Connect company connector"

-image +image


@@ -59,7 +59,7 @@ Select the option "Connector-as-a-service"

-image +image


diff --git a/docs/user/02. Technical Integration/01. Connector Registration/05. Delete Connector.md b/docs/user/02. Technical Integration/01. Connector Registration/05. Delete Connector.md index bd2035252..6b06013e0 100644 --- a/docs/user/02. Technical Integration/01. Connector Registration/05. Delete Connector.md +++ b/docs/user/02. Technical Integration/01. Connector Registration/05. Delete Connector.md @@ -5,7 +5,7 @@ Delete own connector. The deletion will disable the discovery service for the co

-image +image


diff --git a/docs/user/02. Technical Integration/01. Connector Registration/07. FAQ.md b/docs/user/02. Technical Integration/01. Connector Registration/07. FAQ.md index b0300b9b7..7068b864a 100644 --- a/docs/user/02. Technical Integration/01. Connector Registration/07. FAQ.md +++ b/docs/user/02. Technical Integration/01. Connector Registration/07. FAQ.md @@ -10,13 +10,13 @@ The sub-menu is only available for company administrators. The connector registration will auto generate the connector self-description.

-image +image

In the following window, select the connector type. Either "Company Connector" (own Connector) or "Connector-as-a-service" (managed Connector).

-image +image

After selecting the connector and pressing "confirm" the connector form gets displayed where connector details as well as the authentication key (public key) needs to get added. @@ -38,7 +38,7 @@ Managed connectors are (3rd party managed) connectors, e.g. if a connector is ma The deletion of a connector is similar as the registration only possible if the user has enough user permissions. Ideally the company administrator or IT admin. To delete a connector registered inside the network, get to the connector overview and trigger the deletion via the delete icon. -
image +
image
With the successful deletion, the connector is getting removed from the edc discovery service.
diff --git a/docs/user/02. Technical Integration/02. Identity Provider Management/02. Configure Company IdP.md b/docs/user/02. Technical Integration/02. Identity Provider Management/02. Configure Company IdP.md index b29885f6f..86f2926d7 100644 --- a/docs/user/02. Technical Integration/02. Identity Provider Management/02. Configure Company IdP.md +++ b/docs/user/02. Technical Integration/02. Identity Provider Management/02. Configure Company IdP.md @@ -20,7 +20,7 @@ Details regarding the IAM architecture (applies for shared as well as own IdP us

-image +image


@@ -35,7 +35,7 @@ Inside the config, you will find your current registered (enabled and disabled)

-image +image


diff --git a/docs/user/03. User Management/01. User Account/02. User Account.md b/docs/user/03. User Management/01. User Account/02. User Account.md index 53ee9525c..18241684c 100644 --- a/docs/user/03. User Management/01. User Account/02. User Account.md +++ b/docs/user/03. User Management/01. User Account/02. User Account.md @@ -6,7 +6,7 @@ Only those users created under the same company account can get viewed. Users cr

-image +image

diff --git a/docs/user/03. User Management/01. User Account/03. Create new user account (single).md b/docs/user/03. User Management/01. User Account/03. Create new user account (single).md index d644146bc..de32d02f1 100644 --- a/docs/user/03. User Management/01. User Account/03. Create new user account (single).md +++ b/docs/user/03. User Management/01. User Account/03. Create new user account (single).md @@ -3,13 +3,13 @@ User with the respective user management rights can access the user management via the top right user navigation. As soon as the user management is displayed, the user can direct via the button "Identity User Management" or scroll down the page to get to the Identity User Management section where new user accounts can get created. -Select the "Add User" Button image to trigger the new user account creation dialog. +Select the "Add User" Button image to trigger the new user account creation dialog. Inside the dialog, add the users first name, last name and email. Additionally to the user information, a network role need to get selected. Based on the network role, the user will be able to have a certain permissions inside the portal.

-image +image
@@ -24,7 +24,7 @@ With the first login, the user will be asked to set a own password, password pol Role description/details can get viewed via the direct "Role Description" link provided directly above the selectable roles. Via an click on the link, the role descriptions can get viewed. -image +image

diff --git a/docs/user/03. User Management/02. Modify User Account/01. Summary.md b/docs/user/03. User Management/02. Modify User Account/01. Summary.md index 6dc8b3157..00f3ae32c 100644 --- a/docs/user/03. User Management/02. Modify User Account/01. Summary.md +++ b/docs/user/03. User Management/02. Modify User Account/01. Summary.md @@ -2,13 +2,13 @@ The "User Account Details" function is a detailed view of one user, which the company administrator can open by clicking on "details" of any users under his organization. -image +image # My CX Account The "My User Account Details" function is a detailed view of your own user account and can get viewed by the user owner only. -image +image ## NOTICE diff --git a/docs/user/03. User Management/02. Modify User Account/02. Password Reset.md b/docs/user/03. User Management/02. Modify User Account/02. Password Reset.md index 3dcd24bb7..f39875643 100644 --- a/docs/user/03. User Management/02. Modify User Account/02. Password Reset.md +++ b/docs/user/03. User Management/02. Modify User Account/02. Password Reset.md @@ -5,7 +5,7 @@ The picture below includes the service details

-image +image ### Error message handling for password reset diff --git a/docs/user/03. User Management/02. Modify User Account/03. User Permissions.md b/docs/user/03. User Management/02. Modify User Account/03. User Permissions.md index 4bc5fc167..6987d520e 100644 --- a/docs/user/03. User Management/02. Modify User Account/03. User Permissions.md +++ b/docs/user/03. User Management/02. Modify User Account/03. User Permissions.md @@ -18,7 +18,7 @@ Assigned users portal role are visible, additionally, with the necessary rights,

-image +image


@@ -28,7 +28,7 @@ Inide the pop-up, select or unselect the respective roles and click on "Confirm"

-image +image


@@ -40,7 +40,7 @@ To change user assigned app roles, open the "User Management" -> "App Access Man

-image +image


@@ -50,7 +50,7 @@ Select/Unselect the respective roles for the user and click confirm to submit th

-image +image


diff --git a/docs/user/03. User Management/02. Modify User Account/04. Manage user assigned BPN.md b/docs/user/03. User Management/02. Modify User Account/04. Manage user assigned BPN.md index 507b934e4..51479ae6d 100644 --- a/docs/user/03. User Management/02. Modify User Account/04. Manage user assigned BPN.md +++ b/docs/user/03. User Management/02. Modify User Account/04. Manage user assigned BPN.md @@ -5,7 +5,7 @@ To add a business partner number to an existing user; open the user details page (via the user management) and edit the bpn field.
-image +image

@@ -17,7 +17,7 @@ To delete a business partner number to an existing user; open the user details p Inside the overlay the "delete" icon can get used to delete an assigned bpn.
-image +image

diff --git a/docs/user/03. User Management/02. Modify User Account/06. Delete User.md b/docs/user/03. User Management/02. Modify User Account/06. Delete User.md index 98cba1850..f6e400535 100644 --- a/docs/user/03. User Management/02. Modify User Account/06. Delete User.md +++ b/docs/user/03. User Management/02. Modify User Account/06. Delete User.md @@ -19,7 +19,7 @@ More details to the audit logging can get found here: [Audit Log Details](/docs/

-image +image

@@ -27,7 +27,7 @@ More details to the audit logging can get found here: [Audit Log Details](/docs/

-image +image

diff --git a/docs/user/03. User Management/03. Technical User/02. Create Technical User.md b/docs/user/03. User Management/03. Technical User/02. Create Technical User.md index 96886b5b5..ebe557b7d 100644 --- a/docs/user/03. User Management/03. Technical User/02. Create Technical User.md +++ b/docs/user/03. User Management/03. Technical User/02. Create Technical User.md @@ -44,7 +44,7 @@ As soon as the user management is displayed, a button "Technical User Management Click on the action button "Create Technical User" to initiate the process. -image +image Enter the relevant information in the displayed overlay
@@ -55,7 +55,7 @@ Enter the relevant information in the displayed overlay

-image +image



@@ -66,7 +66,7 @@ Each technical user will have the relevant permission assigned and a user attrib

-image +image


diff --git a/docs/user/03. User Management/03. Technical User/03. Delete Technical User.md b/docs/user/03. User Management/03. Technical User/03. Delete Technical User.md index 8ae1866c8..f17dca03a 100644 --- a/docs/user/03. User Management/03. Technical User/03. Delete Technical User.md +++ b/docs/user/03. User Management/03. Technical User/03. Delete Technical User.md @@ -6,7 +6,7 @@ To delete an user, just open up the user details and click the "delete" button.

-image +image


diff --git a/docs/user/03. User Management/04. Assign App Roles/01. App Access Management Overview.md b/docs/user/03. User Management/04. Assign App Roles/01. App Access Management Overview.md index 1a56895b1..d8e914f10 100644 --- a/docs/user/03. User Management/04. Assign App Roles/01. App Access Management Overview.md +++ b/docs/user/03. User Management/04. Assign App Roles/01. App Access Management Overview.md @@ -6,7 +6,7 @@ The assigned role enables the user to access the application.

-image +image

diff --git a/docs/user/03. User Management/04. Assign App Roles/02. Assign User App Role(s).md b/docs/user/03. User Management/04. Assign App Roles/02. Assign User App Role(s).md index a762fbc7d..d87bfcc34 100644 --- a/docs/user/03. User Management/04. Assign App Roles/02. Assign User App Role(s).md +++ b/docs/user/03. User Management/04. Assign App Roles/02. Assign User App Role(s).md @@ -10,7 +10,7 @@ To enable users to access an application, minimum one application app need to ge

-image +image

diff --git a/docs/user/03. User Management/04. Assign App Roles/03. Update Users Assigned App Role(s).md b/docs/user/03. User Management/04. Assign App Roles/03. Update Users Assigned App Role(s).md index 7f83d22c8..21a822c9f 100644 --- a/docs/user/03. User Management/04. Assign App Roles/03. Update Users Assigned App Role(s).md +++ b/docs/user/03. User Management/04. Assign App Roles/03. Update Users Assigned App Role(s).md @@ -2,7 +2,7 @@ User assigned app roles can get easily modified via the user role edit button. -image +image Click on the edit button and select or unselect the respective user role. With the confirmation the user role change is taking place. diff --git a/docs/user/04. App(s)/01. Marketplace/01. App Overview.md b/docs/user/04. App(s)/01. Marketplace/01. App Overview.md index f8100ba08..33d3855b8 100644 --- a/docs/user/04. App(s)/01. Marketplace/01. App Overview.md +++ b/docs/user/04. App(s)/01. Marketplace/01. App Overview.md @@ -11,7 +11,7 @@ Beside the generic list, apps can get viewed in specific pre-configured views

-image +image


diff --git a/docs/user/04. App(s)/01. Marketplace/02. App Details.md b/docs/user/04. App(s)/01. Marketplace/02. App Details.md index e8b82e629..0e196d0e7 100644 --- a/docs/user/04. App(s)/01. Marketplace/02. App Details.md +++ b/docs/user/04. App(s)/01. Marketplace/02. App Details.md @@ -14,7 +14,7 @@ Inside the app details following information will be stored
-image +image

diff --git a/docs/user/04. App(s)/01. Marketplace/03. App Favorites.md b/docs/user/04. App(s)/01. Marketplace/03. App Favorites.md index d66b7d30e..9b355e73e 100644 --- a/docs/user/04. App(s)/01. Marketplace/03. App Favorites.md +++ b/docs/user/04. App(s)/01. Marketplace/03. App Favorites.md @@ -3,7 +3,7 @@

-image +image


diff --git a/docs/user/04. App(s)/01. Marketplace/04. My Business Apps.md b/docs/user/04. App(s)/01. Marketplace/04. My Business Apps.md index 9d50478dc..13145dd48 100644 --- a/docs/user/04. App(s)/01. Marketplace/04. My Business Apps.md +++ b/docs/user/04. App(s)/01. Marketplace/04. My Business Apps.md @@ -11,7 +11,7 @@ The component can hold up to 4 apps in one page, in case the user has more apps

-image +image


@@ -22,7 +22,7 @@ With a click on the business app tile, the user gets automatically redirected to

-image +image


diff --git a/docs/user/04. App(s)/02. App Release Process/01. App Card.md b/docs/user/04. App(s)/02. App Release Process/01. App Card.md index c3df080da..04caa2d00 100644 --- a/docs/user/04. App(s)/02. App Release Process/01. App Card.md +++ b/docs/user/04. App(s)/02. App Release Process/01. App Card.md @@ -11,7 +11,7 @@ In the Step 1 of the publishing process, the app card details are getting filled

-image +image

The input fields for language, sales manager as well as the use case selection supports the user with pre-selectable values. @@ -23,7 +23,7 @@ The app language need to get set to ensure that customers can identifier the app

-image +image


@@ -36,7 +36,7 @@ Customers will have the chance to look up use case specific apps. Select app cov

-image +image


@@ -50,7 +50,7 @@ In case there is no Sales Manager available or in case the app provider doesn't

-image +image


diff --git a/docs/user/04. App(s)/02. App Release Process/02. App Detail Page.md b/docs/user/04. App(s)/02. App Release Process/02. App Detail Page.md index 89077e72d..3f63bc610 100644 --- a/docs/user/04. App(s)/02. App Release Process/02. App Detail Page.md +++ b/docs/user/04. App(s)/02. App Release Process/02. App Detail Page.md @@ -10,7 +10,7 @@ In the Step 2 of the publishing process, the app detail page is getting filled

-image +image


@@ -56,7 +56,7 @@ As part of the app release process, the app provider has to select the respectiv

-image +image


diff --git a/docs/user/04. App(s)/02. App Release Process/03. Terms&Conditions.md b/docs/user/04. App(s)/02. App Release Process/03. Terms&Conditions.md index 243be3dec..96a4535d0 100644 --- a/docs/user/04. App(s)/02. App Release Process/03. Terms&Conditions.md +++ b/docs/user/04. App(s)/02. App Release Process/03. Terms&Conditions.md @@ -5,7 +5,7 @@ Under Step 3 - the user needs to agree to the terms and conditions of the app pu

-image +image


diff --git a/docs/user/04. App(s)/02. App Release Process/04. Technical Integration.md b/docs/user/04. App(s)/02. App Release Process/04. Technical Integration.md index 7680df868..b21d2f9ca 100644 --- a/docs/user/04. App(s)/02. App Release Process/04. Technical Integration.md +++ b/docs/user/04. App(s)/02. App Release Process/04. Technical Integration.md @@ -12,7 +12,7 @@ With the technical integration feature, the user can:

-image +image


diff --git a/docs/user/04. App(s)/02. App Release Process/App-Design_guidelines.md b/docs/user/04. App(s)/02. App Release Process/App-Design_guidelines.md index d9aaab9de..beb7351f9 100644 --- a/docs/user/04. App(s)/02. App Release Process/App-Design_guidelines.md +++ b/docs/user/04. App(s)/02. App Release Process/App-Design_guidelines.md @@ -49,7 +49,7 @@ All images used for any user interaction will receive a frame. White as well as #### App Picture Icon Template -image +image

diff --git a/docs/user/04. App(s)/03. App Release Approval/01. App Approval Board.md b/docs/user/04. App(s)/03. App Release Approval/01. App Approval Board.md index 931f3261e..6c0e9fd50 100644 --- a/docs/user/04. App(s)/03. App Release Approval/01. App Approval Board.md +++ b/docs/user/04. App(s)/03. App Release Approval/01. App Approval Board.md @@ -18,7 +18,7 @@ The page includes following functions ### Page Design
-image +image
With the initial page load, all apps waiting for a review are displayed. diff --git a/docs/user/04. App(s)/03. App Release Approval/02. App Details.md b/docs/user/04. App(s)/03. App Release Approval/02. App Details.md index e6cf976c9..5fa609996 100644 --- a/docs/user/04. App(s)/03. App Release Approval/02. App Details.md +++ b/docs/user/04. App(s)/03. App Release Approval/02. App Details.md @@ -6,7 +6,7 @@ To display the details the app data get displayed by clicking on the app card on

-image +image


diff --git a/docs/user/04. App(s)/03. App Release Approval/03. Approve App Release.md b/docs/user/04. App(s)/03. App Release Approval/03. Approve App Release.md index 99e032617..f87b62836 100644 --- a/docs/user/04. App(s)/03. App Release Approval/03. Approve App Release.md +++ b/docs/user/04. App(s)/03. App Release Approval/03. Approve App Release.md @@ -4,7 +4,7 @@ With the app release approval, the app is getting activated for the app marketpl The approval is triggered by clicking on the approval icon inside the app card:
-image +image

diff --git a/docs/user/04. App(s)/03. App Release Approval/04. Decline App Release.md b/docs/user/04. App(s)/03. App Release Approval/04. Decline App Release.md index d3ec11d23..703543bf6 100644 --- a/docs/user/04. App(s)/03. App Release Approval/04. Decline App Release.md +++ b/docs/user/04. App(s)/03. App Release Approval/04. Decline App Release.md @@ -5,7 +5,7 @@ The app release decline icon can get triggered by clicking on the decline icon i

-image +image


diff --git a/docs/user/04. App(s)/04. App Provider Management Board(s)/01. App Board.md b/docs/user/04. App(s)/04. App Provider Management Board(s)/01. App Board.md index 66b104f42..aa8592722 100644 --- a/docs/user/04. App(s)/04. App Provider Management Board(s)/01. App Board.md +++ b/docs/user/04. App(s)/04. App Provider Management Board(s)/01. App Board.md @@ -15,7 +15,7 @@ The page includes following functions ### Details -image +image

diff --git a/docs/user/04. App(s)/05. App Subscription/01. Subscription Request (Customer).md b/docs/user/04. App(s)/05. App Subscription/01. Subscription Request (Customer).md index a8adc475d..c39afb013 100644 --- a/docs/user/04. App(s)/05. App Subscription/01. Subscription Request (Customer).md +++ b/docs/user/04. App(s)/05. App Subscription/01. Subscription Request (Customer).md @@ -7,7 +7,7 @@ In the drawing below, the initial process is drafted. Important: this is a draft

-image +image

@@ -21,7 +21,7 @@ With that, the customer can manage user roles for their own users (pre-requisite

-image +image

diff --git a/docs/user/04. App(s)/06. App Change Process/01. Summary.md b/docs/user/04. App(s)/06. App Change Process/01. Summary.md index e1934669f..d6ae3d4f8 100644 --- a/docs/user/04. App(s)/06. App Change Process/01. Summary.md +++ b/docs/user/04. App(s)/06. App Change Process/01. Summary.md @@ -23,28 +23,28 @@ On purpose, the change scenarios are kept limited for the first release of "app Inside the App Overview (see following page for details: ) the app change process start got implemented: -image +image

Inactive State (in case the app is not yet "active" - in this case, the change can not get triggered) -image +image

SubMenu Disabled and enabled -image +image

Open up the sub-menu -image +image

diff --git a/docs/user/04. App(s)/06. App Change Process/04. App Deactivation.md b/docs/user/04. App(s)/06. App Change Process/04. App Deactivation.md index 3e9dd08b2..2a59d8212 100644 --- a/docs/user/04. App(s)/06. App Change Process/04. App Deactivation.md +++ b/docs/user/04. App(s)/06. App Change Process/04. App Deactivation.md @@ -6,7 +6,7 @@ The app deactivation function allows users to easily and conveniently deactivate To deactivate an app, select "Deactivate" via the app management app card sub-menu
-image +image

the app provider can deactivate the app provided inside the marketplace. @@ -16,7 +16,7 @@ Important; the process is currently not reversible. The app is getting deactivat

-image +image


diff --git a/docs/user/04. App(s)/07. App Provider Management/01. Open API.md b/docs/user/04. App(s)/07. App Provider Management/01. Open API.md index 23059e928..a64e5c767 100644 --- a/docs/user/04. App(s)/07. App Provider Management/01. Open API.md +++ b/docs/user/04. App(s)/07. App Provider Management/01. Open API.md @@ -21,7 +21,7 @@ Following interfaces are relevant to enable the autosetup ## Architecture Overview
-image +image

@@ -35,7 +35,7 @@ The PUT service url is enabling the service / app provider to store/hold the ser Logic: the service provider/app provider (must be an cx member) can trigger the endpoint to store the autosetup endpoint.
-image +image
diff --git a/docs/user/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md b/docs/user/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md index 1675e4562..abb0188fd 100644 --- a/docs/user/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md +++ b/docs/user/05. Service(s)/01. Service Marketplace/01. Service Marketplace.md @@ -15,7 +15,7 @@ Beside the generic list, services can get viewed in specific pre-configured view ### Service Marketplace Overview -image +image

diff --git a/docs/user/05. Service(s)/01. Service Marketplace/02. Service Details.md b/docs/user/05. Service(s)/01. Service Marketplace/02. Service Details.md index a96b050d7..9afe0cace 100644 --- a/docs/user/05. Service(s)/01. Service Marketplace/02. Service Details.md +++ b/docs/user/05. Service(s)/01. Service Marketplace/02. Service Details.md @@ -13,7 +13,7 @@ Service details include

-image +image

diff --git a/docs/user/05. Service(s)/02. Service Release Process/01. Service Card.md b/docs/user/05. Service(s)/02. Service Release Process/01. Service Card.md index 0e6fffade..268ef86d4 100644 --- a/docs/user/05. Service(s)/02. Service Release Process/01. Service Card.md +++ b/docs/user/05. Service(s)/02. Service Release Process/01. Service Card.md @@ -11,7 +11,7 @@ In the Step 1 of the publishing process, the service card details are getting fi

-image +image

Please make sure that you add a well defined service name. Have a look at the service marketplace to get a feeling about suitable names and define the best name for your service. diff --git a/docs/user/05. Service(s)/02. Service Release Process/02. Service Detail Page.md b/docs/user/05. Service(s)/02. Service Release Process/02. Service Detail Page.md index 8135747fa..df74c98f9 100644 --- a/docs/user/05. Service(s)/02. Service Release Process/02. Service Detail Page.md +++ b/docs/user/05. Service(s)/02. Service Release Process/02. Service Detail Page.md @@ -7,7 +7,7 @@ In the Step 2 of the publishing process, the service detail page is getting fill - provider details (optional)

-image +image


diff --git a/docs/user/05. Service(s)/02. Service Release Process/03. Terms&Conditions.md b/docs/user/05. Service(s)/02. Service Release Process/03. Terms&Conditions.md index 98fa48f0f..194c2fcd0 100644 --- a/docs/user/05. Service(s)/02. Service Release Process/03. Terms&Conditions.md +++ b/docs/user/05. Service(s)/02. Service Release Process/03. Terms&Conditions.md @@ -5,7 +5,7 @@ Under Step 3 - the user needs to agree to the terms and conditions of the servic

-image +image


diff --git a/docs/user/05. Service(s)/02. Service Release Process/05. Verify & Submit.md b/docs/user/05. Service(s)/02. Service Release Process/05. Verify & Submit.md index 02903bcb9..bced33066 100644 --- a/docs/user/05. Service(s)/02. Service Release Process/05. Verify & Submit.md +++ b/docs/user/05. Service(s)/02. Service Release Process/05. Verify & Submit.md @@ -8,7 +8,7 @@ In case any information are incorrectly stored, use the back button on the botto As soon as your entered data meet your expectations, use the "Submit" button on the bottom right to submit the service for marketplace publishing.

-image +image

diff --git a/docs/user/05. Service(s)/02. Service Release Process/index.md b/docs/user/05. Service(s)/02. Service Release Process/index.md index 911a1706f..5733fc9f3 100644 --- a/docs/user/05. Service(s)/02. Service Release Process/index.md +++ b/docs/user/05. Service(s)/02. Service Release Process/index.md @@ -16,7 +16,7 @@ and click on the action button "Register your service"
-image +image

diff --git a/docs/user/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md b/docs/user/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md index 87923c15d..6d6fb1bbd 100644 --- a/docs/user/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md +++ b/docs/user/05. Service(s)/03. Service Release Approval/03. Approve Service Release.md @@ -4,7 +4,7 @@ With the service release approval, the service is getting activated for the serv The approval is triggered by clicking on the approval icon inside the service card:
-image +image

diff --git a/docs/user/05. Service(s)/03. Service Subscription/01. Service Subscription.md b/docs/user/05. Service(s)/03. Service Subscription/01. Service Subscription.md index 8956f00cc..890ec8ab5 100644 --- a/docs/user/05. Service(s)/03. Service Subscription/01. Service Subscription.md +++ b/docs/user/05. Service(s)/03. Service Subscription/01. Service Subscription.md @@ -7,7 +7,7 @@ With the purchasing request, the user need to agree to the terms and conditions The successful service subscription request will be visible via the subscription detail section which appears in the service detail page (see picture 4 below)
-image +image