Let’s create a framework:
We have 201 Created response code, Location header and body with extra properties.
Framework was created in draft status. In this status any field, except technical, can be changed using PATCH method.
Procuring entity can upload files into the created framework. Uploading should follow the upload rules.
201 Created response code and Location header confirm document creation. We can additionally query the documents collection API endpoint to confirm the action:
And again we can confirm that there are two documents uploaded.
In case we made an error, we can reupload the document over the older version:
And we can see that it is overriding the original version:
The second step is moving the framework to active status.
qualificationPeriod.endDate should be in between 30 and 1095 days from activation moment.
There should be at least 1 document in addition to sign document.
After framework activation frameworks periods was calculated:
enquiryPeriod - first 10 full working days after activation.
period - period when suppliers can add submissions.
qualificationPeriod - last 30 full calendar days of framework when suppliers cannot add submissions but still can be qualified based on previous submissions.
Let's check what framework registry contains:
We do see the internal id of a framework and its dateModified datestamp.
In active status only some fields can be changed: telephone, name, email for procuringEntity.contactPoint, endDate for qualificationPeriod, description and documents.
If qualificationPeriod.endDate was changed all periods will be recalculated.
Additionally, the dateModified property was updated to reflect the last modification datestamp.
Checking the listing again reflects the new modification date:
After activating framework, users can register their submissions in period from framework.period.startDate to `framework.period.endDate`:
We have 201 Created response code, Location header and body with extra properties.
Documents can be uploaded/changed only for submission in draft status.
Documents operations is same like in framework:
Submission can be deleted only in draft status:
Submission can be changed only in draft status:
Submission can be activated before period.endDate
After activating the submission, a qualification object is automatically created and submission qualificationID field is filled.
Let's check what submission registry contains:
Let's check created qualification object:
All operations with qualification object can do only framework_owner.
Documents can be uploaded/changed only for qualification in pending status.
Documents operations is same like in framework:
Qualification can be cancelled only in pending status.
After cancelling qualification, related submission changed status from active to complete.
Let's check what happen with submissions after cancelling qualification:
Qualification can be approved only in pending status.
After approving qualification, if it was first active qualification system create agreement with contract otherwise system add contract to agreement.
Let's check current framework
You can see that agreementID appeared in current framework, so let's check that agreement:
As you can see agreement now in active status, and already have contract, so we can see that agreement in agreement feed:
Let's check what qualification registry contains:
Let's check all qualifications for current framework:
Framework is completed automatically at qualificationPeriod.endDate moment.
PATCH with new qualificationPeriod.endDate allow to complete framework earlier than was planned, but not earlier than 30 full calendar days from change moment.