In the built-in editing form of WebScheduler, the WebCombo control that is used to show the list of Categories is called wcCategories. This wcCategories is made from an unbound WebCombo with multiple selection feature enabled.

In order to prevent users from selecting multiple categories on the wcCategories control is simply by disabling the multiple-selection feature in the MultipleSelectionSettings as shown in the following snippet code.

<ISWebCombo:WebCombo ID="wcCategories" runat="server" ...>
    ...
    <MultipleSelectionSettings Enabled="False" />
</ISWebCombo:WebCombo>

However, there is a layout problem in IE 8 browser when the multiple-selection is disabled.

I have reported this layout issue to our WebScheduler development team. Should I hear any news about the status of this issue, I’m surely will let you know.

I just got news from WebScheduler development team regarding the layout issue. Currently the team has managed to fix the issue. I have checked the nightly-build hotfix and found that the layout issue is no longer occurring.

So, the solution to your scenario, to prevent users from selecting multiple categories on the wcCategories, should be by disabling the multiple-selection feature of WebCombo.

<ISWebCombo:WebCombo ID="wcCategories" runat="server" ...>
    ...
    <MultipleSelectionSettings Enabled="False" />
</ISWebCombo:WebCombo>

Should you need to test the nightly-build of the hotfix, please let us know.

Thanks. When will the official hotfix be available to everyone?

We have released the official hotfix of WebScheduler, version 3.0.1000.8 on Tuesday, November 16, 2010. It is recommended to update the hotfix using Intersoft Update Manager.

For more detail information regarding the list of issues that is fixed in this build version, please check http://www.intersoftpt.com/Support/WebScheduler/VersionHistory/.

Hope this helps.

Ok this worked. However now that the Categories combo multi select is disabled on the editing form how do I remove "Categorize" from the scheduler context menu as it allows the user to multi select the categories? I would like the Edit and Delete context menu items to remain.

Thanks.

I just did some testing with the MultipleSelectionSettings disabled as you described above and here is what I found:

1. If you don't remove the SeparatorChar property from the wcCategories webcombo then everytime you save the edit form the CategoryID field will append the separator character to the CategoryID and will continue each time you save. (3,,,,,,). When I removed the SeparatorChar property it works fine.
2. After you disable the MultipleSelectionSettings on the wcCategories webcombo the CategoryID is no longer saved to the RecurringEvents table when you edit an existing recurring event or when you create a new recurring event. I have attached a sample of this issue.

Please let me know how to fix #2.

Thanks,

Tim

Ok this worked. However now that the Categories combo multi select is disabled on the editing form how do I remove "Categorize" from the scheduler context menu as it allows the user to multi select the categories? I would like the Edit and Delete context menu items to remain.

Thanks.

In order to remove the “Categorize” from the WebScheduler context menu it is suggested to utilize the OnContextMenu client-side event. The OnContextMenu client-side event gets or sets the event handler when the context menu is about to be displayed.

<script type="text/javascript">
	<!--
    function WebScheduler1_OnContextMenu(controlId, type, menuObj, el, eventView) {
        var WebScheduler1 = ISGetObject(controlId);

        if (type == "Event" || type == "AllDayEvent" || type == "TimelineEvent") {
            menuObj.Items.GetNamedItem("mnuSeparator").Hide();
            menuObj.Items.GetNamedItem("mnuCategorize").Hide();
        }

        return true;
    }
	-->
</script>

As shown in the above snippet code, WebScheduler will hide “mnuSeparator” object (as the separator of context menu) and “mnuCategorize” object (as the “Category” menu of WebScheduler context menu) if user click on object that has “Event” type or “AllDayEvent” type or “TimelineEvent” type.

I just did some testing with the MultipleSelectionSettings disabled as you described above and here is what I found:

1. If you don't remove the SeparatorChar property from the wcCategories webcombo then everytime you save the edit form the CategoryID field will append the separator character to the CategoryID and will continue each time you save. (3,,,,,,). When I removed the SeparatorChar property it works fine.

...

Thank you for your valuable feedback. Yes, you are correct. We need to remove the “SeparatorChar” property as well in order to completely have the MultipleSelection feature over wcCategories WebCombo disabled.

I will have this finding applied to my previous post so that other community member won’t miss it.

2. After you disable the MultipleSelectionSettings on the wcCategories webcombo the CategoryID is no longer saved to the RecurringEvents table when you edit an existing recurring event or when you create a new recurring event. I have attached a sample of this issue.

Please let me know how to fix #2.

Thanks,

Tim

I have informed our WebScheduler development team regarding this issue for further investigation. Should I hear any news from them, I’ll let you know.

The code for hiding the categorize item in the context menu works great..Thanks.

Have you heard back about #2?

--Tim

Glad to hear that the JavaScript function that is used to hide the categorize item from the context-menu does help.

About #2, I haven’t heard any news from development team regarding this. I’ll update to this thread as soon as I have any news.

This issue is going to become critical path soon on my project. Is there any way to expedite this?

Thanks,

Tim

I just got news from dev team that they have managed to fix the issue. I have examined and tested the nightly-build of WebScheduler.NET 3.0 with a simple sample WebScheduler page and find that everything worked smoothly and the wcCategories WebCombo has been able to keep the CategoryID.

The hotfix will be released along with the schedule of our next release of regular hotfix. Should you need to have the nightly-build of WebScheduler, please let us know.

Thanks the nightly-build of WebScheduler fixed the CategoryID not saving issue.

Now however I have another issue with editing recurring events. If I create a new recurring event and edit one instance of the recurring event then the RecurringEvents table updates the existing recurring event row and adds ParentID to itself and adds exceptioninfo, exceptiondate and start and end time to the existing recurring event instead of creating a new row and adding ParentID and related info to the new row. Then once it does that if you close the scheduler and open it again the recurring event does not show up.

This only happens when you edit the single instance and do not RE-SELECT Category/CarePlan on the edit form. If you don't RE-SELECT the category/CarePlan then the edit form validation detects that the Category/CarePlan was not selected and displays error. Then after you get the validation error and you then select the Category/CarePlan Webcombo and save it saves but has the issue above.

If you select Category/CarePlan before you save then the validation code does not return error and everything saves like it should and a new recurringEvents row is created for the exception like it should.

Here is the edit form validation code below and I have attached a simple sample that uses the nightly-build of the webscheduler.

I’m currently checking your sent sample.
I’ll get back and update the latest result to you.

I have found what may cause the issue.

Please modify the WebScheduler_OnEditingFormSave function into the following.

//Begin Edit form validation
function WebScheduler1_OnEditingFormSave(controlId, action, eventView) {
    var s = ISGetObject(controlId);
    var editWindow = s.GetEditingFormWindow();
    var wcCategories = editWindow.ISGetObject("wcCategories");

    if (wcCategories.Value == "") {
        alert("You must select a Care Plan");
        return false;
    }

    return true;
}
//end edit form validation

We need to add return true; into this function in order to let the editing form’s default action to happen after the JavaScript has been executed.

Please let us hear your response whether this helps or not.

This solution did not fix the issue as I am getting the same results.

The issue has been forwarded to WebScheduler development team to be investigated further.

I’ll keep you updated with any news I heard from the team regarding this issue.

Any updates on this issue?

There is no update on this issue yet, but I have added a note to the dev team regarding this issue.
Should I heard any news regarding this issue from the dev team, I will directly let you know.

I am really needing this issue resolved soon. Is there anyway they can expedite this?

Thanks,

Tim

The nightly build hotfix of this issue is ready. I have tested the issue on my local end to ensure that the issue is no longer persisting. A message containing the link to download the nightly build hotfix has been sent to your registered email account. Please kindly check the inbox and download the hotfix.

After download the hotfix, please carefully follow the step-by-step listed in http://www.intersoftpt.com/Build/ApplyHotfix in order to manually apply the hotfix file to your development machine. After apply the hotfix to the dev machine, please don’t forget to apply the hotfix to your project as well.

The sent hotfix is a nightly build and was not tested for regression. We hope you can collaborate and test it in your project. Please let us know any feedback regarding the hotfix.

This fixed it. Thank you!

Glad to hear the good news.

Should you need further assistance or run into any problems regarding our controls, feel free to post it into our community site. We would be happy to assist you again.