Taskspace Form Tab design

We are trying to create a case management system using xCP. There are different types of cases that this system needs to handle. And each type of case will need different data to be collected. So I am thinking of creating a Forms Builder form with 2 tabs (using tab component). The case type will be a drop down field on the first tab and once the user selects the case type, the second tab would need to change based on the case type. Here are a couple of options that I can think of, to implement the tabs -

1) Create separate tabs for each case type and only show the tab based on case type selected. All others will be hidden. The tab visibility would change at runtime.

2) Create one tab with text and fields for all case types. Only show the text and fields relevent to the selected case type.

Are the above options even possible? What is the best solution for this situation?

Find more posts tagged with

Comments

DCTM_Guru

Tabs is visibility is "controlled" by the role. So if you wanted to limit your 3 tabs visibility, you have 6 different permutations to account for a role (which can get messy).

Typically a case "type" is associated with custom folder type. You can create different electronic forms and/or folder information views based on type. This is NOT tied to a tab and therefore, not tied to a role.

jsabh

Thanks for your reply Johnny. The tabs I am talking about are not the taskspace tab, but rather the Form builder Tab control tabs.

You mentioned that the case type is associated with a custom folder type. That may be the only way to do it. I could create forms for each folder with the appropriate tabs. The drawback is that the user would not be able to change the tabs on the fly. A user will first need to select the type of case, then the system will need to create a custom folder, and then the user would need to open the folder and update the information. If the user selects the wrong type of case initially, the folder will need to be discarded.

If possible, we would want to setup the system such that the case type is changeable on the fly.

DCTM_Guru

If you are familiar with Webtop, the data model assumes you select the correct type to begin with. You cant change the object model (on the fly) via normal UI.

That being said, to get around this scenario, you can create generic form object (and use form tabs if you like) and then have it sent through a workflow to create correct custom folder instance and map the fields from your generic form object to the fields associated with the folder type.

manikhambire

Hi,

I think your second option will be good.

In First tab on the form, create one drop down which will lists your all case types.

On second tab create all the possible controls & apply rules for visibility from properties pane in Forms builder.

So you can control which fields will be shown for particular case type.

jsabh

Thanks folks, I am thinking of using the first option - because then I need to set one rule per tab. If I use the second option, I will need to set the rules on many controls per case type. So say if I have 20 controls for each case type and I have 20 case types, I will need to set 400 rules. Using option 1, I will need to set 20 rules. Option 1 will also be easier to maintain. Hopefully, there will not be a performance problem in having 20+ tabs.

DCTM_Guru

I would be concerned more about whether your controls have any adaptors associated with them. If you have one control that has an adaptor associated with it and it is repeated across 20+ tabs, then I think the adaptor will fire off 20 times regardless of whether the tab is visible or not.