![]() ![]() A simple loop is then added to create an object for mapping the Service Resource ids to their related Operating Hours ids. The Operating Hours Id field needs to be added to the SOQL query. You’ll make some small changes to the original On Resources Fetched action. Since DayBack is already querying Service Resources and Service Territories on start-up in the On Resources Fetched action that was set up in the first article, it makes sense to add the Operating Hours data that’s needed to that query and then write that data to a settings object in DayBack that can be retrieved in the new Custom App Action. The new App Action will need to associate a Service Resource with its related Operating Hours record. Add the virtual unavailable events to the existing unavailable calendar source and render them.Calculate those results as unavailability and create virtual DayBack events.Calculate if the results match resources and days in the current view.Query operating hours and time slots in Salesforce.To accomplish this, a Custom App Action will be needed to do the following: Time Slots also represent availability, so we’ll calculate the inverse so DayBack can display Time Slots as unavailable. Unlike Resource Absences, which have specific dates and times, Operating Hours and Time Slots are more like rules that will need to be translated to specific dates and times. Resource Absence blocks out time from 11:00 am until 2:00 pm for LA Exam Room 2 on Tuesday Setting up Operating Hours and Time Slots ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |