View source for Railbuyer-onboarding

[[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:

# 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]]

Request Approval

# 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.

== Notes ==
The digital creator has some configuration files for static components

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

[[File:Digital creator settings.png]]