Skip to main content

Walk-up experience - some appointment slots disappearing

We eventually discovered this:

"This issue is happening because you have a 24/7 schedule with a 0.5 appointment window, which creates a lot of available appointment slots. 
However, there is an appointment booking property [sys_properties] called 'sn_apptmnt_booking.max_appointments_returned' which limits the number of appointment slots available. The property has a default value of 100. This explains why the location queue is limiting the available slots in the schedule. 

The workaround is to simply increase the value of sys_property 'sn_apptmnt_booking.max_appointments_returned'. 
Something like 1000 should do the trick


Popular posts from this blog

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue'" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object