Skip to content

Commit

Permalink
Merge pull request #1256 from ds-crehm/chore/1007-data-sovereignty
Browse files Browse the repository at this point in the history
chore(documentation): #1007 fix diagram titles
  • Loading branch information
ds-mwesener authored Jul 22, 2024
2 parents 9547a08 + 67be707 commit 49bbbed
Showing 1 changed file with 4 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ The policies used for sending and receiving notifications and parts have an iden
The processes itself are different and will be explained here:

== Policies for sending and receiving parts
[plantuml, target=level-1, format=svg]
[plantuml, target=data-sovereignty-publish-assets, format=svg]
....
include::../../../../uml-diagrams/arc42/runtime-view/data-sovereignty/data-sovereignty-publishing-assets.puml[]
....
Expand Down Expand Up @@ -75,7 +75,7 @@ It's possible to publish parts with different policies. For this, the user must
**[Work-in-progress]** The user may also choose parts that have already been published - they can be republished with a different policy. The process for this is identical to the regular publishing process.

== Policies for sending and receiving notifications
[plantuml, target=level-1, format=svg]
[plantuml, target=data-sovereignty-notifications, format=svg]
....
include::../../../../uml-diagrams/arc42/runtime-view/data-sovereignty/data-sovereignty-notifications.puml[]
....
Expand Down Expand Up @@ -117,15 +117,15 @@ include::../../../../uml-diagrams/arc42/runtime-view/data-sovereignty/data-sover
|===

=== No policies when sending notifications
[plantuml, target=level-1, format=svg]
[plantuml, target=data-sovereignty-notifications-policy-change, format=svg]
....
include::../../../../uml-diagrams/arc42/runtime-view/data-sovereignty/data-sovereignty-notifications-policy-change.puml[]
....

If no policies are configured for the receiving BPN and a notification is sent to that BPN, the default policy of Trace-X is used as a backup. If the default policy is accepted by the receiving BPN, the process can continue as normally and the notification can be sent. When the policy does not match and the notification can't be sent, an administrator can create policies for the receiving BPN. Then the notification can be resent and will use the new policy.

=== Expired policy when sending notifications
[plantuml, target=level-1, format=svg]
[plantuml, target=data-sovereignty-expired-policy, format=svg]
....
include::../../../../uml-diagrams/arc42/runtime-view/data-sovereignty/data-sovereignty-notifications-policy-expired.puml[]
....
Expand Down

0 comments on commit 49bbbed

Please sign in to comment.