Ambita.Infoland.init
This is used for configuration of the components, available props are:
Name | Required | Type | Options | Description |
---|---|---|---|---|
| True | string | This property is used for setting the id of the html element you want the components to load. | |
| True | string |
| Determine what type of products that will be available in the product list. If your application have different types of users, you might want to make this dynamic based on the logged in user (brokers and architects might want different products). |
| True | object / string | This is where you pass in the token for the logged in user, see Infoland Flex - Authentication for more information. Could be the entire token object or only the access token. | |
| True | string | The reference property is added to the order when placed. This must be something that connects the order to the entity in your application that the user can relate to and have an understanding of. Could be an ID or key unique to an assignment or a project. The reference will show up on the invoices from Ambita | |
| False | string | The technical reference is added to the order and can be used by your application, in case you want to track the orders. We recommend using this when handling file deliveries, see Infoland Flex - File Handling . | |
| False | number | Used in spesial cases only | |
| False | function | This function must be used to save the order id in your application, you need this to handle file deliveries later, see Infoland Flex - File Handling . |
Ambita.Infoland.load
This function will do the actual loading of the components and takes inn a json object as a search query.
You should try to fill out as much as possible of these fields, depending on what type of property you want to buy. You should always try to fill out as much as possible and the components will calculate what property you are looking for based on the query.
Name | Description |
---|---|
| |
| |
| |
|