Council Wide Digital PlatformNo Code Service CreationGCloud Information

Missed Bin Configuration

The configuration for the Missed Bin Collection form is fairly significant owing to the high level of configuration in the form.

But can be broken down into the following areas:

Yotta Alloy Specific Sections

Before getting into the sections which are the same irrespective of the back office application, we will first cover those which are specific to Yotta Alloy.

Back Office Mapping

This section tells the Missed Bin form which schedules to look for, which workflows, which binstoredesign, and the waste rounds schedule. I.e. you need to update the value of each to reflect your Yotta Alloy instance:

  <BackOfficeMapping>
    <Mapping Key="ScheduleCodeDesign" Value="designs_scheduleCode_5f8d5eac8dae040066c53c8c"/>
    <Mapping Key="ScheduleCode" Value="attributes_scheduleCodeCode_5f8d5f3f0e567e0066100ee7"/>
    <Mapping Key="ScheduleCodeDescription" Value="attributes_scheduleCodeName_5f8d5f052802f700676fb147"/>
    <Mapping Key="WorkflowCode" Value="attributes_scheduleCodeWorkflowID_5f8dbfdce27d98006789b4ec"/>
    <Mapping Key="BinStoreDesign" Value="designs_binStores_5fb27335fd2e4f005f4bc8f7"/>
    <Mapping Key="WasteRoundsScheduleCode" Value="attributes_wasteRoundsScheduleCode_5f8de8de8dae040066c59dae"/>
  </BackOfficeMapping>

Address Search Filter

This section tells the Missed Bin form's address look up which addresses to look for and has the primary purpose of excluding commercial addresses. The only parameter that really matters if the 'Value', which says only show addresses where the class of them starts with an R. You could change this to RD (residential) but generally R is suffice:

Round Types

These are the streams to which a person can say the missed bin relates. The label e.g. Black bin (general rubbish) is what is presented to the customer:

Incab Codes

The in cab codes are the premises events that indicate why a person's bin was not collected. E.g. for each item, there is a section of XML that maps what was received from the back office (if an event is present) and the message to present to the customer.

The following example shows the constituent elements each:

So for each event type you can set a message. The following elements are configurable:

  • EventCode - as known in the back office

  • Shortdesc - just makes it easy to identify what it is

  • Message - this is what the form will present if the event is present

Street Incidents

The section enables a council to configure the types of street event that could be set against the street a property is on where a bin was not collected as a result of a street level event. Again, the primary purpose of the config is to create and map an appropriate message to present to the customer based upon the event on their street.

For example the following is a street event, saying the bin was not emptied as a result of roadworks preventing access to the street:

So for each street event type you can set a message. The following elements are configurable:

  • EventCode - as known in the back office

  • Shortdesc - just makes it easy to identify what it is

  • Message - this is what the form will present if the event is present

August 2024 release 1.9 - Whitespace

The Missed Bin form has been enhanced for Whitespace to add new configuration to allow certain Missed Bin Event codes to be ignored when the form is being completed.

I.e. You can mark an Event Code from Whitespace as to be ignored and it will not stop the citizen from submitting the Missed Bin form

The new configuration looks like this:

<ContainerEventsToIgnore>

<Event Shortdesc="Not Presented">

</Event>

</ContainerEventsToIgnore

Example Full File

PreviousSettingsNextRequest a Bin

Last updated

Was this helpful?