{"id":2449,"date":"2024-05-27T17:22:29","date_gmt":"2024-05-27T17:22:29","guid":{"rendered":"\/agile\/?post_type=ht_kb&#038;p=2449"},"modified":"2024-08-08T20:42:56","modified_gmt":"2024-08-08T20:42:56","slug":"publishing-schedules","status":"publish","type":"ht_kb","link":"\/agile\/knowledge-base\/publishing-schedules\/","title":{"rendered":"Employee Schedules \u2013 Publishing Schedules"},"content":{"rendered":"\n<ul class=\"wp-block-list\">\n<li>The publish schedules function is used along with the Employee Self Service module<\/li>\n\n\n\n<li>Employees can look up their schedules by logging in to their Employee Self Service website<\/li>\n\n\n\n<li>When you create schedules, they will be in unpublished status by default, this means that employees will not be able to view their schedule yet<\/li>\n\n\n\n<li>Once you click the publish button, all schedules showing on the screen will be put in published status and show in green<\/li>\n\n\n\n<li>They can now be viewed by employees<\/li>\n<\/ul>\n\n\n\n<p>Once user publishes the schedule, it will be visible to employees through the employee self-service function.<\/p>\n\n\n\n<p><strong>How to publish schedule:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Select the&nbsp;<strong>Schedules<\/strong>&nbsp;from the side menu.<\/li>\n\n\n\n<li>Select&nbsp;<strong>employees<\/strong> <strong>and<\/strong> <strong>specify<\/strong> <strong>date range<\/strong> user wish to publish the schedule for, from the employee selector.<\/li>\n\n\n\n<li>Click on the&nbsp;<strong>Actions<\/strong>&nbsp;button appearing on top-right corner.<\/li>\n\n\n\n<li>Click on&nbsp;<strong>Publish<\/strong><\/li>\n\n\n\n<li>User will see the &#8220;Publish Schedule&#8221; confirmation dialog.<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"1919\" height=\"925\" src=\"\/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9.png\" alt=\"A screenshot of a computer\n\nDescription automatically generated\" class=\"wp-image-2450\" srcset=\"\/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9.png 1919w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-300x145.png 300w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-1024x494.png 1024w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-768x370.png 768w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-50x24.png 50w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-1536x740.png 1536w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-60x29.png 60w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-9-100x48.png 100w\" sizes=\"auto, (max-width: 1919px) 100vw, 1919px\" \/><\/figure>\n\n\n\n<p>Once user confirms the publish schedule, it will show the progress bar at the bottom with&nbsp;<strong>undo action timer<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\n<ol class=\"wp-block-list\">\n<li>If user clicks on undo, it will not publish the schedule and show the bottom timer as &#8220;action undone&#8221;.<\/li>\n\n\n\n<li>If user does not click on undo, send the request publish to API, show the successful toast message, and update the grid with published background.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"1919\" height=\"929\" src=\"\/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10.png\" alt=\"A screenshot of a computer\n\nDescription automatically generated\" class=\"wp-image-2452\" srcset=\"\/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10.png 1919w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-300x145.png 300w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-1024x496.png 1024w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-768x372.png 768w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-50x24.png 50w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-1536x744.png 1536w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-60x29.png 60w, \/agile\/wp-content\/uploads\/sites\/2\/2024\/05\/a-screenshot-of-a-computer-description-automatica-10-100x48.png 100w\" sizes=\"auto, (max-width: 1919px) 100vw, 1919px\" \/><\/figure>\n\n\n\n<p><strong>POINTS TO REMEMBER<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>&#8216;Publish&#8217; button will be disabled if schedule is:\n<ul class=\"wp-block-list\">\n<li>in the past date.<\/li>\n\n\n\n<li>already published.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>&#8216;Publish&#8217; button becomes active and visible when:\n<ul class=\"wp-block-list\">\n<li>in system settings, PublishSchedule.RestrictViewEnabled is set to Yes.<\/li>\n\n\n\n<li>Shift Schedule &#8211; edit permission is available.<\/li>\n\n\n\n<li>Schedule is in the future date and unpublished.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>&#8220;Publish Schedule&#8221; confirmation dialog:\n<ul class=\"wp-block-list\">\n<li>Confirmation dialog will show the message as &#8220;Are you sure you want to publish this schedule to {n} employees for all days up to {week&#8217;s end date}?&#8221; if <strong>AppEvents.ScheduleChange.NotificationEnabled<\/strong> is set to <strong>No<\/strong> in System settings.<\/li>\n\n\n\n<li>Confirmation dialog will show the message as &#8220;Are you sure you want to publish this schedule to {n} employees for all days up to {week&#8217;s end date}? This action will send an SMS\/email to all published employees. if <strong>AppEvents.ScheduleChange.NotificationEnabled<\/strong> is set to <strong>Yes <\/strong>in System settings.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>If the schedules are already published and user is making any subsequent changes to the schedule,\n<ul class=\"wp-block-list\">\n<li>User will see the confirmation dialog \u201cYou are changing one or more schedules that will result in a notification being sent to {employee name}, do you want to proceed?&#8221; if System setting <strong>AppEvents.ScheduleChange.NotificationEnabled<\/strong> is set to <strong>Yes<\/strong>.<\/li>\n\n\n\n<li>If System setting <strong>AppEvents.ScheduleChange.NotificationEnabled<\/strong> is set to <strong>No<\/strong>, user will not see any confirmation dialog, it will update the schedule and show the success toast message.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Required permission:<\/strong>&nbsp;ShiftSchedule-Edit<br><strong>Required System settings:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PublishSchedule.RestrictViewEnabled &gt; to make the \u201cPublish\u201d option active and visible.<\/li>\n\n\n\n<li>AppEvents.ScheduleChange.NotificationEnabled &gt; for notification confirmation dialog<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Once user publishes the schedule, it will be visible to employees through the employee self-service function. How to publish schedule: Once user confirms the publish schedule, it will show the progress bar at the bottom with&nbsp;undo action timer: POINTS TO REMEMBER Required permission:&nbsp;ShiftSchedule-EditRequired System settings:<\/p>\n","protected":false},"author":3,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"ht-kb-category":[106],"ht-kb-tag":[],"class_list":["post-2449","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-bolt-scheduler"],"_links":{"self":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/2449","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/comments?post=2449"}],"version-history":[{"count":2,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/2449\/revisions"}],"predecessor-version":[{"id":2882,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/2449\/revisions\/2882"}],"wp:attachment":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/media?parent=2449"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-category?post=2449"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-tag?post=2449"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}