Infoland Flex - Flows

This page will contain two different flows. One standard, and one more automatic and customizable.

Both flows should implement the required components. Which can be found here: Required basic components

You can omit the search since it's automatically performed when loading the product list. The loading of the product list can be configured to trigger again once the user has completed utilizing the search feature. Refer to the usage guide for a detailed understanding of how these functions operate.

Standard flow (simple setup)

You has to do Page setup first. Then the only thing you would need to do is call the function for loading the receipt with the order number.

Pros:

• Can see a visual representation of current status

• Can download files belonging to the product

• Visual representation of order information

• Can send and receive messages from suppliers

• Does not have to implement API-calls for files, status and order info

Cons:

• No customization

• User has to continually check status

Custom flow (advanced setup, must implement api calls)

You has to have to do Page setup first.

Order files:

You would need to poll this endpoint to receive files for the whole order:

More information about how the output will look like.

Order information:

To access information regarding the statuses of individual products and the overall order, utilize this feature.

More information about how the output will look like.

Order confirmation:

This endpoint will return: Order messages, property information for the order, products and their assets. It is essentially a summary of the first two API-calls, and more in one endpoint.

More information about how the output will look like.

Pros:

• Flexibility and customization

• Can download files

• Checking statuses

• More detailed from API compared to visual

Cons:

• Have to poll API changes

• Have to make visual presentation

• Has to implement some logic for this

Next step: Infoland Flex - Javascript components