Enabling Crowd Widget

Source: This article refers to Enabling Crowd Widget

Attention: The following step must be completed by a member of your organization with the ADMIN role.

In a Nutshell

In order to assign service calls and activities to external service providers, you must enable the crowd widget that displays on the Workforce Management app.


Implementation

The Crowd Service company settings are managed in Admin & Config > Company > Settings.

By default, the Crowd settings are inactive.

Important Only the Crowd.Enabled setting must be activated in order to use the Crowd Service auto-scheduling widget.

Settings

Setting Type Description
Crowd.enabled Boolean if crowding is enabled for this company
Crowd.minimumCrowdQueueSize Integer Minimum size of the crowding queue to trigger dispatch
Crowd.timeIntervalSeconds Integer Time when the crowding action will take place.
Crowd.maxRetries Integer Number of retries in case of rejection
Crowd.rejectEnabled Boolean If the technician can reject a task, or only accept and let it timeout.
Crowd.notificationOnCrowdDispatchFailed Boolean When at least one job failed to be scheduled
Crowd.notificationOnCrowdDispatchFinished Boolean  
Crowd.notificationOnServicePartnerAccepted Boolean  
Crowd.notificationOnServicePartnerRejected Boolean  
Crowd.scheduleOnlyServicePartners Boolean Indicate if only technicians of the service providers are to be scheduled, or the own technicians are also included
Crowd.acceptanceTimeoutSeconds Integer time, in seconds, the technician has to accept activity

Example Crowd Service Configuration

Please note the following in the example below:

  • Crowd is enabled
  • Service will crowd when 50 activities are in the queue, or when 5 minutes are elapsed since last crowding ended
  • Technician can reject and each activity can be rejected 3 times before going out of the queue notifications are sent in case crowding does not schedule some activities, or when technician rejects
[{ "name": "CoreSystems.CoresystemsFSM.Crowd.numberRetriesAfterRejection", "value": "3" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.onScheduleRelease", "value": "false" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.rejectEnabled", "value": "true" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.timeToAcceptMinutes", "value": "60" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.acceptanceTimeoutSeconds", "value": "900" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.enabled", "value": "true" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.minimumQueueSize", "value": "2" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.timeIntervalSeconds", "value": "45" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.maxRetries", "value": "3" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.notificationOnDispatchFailed", "value": "true" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.notificationOnDispatchFinished", "value": "false" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.notificationOnServicePartnerAccepted", "value": "false" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.notificationOnServicePartnerRejected", "value": "true" }, { "name": "CoreSystems.CoresystemsFSM.Crowd.scheduleOnlyServicePartners", "value": "false" } ]

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.