Skip to content

Commit

Permalink
release: merge release into main (#118)
Browse files Browse the repository at this point in the history
  • Loading branch information
Phil91 committed Aug 7, 2023
1 parent 1b4327b commit 3014345
Show file tree
Hide file tree
Showing 24 changed files with 345 additions and 75 deletions.
18 changes: 18 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,24 @@

New features, fixed bugs, known defects and other noteworthy changes to each release of the Catena-X Portal Assets.

## 1.6.0-RC3

### Change
* App subscription activation docu enhanced by added activation overlay screenshot as example/reference with new content body
* Application checklist retrigger information added

### Feature
* App Change documentation released
* Upgrade info added
* daps deletion

### Bugfix
* Dataspace Introduction - added missing direct links and deleted unnecesary links
* Network Participant Introduction - typos fixed

### Known Knowns
* Help application - side menu botton scrolling blocked and rendering broken

## 1.6.0-RC2

### Change
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -559,3 +559,13 @@ Response Body
}

<br>
<br>

### Details for retrigger process

retriggering any process manually always deletes the current saved comment inside application_checklist.comment to ensure that the reason for the earlier failed execution is not getting displayed to the user anymore.





Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ CX Member companies can create their technical users on their needs and map them

### Customer Functionalities covered in the function
* Create new technical user under my org
* View all my technical users (including technical user details)
* Delete a technical user
* View all my technical users (including technical user details) of owned and managed tech users
* Delete technical user


### Available technical user roles
Expand All @@ -25,7 +25,7 @@ Following technical user roles are configured/available as standard technical us
* Identity Wallet Management
* BPDM Management
* BPDM Gateway
* Dataspace Discvoery
* Dataspace Discovery
* App Tech User
* Service Management

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
<br>

<p align="center">
<img width="981" alt="image" src="https://user-images.githubusercontent.com/94133633/219899645-d584a520-a78f-478f-9082-4db6e3066369.png">
<img width="636" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/5cab4d31-3b7b-4754-9702-878e27a2a37d">
</p>

<br>
Expand Down Expand Up @@ -34,11 +34,35 @@ Permission: "view_tech_user_management"
"clientId": "string",
"name": "string",
"serviceAccountType": "MANAGED/OWN",
"offerSubscriptionId": "uuid"
"isOwner": true,
"offerSubscriptionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"connector": {
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"name": "string"
},
"offer": {
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"type": "APP",
"name": "string",
"subscriptionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}
]
}

<br>
<br>

* isOwner provides the information of the technical user is managed by another company for the acting company. Example: Company A has a managed EDC subscribed. The managed EDC provider creates in the name of Company A an technical user to connect the managed EDC to the dataspace. For Company A the technical user will get displayed as "isOwned: false" since the user exist in the name of Company A but is managed by the service provider.
* in case the technical user is not connected to any app/service - the "offer" section will be empty

<br>
<br>

#### Data Mapping (example)

<p align="center">
<img width="750" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/34d3a644-422e-4fe2-97c5-fd30861f415e">
</p>

<br>
<br>
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,9 @@ Request body

<br>
<br>

> **_NOTE:_** Technical user owner as well as provider (managed tech user owner) can run the delete endpoint - however deletion is not possible if subscription/connector are still active.
<br>
<br>

Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Business Logic:

<br>
<p align="center">
---------- image ---------- image ---------- image ----------
<img width="495" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/9c914fad-8811-47bb-9a6d-f3eed4e27214">
</p>
<br>

Expand Down
26 changes: 26 additions & 0 deletions developer/04. Apps/06. App Change Process/01. Summary.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
## Summary


The app change process is implemented to support app providers to change apps which are active.
<br>
<br>
There is a number of change scenarios, in the first implementation round the following change scenarios are considered
<br>

* App Deactivation
* Add App Role - not yet supported
* Change Documents - not yet supported
* Change Description
* Change Image

<br>

On purpose, the change scenarios are kept limited for the first release of "app change" to ensure that the implementation is supporting a number of key scenarios within the given / available implementation slot.

<br>
<br>

Functional Details: [click here](/docs/04.%20App(s)/06.%20App%20Change%20Process/01.%20Summary.md)

<br>
<br>
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
## Summary


App Providers can adjust the app lead image via the "App Overview" page.
The change has direct impact on the app card displayed on the marketplace as well as the app detail page and other connected pages where the lead image is fetched.
Please note that a delay of displaying the new lead image could appear, in case a longer cache hold of the image is configured.

Functional Description: [click](./docs/04.%20App(s)/06.%20App%20Change%20Process/02.%20Change%20App%20Lead%20Image.md)

<br>

## Implementation

```diff
POST /api/apps/AppChange/{appId}/appLeadImage
```

<br>

Request Body

image file - png/jpeg

<br>

#### Validation:

* only png and jpeg are allowed
* the user can only update the image; if the user assigned company_id is the same as the app/offer provider_company_id
* app status = "ACTIVE"


#### Logic:

* if all pre-requisites/validations are met, the document is getting stored in the portal.documents table
* link between the document and the app/offer is created in table portal.offer_assigned_documents
* previous leadImage status is changed from "LOCKED" to "INACTIVE" in table portal.documents

<br>
<br>
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
## Summary


App Providers can adjust the app description (short and long) via the "App Overview" page.
The change has direct impact on the app details displayed in the marketplace other connected pages where the app description is used/displayed.

Functional Description: [click](./docs/04.%20App(s)/06.%20App%20Change%20Process/03.%20Change%20App%20Description.md)

<br>

## Implementation

```diff
PUT /api/apps/AppChange/{appId}/appupdate/description
```

<br>

Request Body

[
{
"languageCode": "string",
"longDescription": "string",
"shortDescription": "string"
}
]

<br>

#### Validation:

* app id is found in table offers and has the offer_type_id "APP"
* calling user need to belong to the same company as the app (check via offer.provider_company_id)
* status of the app is "ACTIVE"


#### Logic:

* store the long and short description for the respective language inside the portal table offer_descriptions
* important: if records are already existing; overwrite the existing record

<br>
<br>
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
## Summary


The app deactivation function allows users to easily and conveniently deactivate their app from the app marketplace. This feature gives users the power to control their own offers and allows them to easily stop or start offer whenever they like.
The app deactivation function allows users to easily and conveniently deactivate their app from the app marketplace. This feature gives users the power to control their own offers and allows them to easily stop or start offer whenever they like.

<br>

Expand Down
26 changes: 26 additions & 0 deletions developer/04. Apps/06. App Change Process/05. App Instance Url.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
## App Tenant URL Change

The app tenant url change is in a different area located as the app offer details change.
To change the app url of a specific instance, the app subscription management board need to get opened.
Inside the board all active subscriptions can get viewed and filtered. Select the respective relevant subscription and click on "Details".

<br>

Functional Description: [Link](/docs/04.%20App(s)/06.%20App%20Change%20Process/03.%20Change%20App%20Tenant%20URL.md)

<br>
<br>

### Trigger App Instance Url Switch

```
! PUT /api/apps/appchange/{appId}/subscription/{subscriptionId}/tenantUrl
```
Request Body

{
"url": "string"
}

<br>
<br>
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,14 @@ Each section includes the respective change details, impact on existing data and
<br>
<br>

#### Connectors - CHANGED - 1.6.0

* REMOVED: removed table connector_client_details
* REMOVED: column daps_registration_successful

The DAPS was completly removed from the portal services, hence the connector_client_details table was removed, as well as the daps_registration_successful column from the connector table.


#### Technical User Profiles - NEW - 1.4.0

> **_INFO:_** Please note: the technical user profiles will remove the interim solution of technical_user_needed within the service_details table, which was introduced in 1.1.0
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,16 +3,16 @@ User with the respective user management rights can access the user management v

Inside the Technical User Management page administrator users can

* view owned and managed technical user identities which are registered under the name of the users company
* create technical users in the name of their company
* get an overview of the existing, company owned technical users
* look-up technical user details
* delete technical user

<br>
<br>

<p align="center">
<img width="636" alt="image" src="https://user-images.githubusercontent.com/94133633/220773760-c1388287-2b75-4762-9241-1c4ca703ded4.png">
<img width="636" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/f1a6c5bb-5e5d-42dd-bc88-c8bc1c301faa">
</p>
<br>
<br>
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,14 @@ The technical user deletion will immediately get active. Please ensure that you
<br>
<br>

> **_NOTE:_** Technical user owner as well as provider (managed tech user owner) can run the delete endpoint - however deletion is not possible if subscription/connector are still active.
<br>
<br>

#### Currently not supported:

update technical user secret

<br>
<br>
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ With the confirmation of the activation, the technical user credentials are crea

<br>
<p align="center">
<img width="438" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/fc426c88-2b52-43ea-9657-a2f14944bdfb">
<img width="495" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/9c914fad-8811-47bb-9a6d-f3eed4e27214">
</p>
<br>

Expand Down
6 changes: 3 additions & 3 deletions docs/04. App(s)/06. App Change Process/01. Summary.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,10 @@ There is a number of change scenarios, in the first implementation round the fol
<br>

* App Deactivation
* Add Role - not yet supported
* Add App Role - not yet supported
* Change Documents - not yet supported
* Change Description - not yet supported
* Change Image - not yet supported
* Change Description
* Change Image

<br>

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
## Summary

App Providers can adjust the app lead image via the "App Overview" page.
The change has direct impact on the app card displayed on the marketplace as well as the app detail page and other connected pages where the lead image is fetched.
Please note that a delay of displaying the new lead image could appear, in case a longer cache hold of the image is configured.

<br>

To change the app lead image, select "Change Image" via the app management app card sub-menu
<br>
<img width="254" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/af2ea87d-d9c6-4870-9aa4-3afd01f6e2d6">
<br>
<br>

By selecting the button "upload new image" the dropzone element will get displayed and the user can upload the new jpeg/png file.
Please make sure that the image has a valid size - ideally below 0.8 MB

<br>

Important; the change is not reversible. However you can upload a new image whenever you like.

<br>
<br>

<p align="center">
<img width="836" alt="image" src="https://github.com/catenax-ng/tx-portal-assets/assets/94133633/0020d840-a15e-4890-883f-9f15be69f8bd">
</p>

<br>
<br>
Loading

0 comments on commit 3014345

Please sign in to comment.