Checklists and workflow
There’s no way for a partner to configure a customers checklists.
In Next, checklists drive workflow. Checklists differ by customer and can differ by type of assignment
(sale, rent, forced sale, projects etc.).
It’s also possible to configure differences in checklists for different departments, estate types and
ownership types.
Properties and macros
Each item in the checklist can have a range of different properties. In the example above, let us refer to the different item as A,B and C. Item C can be marked to be dependent on A and B, then both A and B need to be checked before it is possible to check C. C can also be marked with dependency and auto-run. Then C will be checked and macros run as soon as A and B are checked.
A macro is a set of events executed when an item gets checked. The following macros can be used for items checked by Hub.
• Create activity
• Create expense
• Post budget expense
• Run code
• Send email
• Send SMS
• Set settlement status
Email and SMS will be sent from the main broker.
Trigger a checklist item
There are two ways to trigger checklist items in Next for a partner. Either by setting the status of an order or by calling the PUT Hub-function for checkList.
Using orders
All products defined in Next (see Next Ordreintegrasjon at https://hub.megler.vitec.net/) can run checklist items at two steps in the order
process, when the order is created and when the order status is set as delivered.
This configuration is set by the customer in Next, under “Administrasjon->Produkter fra partnere» for each supplier. (See also Adding a product in Next)
Two items can be set “Opprettet” (created) and “Ferdig” (Delivered). Created is set as soon as the order is confirmed from the partner. Delivered is set when the partner sets the order status to Delivered using POST {installationId}/Orders/{orderId}/Status
The Put function
By calling the Hub function PUT {installationId}/Estates/{estateId}/CheckList it is possible to set the
state of an item by using its tag. If the tag does not exist in the checklist for the assignment, a 412
status code is returned.
Vitec recommends the tags to have the following format HUB_
Otherwise, the item is checked and the associated macros are run. If there are macros of any other type than Hub can handle they will be ignored (for example, create a document, which is an operation that need user intervention).
In both cases, any items that have the auto-run property who gets fulfilled will be run too.
Placing orders
Orders can be placed manually from the page “Marked og tjenester” but it is also possible to place an order from the checklist. As stated in the Next Ordreintegrasjon an order can generate either a 200 or a 302 response code.
302 will open a web page for the user to add additional information and complete the order. A 200 means that the order is accepted without additional user input.
The latter is of course recommended since this will allow for a more automated workflow so try building solutions that can generate an order without user input.
Multiple order phases
There’s support for handling orders with multiple phases in the checklists as well. Consider the following example.
1. A tentative order is placed for a buyer insurance when the assignment is accepted. This is done so the premium can be calculated and returned to Next. At this point we don’t know who the buyer will be and hence can’t ask them if they want the insurance.
2. After the assignment is sold we know who the buyer is, asks them and then completes the order.
To handle this there are two items in the checklist. One for placing the order (as described under placing orders) and one (or multiple) for completing the order.
The item for completing the order will open a browser using the link provided by the partner in the last orderstatus delivered. This link is also available from the page Marked og Tjenester. This allows for the partner to have full control of the completion of the order.