Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
182 lines (111 sloc) 6.88 KB

Tutorial

Exploring basic rules

Let's try exploring the /contracts endpoint:

Just invoking it reveals an empty set.

Contract is transferred from the auction system by an automated process.

.. index:: Contracts

Creating contract

Let's say that we have conducted procedure and it has complete status. When the procedure is completed, contract (that has been created in the auction system) is transferred to the contract system automatically.

Brokers (eMalls) can't create contracts in the contract system.

The contract initially receives active.confirmaition status.

Getting contract

Let's access the URL of the created object. The internal identification of the contract (id) is noted within the Lots Registry (lot.contracts.relatedProcessID):

Getting access

In order to get rights for future contract editing, you need to use access transfer mechanism.

Let's create a transfer:

To acquire ownership on the contract, we must to use that transfer:

For futher actions to be applied you need to activate the contract. Using access_token change status of the contract to active.payment:

Now let's view contracts.

Milestones

There are 3 milestones within:

  • financing milestone;
  • approval milestone;
  • reporting milestone.

Working with the financing milestone

The milestone initially receives processing status with an auto-generated dueDate equal to (dateSigned + 60 days):

It is then when the winner has to introduce the payment (the sum suggested within the auction). As soon as the payment is received, the Organizer has to mention this date within the dateMet field. If dateMet lies within the suggested frames (up to dueDate), the milestone status will be automatically switched to met:

If dateMet is after dueDate, the milestone status will be switched to partiallyMet:

Both of the described actions result in contract being changed its status from active.payment to active.approval:

The Organizer can also switch the milestone status to notMet if the payment has not been introduced at all. This one will change the contract status to pending.unsuccessful. As long as the lot becomes pending.dissolution, the contract receives unsuccessful status.

We don't show a request for this, because it's irreversable action, and after it we cannot fully demonstrate the work with contracts.

Working with the approval milestone

The milestone initially receives scheduled status. As long as the contract receives active.approval, status of the approval milestone is changed to processing. The dueDate here is equal to (financing milestone’s dateMet + 20 business days)

The Organizer can also optionally set the dueDate of the reporting milestone. It can be done only when the reporting milestone has status scheduled. If dueDate will not be set manually, it will be set automatically.

It is then when the Organizer has to upload the Small-Scale Privatization Completion Report (documentType: approvalProtocol), note the date when the Report has been signed (dateMet field) and change status of the current milestone to met (if dateMet lies within the suggested frames) or partiallyMet (if not) by setting actual dateMet:

The actions performed lead to the contract being changed its status from active.approval to active:

In case of the Completion Report has not been introduced, the Organizer has to manually switch milestone status to notMet. This one will change the contract status to pending.unsuccessful. As long as the lot becomes pending.dissolution, the contract receives unsuccessful status.

Working with the reporting milestone

The milestone initially receives scheduled status. As long as the contract receives active, status of the reporting milestone is changed to processing. The dueDate here is equal to either (reporting milestone’s dateMet + 3 years) or the date mentioned before.

As long as all of the contract conditions have been met, the Organizer has to mention the appropriate dateMet and change status of the current milestone to met (if dateMet lies within the suggested frames) or partiallyMet (if not):

The actions performed lead to the contract being changed its status from active to pending.terminated:

As long as the lot becomes pending.sold, the contract receives terminated status so that any future modification to the contract are not allowed.

In case of the conditions have not been met, the Organizer has to manually switch milestone status to notMet. This one will change the contract status to pending.unsuccessful. As long as the lot becomes pending.dissolution, the contract receives unsuccessful status.

Uploading milestone document

Document has to be added in two stages:

  • you should upload document
  • you should set document properties "documentOf": "milesone" and "relatedItem": "{milestone.id}" in order to bind the uploaded document to the milestone:

Uploading documentation

Procuring entity can upload PDF files into the created contract. Uploading should follow the :ref:`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:

.. index:: Enquiries, Question, Answer
You can’t perform that action at this time.