Difference between revisions of "Railbuyer-onboarding"

Revision as of 12:19, 26 August 2024

The process is setup by creating a digital approval rule in the App:Approval_strategies_administration .
Then the FE app:registration website needs to be installed for the tenant where the approval rule is administered.
The digital API then processes the requests and saves it in the digital DB

@@ Line 1: / Line 1: @@
-FE: zugseil-sbb-landing-page  # save-digital-creation-request (DIG_DigitalCreationRequest) # -> API: zugseil digital
+[[File:ProcessMapRailbuyerApproval.png|thumb]]
-FE: zugseil-sbb-landing-page  # check-domain-availability (DIG_CheckDomainNameAvailability_Request) # -> API: zugseil digital
+# The process is setup by creating a digital approval rule in the [[App:Approval_strategies_administration]] .
+# Then the FE  [[app:registration website]] needs to be installed for the tenant where the approval rule is administered.
-API: zugseil digital # MT DIG_MT_CheckDomainNameAvailability_Request # -> API: zugseil digital
+# The digital API then processes the requests and saves it in the digital DB
-API: zugseil digital # MT DIG_MT_CheckDomainNameAvailability_Response # -> API: zugseil digital
-CRON: bop clearance process agent  # DigitalCreationClearanceProcessingService -> Create request for API: zugseil pendingtasks
-FE zugseil pendingtasks # send-digital-creation-clearance-response  (PT_SendDigitalCreationClearanceResponse_Parameter) # API: zugseil pendingtasks # MT BOp_CP_VoteOnClearances_Request # API: bop clearance process agent # MT BOp_CP_VoteOnClearances_Response # API: zugseil pendingtasks