When the system is deployed for the first time, it is crucial to have an initial Business Process Number (BPN) assigned to the operator to ensure that core components, such as Keycloak, function correctly. This initial BPN will serve as a foundational identifier for the operator within the system.
BPN Generation:
The system should generate a valid BPN for the operator using the predefined format:
Prefix: "BPN"
Classification: "L" (Legal Entity)
Identifier: A 10-character alphanumeric string
Two-digit checksum
Component Integration:
Ensure the generated BPN is accessible to core components like Keycloak.
Additional information
Notes:
[ ] Ensure the BPN generation logic adheres to the ISO 7064 MOD 1271-36 checksum algorithm.
[ ] The initial BPN should be marked in a way that distinguishes it as the operator's BPN.
[ ] The process should be idempotent, meaning that re-deployments should not create additional initial BPNs if one already exists.
By implementing this user story, the system will have a robust mechanism to initialize an essential identifier needed for core operations during the first deployment. This setup will ensure smooth functioning and integration of critical components like Keycloak right from the start.
Checksum Warning:
no checksum checks could be performed due to the changing algorithm.
Description
When the system is deployed for the first time, it is crucial to have an initial Business Process Number (BPN) assigned to the operator to ensure that core components, such as Keycloak, function correctly. This initial BPN will serve as a foundational identifier for the operator within the system.
BPN Generation:
The system should generate a valid BPN for the operator using the predefined format: Prefix: "BPN" Classification: "L" (Legal Entity) Identifier: A 10-character alphanumeric string Two-digit checksum
Component Integration:
Ensure the generated BPN is accessible to core components like Keycloak.
Additional information
Notes:
By implementing this user story, the system will have a robust mechanism to initialize an essential identifier needed for core operations during the first deployment. This setup will ensure smooth functioning and integration of critical components like Keycloak right from the start.
Checksum Warning:
no checksum checks could be performed due to the changing algorithm.