Greetings,

We are using Client Side Human Services to display forms like UI having 50 fields. If we see it from Usability perspective then its not good as the number of fields are quite large. 
is it possible to do some kind of Paging on the Coach View so the fields can be displayed on multiple pages of coach and there would be next/previous button to navigate between the pages. 

What the recommendations around CSHS when there are large number of fields.

Thanks

------------------------------
Lakshya Agarwal
------------------------------

Hi

You have a number of options.

The simplest is the put multiple "Coaches" into your CSHS and wire them together:
I have added buttons to each coach, The CSHS editor allows you to simply wire the buttons to each coach.

Another option would be to use "views" to split up a single coach. For example the "tab section" view allows for multiple layout views to be displayed as a series of tabs. For example this tab section has three "Panel" views:

Other layout controls such as "Collapsable Panels" and "Stacks" can also be used.

I hope that helps.

Mark

------------------------------
Mark Ketteman
Digital Business Solutions Engineer
IBM United Kingdom Limited
London
------------------------------

Original Message:
Sent: Fri July 02, 2021 05:14 AM
From: Lakshya Agarwal
Subject: How to handle large number of fields in CSHS

Greetings,

We are using Client Side Human Services to display forms like UI having 50 fields. If we see it from Usability perspective then its not good as the number of fields are quite large. 
is it possible to do some kind of Paging on the Coach View so the fields can be displayed on multiple pages of coach and there would be next/previous button to navigate between the pages. 

What the recommendations around CSHS when there are large number of fields.

Thanks

------------------------------
Lakshya Agarwal
------------------------------

Hello! There are several ways of approaching this in the CSHS and its page(s).

There are layout controls that allow you to paginate a CSHS page into things like tabs, sections, panels, etc. This is more of a visual approach and all of the fields are still being handled on a single page.

The other approach is to leverage the power of the CSHS and its page flow capability, You were probably wondering why a CSHS looks like a little process map when you first open it. This is because you can actually create a flow of pages and add logic between them to do things like preload data from service calls before displaying it on one or more CSHS pages. You can also control the flow between the pages you add by adding buttons to the pages and using the boundary events to select which route to take when each button is clicked. You do this by selecting an outgoing flow line and telling it which button it is associated with.

------------------------------
DAVE PERMAN
------------------------------

Original Message:
Sent: Fri July 02, 2021 05:14 AM
From: Lakshya Agarwal
Subject: How to handle large number of fields in CSHS

Greetings,

We are using Client Side Human Services to display forms like UI having 50 fields. If we see it from Usability perspective then its not good as the number of fields are quite large. 
is it possible to do some kind of Paging on the Coach View so the fields can be displayed on multiple pages of coach and there would be next/previous button to navigate between the pages. 

What the recommendations around CSHS when there are large number of fields.

Thanks

------------------------------
Lakshya Agarwal
------------------------------

I recommend you use a Deferred Section. Other than the small HTML footprint of uninstantiated views, your CSHS Coach will incur none of the load overhead for the deferred views until the Deferred Section is lazy-loaded (through the lazyLoad method of the view).

You can combine this with the other suggestion to use a tab section for example so that your Coach isn't cluttered and is incrementally loaded only if and when you open a specific tab  (by combining the "on tab changed" tab section event with the lazyLoad method of the Deferred Section).

------------------------------
Eric Ducos
------------------------------

Original Message:
Sent: Fri July 02, 2021 05:14 AM
From: Lakshya Agarwal
Subject: How to handle large number of fields in CSHS

Greetings,

We are using Client Side Human Services to display forms like UI having 50 fields. If we see it from Usability perspective then its not good as the number of fields are quite large. 
is it possible to do some kind of Paging on the Coach View so the fields can be displayed on multiple pages of coach and there would be next/previous button to navigate between the pages. 

What the recommendations around CSHS when there are large number of fields.

Thanks

------------------------------
Lakshya Agarwal
------------------------------

Hi @Mark Ketteman @DAVE PERMAN @Eric Ducos, Many thanks for your response.

I have add a new View (Case Page Layout > Add Case) for Add Case in BPM Coaches. By default "Add Case" View is created and works fine.
Now I would like to put these fields in 2 pages for which I have created another coach view and connected with the click of a Next button. On this new coach view, I have added the "Case properties widget" and through the variables section added the remaining properties.

While navigating to this coach view, the properties are not getting displayed and getting the exception in browser debugger. What else is needed to make this work like this ?
I am using this coach view URL (outside of Case Client)
Please suggest





------------------------------
Lakshya Agarwal
------------------------------

Original Message:
Sent: Fri July 02, 2021 05:14 AM
From: Lakshya Agarwal
Subject: How to handle large number of fields in CSHS

Greetings,

We are using Client Side Human Services to display forms like UI having 50 fields. If we see it from Usability perspective then its not good as the number of fields are quite large. 
is it possible to do some kind of Paging on the Coach View so the fields can be displayed on multiple pages of coach and there would be next/previous button to navigate between the pages. 

What the recommendations around CSHS when there are large number of fields.

Thanks

------------------------------
Lakshya Agarwal
------------------------------
​​​

I get the same issue if I add 2 Case Properties Widget on the same coach.

Please suggest how these can be addressed

------------------------------
Lakshya Agarwal
------------------------------

Original Message:
Sent: Mon July 12, 2021 01:17 AM
From: Lakshya Agarwal
Subject: How to handle large number of fields in CSHS

Hi All, Many thanks for your response.

I have add a new View (Case Page Layout > Add Case) for Add Case in BPM Coaches. By default "Add Case" View is created and works fine.
Now I would like to put these fields in 2 pages for which I have created another coach view and connected with the click of a Next button. On this new coach view, I have added the "Case properties widget" and through the variables section added the remaining properties.

While navigating to this coach view, the properties are not getting displayed and getting the exception in browser debugger. What else is needed to make this work like this ?
I am using this coach view URL (outside of Case Client)
Please suggest





------------------------------
Lakshya Agarwal

Original Message:
Sent: Fri July 02, 2021 05:14 AM
From: Lakshya Agarwal
Subject: How to handle large number of fields in CSHS

Greetings,

We are using Client Side Human Services to display forms like UI having 50 fields. If we see it from Usability perspective then its not good as the number of fields are quite large. 
is it possible to do some kind of Paging on the Coach View so the fields can be displayed on multiple pages of coach and there would be next/previous button to navigate between the pages. 

What the recommendations around CSHS when there are large number of fields.

Thanks

------------------------------
Lakshya Agarwal
------------------------------