Add new notification methods to the app/service registration process

[MaximilianHauer]

Overview

Explain the topic in 2 sentences

The Application/Service creation process should be enhanced with an option to add e-mails where mails are send as soon as a customer is subscribing the service/app

What's the benefit?

It provides the options to target the groups of interest more narrowly and reduced the need of checking actively the notifications in the portal.

What are the Risks/Dependencies ?

no risks identified

Detailed explanation

Current implementation

currently a service/app provider is only informed of a new customer subscription via notification in the portal or by activly checking the subscription requests in the appSubscription page

Proposed improvements

During the creation process of an App/Service the user should receive the option to add a bucnh of emails that will be then informed by a mail as soon as someone is subscribing their service/app

(optional) in the same process step the user should be able to define the text present in the email .

Feature Team

Contributor

• @MaximilianHauer
• @maximilianong

Committer

• Committer 1
• Committer 2

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

Acceptance Criteria

• [ ] Criteria 1
• [ ] Criteria 2
• [ ] Criteria 3

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• [X] This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
  • [] CX-0010 Business Partner Number
  • [ ] CX-0013 Identity of Member Companies
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • [ ] CX-0049 DID Document Schema
  • [ ] CX-0050 Framework Agreement Credential
  • [ ] CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
  • [ ] CX-0001 EDC Discovery API
  • [ ] CX-0002 Digital Twins in Catena-X
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • Data Format:
  • [ ] The data model is based on a published Semantic Model
• [ ] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• [ ] Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• [ ] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[maximilianong]

Hi @MaximilianHauer Could we add a configuration option to change the button text from "Subscribe" to "Get Offer"? Additionally, it would be helpful to communicate with the customer, for example: "Sales will contact you soon." Pop-Up. After that, the button could change its status to "Offer in Preparation."

[MaximilianHauer]

@ybidois / @maximilianong if we develop something like this we would need to discuss how we handle the migration from the old apps/services as we change the structure how technical users are created we would need to deprecate the old service/apps and create a new one. This should be only important for the bpdm services as they need more than 1 tec user atm nevertheless we should be aware of the prod impact.

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out
• Please addcommitter
• Please add assignee (overall responsible person who drives the feature)

[MaximilianHauer]

as aligned with @maximilianong the feature is not needed for the moment.
we will align on the minor adjustments on a bilateral format and implement it on story level.