Difference between revisions of "Railbuyer-onboarding"

From ZUGSEIL Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
FE: zugseil-sbb-landing-page  # save-digital-creation-request (DIG_DigitalCreationRequest) # -> API: zugseil digital
[[File:ProcessMapRailbuyerApproval.png|thumb]]Request creation:
# 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.
Request processing:


FE: zugseil-sbb-landing-page  # check-domain-availability (DIG_CheckDomainNameAvailability_Request) # -> API: zugseil digital
# The [[Dev:Approval agent|Clearance agent]] goes over all the digitals that have Approval rules setup and checks if needs to create clearance requests for the [[App:Task manager|Task Manager]]


API: zugseil digital # MT DIG_MT_CheckDomainNameAvailability_Request # -> API: zugseil digital
Request Approval


API: zugseil digital # MT DIG_MT_CheckDomainNameAvailability_Response # -> API: zugseil digital
# The Request is approved over the [[App:Task manager|Task Manager]] and upon receiving an answer from the [[Dev:Approval agent|Clearance agent]] the digital API sends a message to a hardcoded Digital where the deployment process starts over the digital API.


CRON: bop clearance process agent  # DigitalCreationClearanceProcessingService -> Create request for API: zugseil pendingtasks
== Notes ==
The digital creator has some configuration files for static components


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
/var/zugseil/api/digital/Resources/Templates/Railbuyer
 
[[File:Digital creator settings.png]]

Latest revision as of 08:31, 9 October 2024

ProcessMapRailbuyerApproval.png

Request creation:

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

Request processing:

  1. The Clearance agent goes over all the digitals that have Approval rules setup and checks if needs to create clearance requests for the Task Manager

Request Approval

  1. The Request is approved over the Task Manager and upon receiving an answer from the Clearance agent the digital API sends a message to a hardcoded Digital where the deployment process starts over the digital API.

Notes

The digital creator has some configuration files for static components

/var/zugseil/api/digital/Resources/Templates/Railbuyer

Digital creator settings.png

Retrieved from "https://wiki.zugseil.com/en/index.php?title=Railbuyer-onboarding&oldid=28562"