Waste Localisation

IEG4's waste integration happens via its own Waste API that is capable of 'speaking' to Yotta Alloy, Bartec Collective and Whitespace Powersuite.

Because it does this it has a set of configuration to aid the translation from one API to the other.

Missed Bin Collection - API Configuration

The details this file holds and are needed for this to function are:

  • Container Types including:

    • code

    • colour (waste stream colour of Blue, Blue, Green, Brown)

    • round type e.g. REF = Refuse

    • name e.g. Small Black Bin

  • Round Types including:

    • round type e.g. REC for recycling

    • colour (waste stream colour of Blue, Blue, Green, Brown)

    • name of the round

    • description of the round

  • Settings including (but not necessarily required for all waste systems):

    • Street complete code - which back office code should be looked for to determine if a street is completed or not

    • Service Type ID - which service request type should be used for the use case

    • Service Status ID - which service request type status should be used for the use case

    • Service Source - this will be the waste application in question E.g. Alloy / Collective

    • Service SLA ID - which service request type SLAID should be used for the use case

    • Service CrewID - which service request CrewID should be used

    • Service LandTypeID - which service request LandTypeID should be used

    • Post Service Status ID - which service request type status should be used for the use case (Bartec Only) after the service request has already been created

  • Street Issues (Events) including:

    • Description

    • Message

    • Code (as held in the back office)

  • Container Issue (Events) codes including:

    • The code

    • Note - for Bartec - the config is capable of handling event ids and events where there are sub-events. Where there are sub events simply separate them from the event with a hyphen. E.g. if the event id was 264 and the event sub event id was 680 then it would be this:

        "264-680"

Example File

Request a Bin - API Configuration

This is the configuration we need to set our side for this form.

Example File

Bulky Waste Collection - API Configuration

This is the configuration we need to set our side for this form.

Example File

Clinical Waste Collection - API Configuration

This is the configuration we need to set our side for this form.

Example File

Assisted Collection - API Configuration

This is the configuration we need to set our side for this form.

Example File

Garden Subscriptions - Whitespace API Configuration

Filename: configuration/serviceconfigurationmappings.json

ContractStartDay / Month - this is the date that the form will use when determining whether the subscription renewal period is open.

RenewablePeriodDays - combined with the start day and month this will determine the renewal period.

RemovePremisesBinCountFromSubscriptionOptions - when set to true the number of bins held at the address on the waste system will not be available to select if changing an existing subscription.

UsePremisesBinCountForBinsToOrderOptions - when set to true the number of bins held at the address on the waste system will determine how many bins can be requested to make up a subscription i.e. if a premise has 1 bin on the waste system and the resident selects a 2 bin subscription they will only be able to order 1 additional bin. If set to false the opposite applies and the resident could order 1 or 2 bins for a 2 bin subscription even if the waste system has 1 bin at the address already.

UseDeliverBinDropdownCountInOrderCreation - when set to true the bins to order worksheet will automatically determine the number of bins based on the subscription chosen and the number of bins at the premise. When set to false the number of bins requested by the resident on the form will be used instead.

Example configuration file:

Garden Subscriptions - Alloy API Configuration

Filename: configuration/serviceconfigurationmappingsv2.json

ContractStartDay / Month - this is the date that the form will use when determining whether the subscription renewal period is open.

RenewablePeriodDays - combined with the start day and month this will determine the renewal period.

addressSearchFilters - allows a prefix to be set to exclude certain addresses e.g. parent properties

SubscriptionTypes - defines the subscriptions that are available and the pricing. Each subscription corresponds to a container code on Alloy.

PaymentProviderConfigId - enables separate finance codes to be set per subscription type (if required).

Last updated

Was this helpful?