Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Hi Nakul,

Can you check if the template Coach View has any global CSS that overrides default styles of the radio button.

Such CSS can affect all radio buttons in the Process App once the toolkit is imported.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Nakul,

Also check the Theme that is set in the project properties for the toolkit and the process app.  When viewing the toolkit in isolation, the theme set on the toolkit is used.  However, when a toolkit is referenced by a process app, then the theme set on the process app will be applied to all dependent toolkits.  The result is that the theme set on a toolkit is never used at runtime, and only exists as a default to use when the toolkit is opened for editing in isolation.

Hope this helps,

Grant.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Hi,

Another alternative approach is to check the running version of your screen (Run Workflow & Check Task Screen) Or Run Human Service Separate & then open browser inspect and select html element to check customized css applied over your element below is an example and you should check below also 

01) Selected Theme Over Process App / Toolkit ( Also Customized CSS If Your Theme Less File)

02) Check Inline-CSS Applied Over Used Coach Views / Views Added In Your Human Service.

03) Check Your Control is Custom CSS added ( Check Also If Javascript Code Applied )

04) Check OnLoad Events as there code be some lines to customize control behavior / styling

05) Check Browser Inspect Option to check what is reflecting your control styling as there could be changes applied to common css classes like "form-group" , "control-label" which could change styling of majority of IBM BPM Controls.

Nakul,

Also check the Theme that is set in the project properties for the toolkit and the process app.  When viewing the toolkit in isolation, the theme set on the toolkit is used.  However, when a toolkit is referenced by a process app, then the theme set on the process app will be applied to all dependent toolkits.  The result is that the theme set on a toolkit is never used at runtime, and only exists as a default to use when the toolkit is opened for editing in isolation.

Hope this helps,

Grant.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Nakul,

Also check the Theme that is set in the project properties for the toolkit and the process app.  When viewing the toolkit in isolation, the theme set on the toolkit is used.  However, when a toolkit is referenced by a process app, then the theme set on the process app will be applied to all dependent toolkits.  The result is that the theme set on a toolkit is never used at runtime, and only exists as a default to use when the toolkit is opened for editing in isolation.

Hope this helps,

Grant.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Hi Grant,

This is great insight. I will see if I can modify theme set from process app itself. However, it still comes from another toolkit. Maybe a quick workaround through coach properties can sort out something.

Thanks for your response.

Nakul,

Also check the Theme that is set in the project properties for the toolkit and the process app.  When viewing the toolkit in isolation, the theme set on the toolkit is used.  However, when a toolkit is referenced by a process app, then the theme set on the process app will be applied to all dependent toolkits.  The result is that the theme set on a toolkit is never used at runtime, and only exists as a default to use when the toolkit is opened for editing in isolation.

Hope this helps,

Grant.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.

Hello, 

There is a toolkit which has a template coach view. This toolkit is imported in Process App. The radio buttons before importing this tempate coach view, looks as usual. After importing template coach view, radio buttons change their look and feel. Where possibly I should look for a bug? Has anyone faced such issue earlier?

Thanks.