Verne has the mechanism that locks down concurrent applications for the same service type once one of the concurrent in-progress applications has made it through to review.
This is applicable to the services where only one instance of a service is allowed to be in the system from Review till Approval or Rejection. Multiple concurrent applications of such service type can exist until the point in time when one application gets submitted, paid for and goes to the work queue. Whoever gets to the review stage first will take the ownership of the change until it is resolved.
Examples of such service include re-registration service, name change service, annual return service for the same compliance cycle.
How does it work?
Any user is allowed to start such application for the same entity if there are NO in-progress applications of same service type for this entity that are submitted:
- either waiting in the queue (review status)
- or returned for revision (revise status)
Whenever one of the concurrent pending applications gets submitted and successfully paid for, the following will happen:
- any attempts to start a new application of this service type for this entity will be blocked, if user attempts to start a new application in such cases, system displays an error message Companies register: “Another application of the same type for this <entity type> is currently being reviewed by the Registrar. You are not able to start a new application until this process is completed.”
- all existing in-progress application of this service type and for this entity become temporary invalid: this means that application can no longer be submitted. Refer to Invalid application handling for more details on how invalid application is presented in the system. Depending on the outcome of the submitted application – approve or reject – in-progress application can be revived or will become invalid forever.
When application gets approved, the lock down is lifted and normal business rules take effect. E.g.:
- for re-registration service – entity becomes re-registered and no longer transnational, therefore re-registration service becomes unavailable in UI. All in-progress re-registration applications for this company have now become invalid due to failure to merge because of the conflicts – Transitional Flag impact group.
- for name change service – another new name change application can now be started. In-progress application that contained name change have now become invalid due to failure to merge because of the data conflicts.
When application gets rejected, the lock down is lifted and normal business rules take effect. E.g.:
- for re-registration service – entity is still transitional, therefore another new re-registration application can now be started or any existing in-progress concurrent application that was locked is now unlocked and can be submitted
- for name change service – another name change application can now be started or any existing in-progress concurrent application that was locked is now unlocked and can be submitted
Example Scenarios
The following scenarios relate to an example of Re-registration business services
| Scenario | Expected result |
|---|---|
| Scenario 1. User A started re-registration of a company, saved it and exited. User B wants to start re-registration of the same company… | User B is allowed to start re-registration (and whoever pays first will take ownership of this company) |
| Scenario 2. User A started re-registration of a company, saved it and exited. User B started re-registration of a company, paid and submitted (application is now either waiting in the queue or was returned due to missing information). User C wants to start re-registration of the same company… | User C is NOT allowed to start re-registration while there is one in review/revise. User A’s application is invalid and user is not able to progress it any further. |
| Scenario 3. User B started re-registration of a company, paid and submitted. Application was rejected. User C wants to start re-registration of the same company… | User C is allowed to start re-registration |
| Scenario 4. User B started re-registration of a company, paid and submitted. Application was approved. User C wants to start re-registration of the same company… | User C will not be able to start re-registration since re-registration is only available for transitional companies |
| Scenario 5. User A started re-registration of a company, filled in the entire form and selected Pay Later. User B started re-registration of the same company, paid, submitted and it was approved. User A wants to continue their application | User A is NOT allowed to continue their re-registration application as it is now invalid due to merging conflicts. Note, in this case the message on User A’s dashboard will be about “merge conflicts” and not about “concurrent lock-down” |
