Predefined Content Guide › Business Logic Modules › Library Modules › Within X Business Days By Timeslots Extension Library

Within X Business Days By Timeslots Extension Library

This module extends the Within X Business Days module, giving it the ability to handle multiple source timeslots. To enable this functionality the user must include the extension library, as well as the resolution module in the metric. The extended library has two new parameters that need to be populated.

• RegistrationList - This is a table parameter. The table has one column called LocationId. This parameter needs to contain a list of the names of all the metrics that send the timeslot enter and timeslot exit events for the locations relevant to the metric (as created from the Timeslot Events Sender module). The list must contain the names of the metrics that send events and not the names of the location. For example, if the name of the metrics has the prefix Location – , then the list should contain values such as Location – France and Location – Spain. This list is used to register and receive the timeslot enter and timeslot exit events for the specified locations.
• EventLocationId - This parameter tells the system how to find the location information within the details of each event it handles. This can be done in one of three ways:
  • The name of the event type field containing the location information. In this case the content of the parameter is the name of the corresponding field.
  • Event specific information not contained in the event details. To access this information, the first character must be an @:
    • @resource – The name of the resource that sent the event.
    • @eventtype – The name of the event type that sent the event.
    • @sendermetric – The name of the metric that sent the event.
  • The user can supply any expression that can be evaluated in VBS. This can be used to access more than one field or to access the custom attribute information of the sending resource. To use this functionality, the first character must be an ‘=’ (equal sign). For example, to extract the custom attribute of the resource that the event was sent on, we would use:

    =eventDetails.CustomAttribute("MyAttribute")
    

    This would use the value of the myAttribute custom attribute of the resource that sent the event as the location identifier of the event.