<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Trailblazer Community Latest Ideas</title>
		<link>https://trailblazer.salesforce.com/</link>
		<description>Latest Ideas submitted on Trailblazer Community</description>
			<item>
				<title>Gantt Label for Service Territories</title>
				<pubDate>Wed, 7 Jul 2021 18:58:31 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000wnaWQAQ</link>
				<description>We have hundreds of service territories, each representing a parter account. The service territory Name is the name of the account, and each service territory has a Facility ID. Facility IDs have prefixes by geography, which makes it much easier for the dispatchers to quickly search for the right territory.&lt;br&gt;&lt;br&gt;For example, instead of searching for &amp;quot;Awesome Service Territory&amp;quot;, they would search by entering &amp;quot;95&amp;quot;, because the facility ID is 95366. The dispatcher knows Awesome Service Territory is in Los Angeles, and the LA area prefix is &amp;quot;95.&amp;quot; This also helps when there are territories with similar/identical names. &lt;br&gt;&lt;br&gt;Currently, we are naming the service territories &amp;quot;95366 - Awesome Service Territory.&amp;quot; We would prefer to store the two data points in two fields, and then use a Gantt Label to concatenate them, as the service resource and service appointments do.
					
				</description>
			</item>
			<item>
				<title>Undo Button for Field Service Dispatcher GANTT Chart</title>
				<pubDate>Sat, 29 May 2021 16:04:32 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000015LiLQAU</link>
				<description>It would be very handy if an Undo/Redo button could be added to the Field Service Dispatcher Gantt Chart. It&amp;#39;s easy to accidentally slide an appointment or make a change that could slide the appointment to a different week (and therefore out of the current view).
					
				</description>
			</item>
			<item>
				<title>Make Service Crews more dynamic.</title>
				<pubDate>Tue, 4 May 2021 10:45:14 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000M4JvQAK</link>
				<description>&lt;p&gt;When assigningen a new Service Resource to a Service Crew and that Crew is already Dispatched to a Service Appointment. The new user can&amp;#39;t see the Service Appointment.&lt;/p&gt;

&lt;p&gt;The appointment needs to be moved to Scheduled and to Dispatch again. &lt;/p&gt;

&lt;p&gt;There are already a lot of functionality missing to Service Crews, but this one needs to be there to make them plannable in a scalable way&lt;/p&gt;

&lt;p&gt; &lt;/p&gt;

&lt;p&gt; &lt;/p&gt;
					
				</description>
			</item>
			<item>
				<title>Move Resource Absences To Other Technicians On Dispatcher Console</title>
				<pubDate>Mon, 3 May 2021 15:43:09 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000lgTLQAY</link>
				<description>From the dispatcher console dispatchers are able to move Service Appointments from one technician to another by simply dragging the record to the desired technician at the desired time.&lt;br&gt;&lt;br&gt;This functionality is not possible with the Resource Absences visible on the dispatcher console. The dispatcher can move the absence to a different time for the assigned technician, but cannot move the absence to a different technician.
					
				</description>
			</item>
			<item>
				<title>show shifts in Gantt</title>
				<pubDate>Fri, 9 Apr 2021 09:59:33 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000015LOGQA2</link>
				<description>With Shift management shifts are created for engineer. With this we put engineers on dedicated &amp;#39;work-type&amp;#39; related shifts, ie &amp;#39;urgent breakdown&amp;#39;-shift.&lt;br&gt;&lt;br&gt;The disptacher is not able to take this into account when scheduling a job. The assigned shift is not visible in the Dispatch Center Gantt and therefore the dispatcher misses essential information in order to take the shift into account.&lt;br&gt;&lt;br&gt;Request: show in the Gantt as a colored layer when a shift is present per engineer and active period.
					
				</description>
			</item>
			<item>
				<title>Customizing the color for rule violations in Dispatch Console</title>
				<pubDate>Thu, 11 Mar 2021 06:16:40 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000003lowQAA</link>
				<description>As per current behaviour, if there is a rule violation on a service appointment, there will be a &amp;quot;!&amp;quot; icon show on the Gantt view and list in dispatch console. This &amp;quot;!&amp;quot; icon will appear depend on the Scheduling Policy.&lt;br&gt;&lt;br&gt;It will be good to have a function to allow dispatcher to accept the violation (like changing to another color after accepted).
					
				</description>
			</item>
			<item>
				<title>On Field Service Map Report Layer Selections Should Persist</title>
				<pubDate>Fri, 5 Mar 2021 15:08:29 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000UKuYQAW</link>
				<description>When displaying markers from a Report on the Field Service Dispacher Console Map you need to reselect the report that you want to display every time that you open the map.  The other map layer selections that display markers (like Service Resources, Service Appointments) persist so the Report-based layers selected should also persist.
					
				</description>
			</item>
			<item>
				<title>Field Service Map Report Marker Pop-up Label Should Be Title of Report</title>
				<pubDate>Fri, 5 Mar 2021 15:03:45 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000UKuTQAW</link>
				<description>When using a Report to display markers on the Field Service Dispatcher Console Map if you select a displayed marker on the map the title/lable of the pop-up that appears is always &amp;quot;REPORT PROPERTIES&amp;quot;.  This title should be the Name of the Report from which the marker is displayed.
					
				</description>
			</item>
			<item>
				<title>Make the Scheduling Window Length in Field Service Dispatch Console customizable</title>
				<pubDate>Tue, 23 Feb 2021 22:14:40 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000015KrGQAU</link>
				<description>It would be good to have the Scheduling Window Length be a customizable value. Currently the maximum allowable value is 60 days, which limits what is returned in the Service Appointment window. Our work orders are typically more than 2 months long, the average being 6 months for each appointment. This limits what is returned to us based on the date filled in the horizon window.
					
				</description>
			</item>
			<item>
				<title>Gantt Map tab: prevent users (or profiles) from switching on Map Layers</title>
				<pubDate>Wed, 17 Feb 2021 12:50:17 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000UKkSQAW</link>
				<description>&lt;u&gt;Situation&lt;/u&gt;&lt;br&gt;Due to privacy concers &amp;amp; GDPR regulations, not all users that have access to the dispatcher console map tab are allowed to see the different layers on the map like &amp;#39;Live Positions&amp;#39; and &amp;#39;Home Base&amp;#39; (FSL__UserSetting__c.FSL__Map_Object_Markers__c). At this moment, all users that have access to the dispatcher console, can see the Map Tab &amp;amp; can select/deselect all layers according to their wishes.&lt;br&gt;&lt;br&gt;&lt;u&gt;Objective&lt;/u&gt;&lt;br&gt;To make sure that the Dispatcher Console can be used by multiple profiles without providing each profile access to data like &amp;#39;Live Positions&amp;#39; &amp;amp; &amp;#39;Home Bases&amp;#39; to be in line with GDPR &amp;amp; privacy regulations on national &amp;amp; regional level. &lt;br&gt;&lt;br&gt;&lt;u&gt;Use Case &amp;amp; Solution&lt;/u&gt;&lt;br&gt;1. Create a setting to allow only certain profiles to have access to the Map Tab in general on the dispatcher console&lt;br&gt;2. Create a setting to allow only certain profiles to switch on / switch off the layers on the Map Tab &amp;#39;FSL__Map_Object_Markers__c. That way, access to data can be controlled &amp;amp; prevented.
					
				</description>
			</item>
	</channel>
</rss>