Bug 1322100 - Missing documentation on how to change user task form styles globally in jBPM 6.2
Summary: Missing documentation on how to change user task form styles globally in jBPM...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Documentation
Version: 6.2.0
Hardware: x86_64
OS: Windows
unspecified
high
Target Milestone: ---
: ---
Assignee: Dawn Eisner
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 19:42 UTC by brandon.buteau
Modified: 2020-03-27 19:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:44:47 UTC
Type: Bug


Attachments (Terms of Use)

Description brandon.buteau 2016-03-29 19:42:57 UTC
Description of problem:

Unable to figure out how to change user task (or process) form styles globally. The documentation only mentions plugging in CSS styles for individual fields (labels or content). (Even then, the documentation does explain where the CSS definitions must be deployed to be accessible from the forms.) But I'd rather not have to set CSS for each field individually if I can change them all globally to a common style. And no method is identified for changing overall form style properties (e.g., background-color). How can this best be accomplished? I'd prefer to do it separately for each project, but if I have to do it overall for all user task and process forms, that would be acceptable. The user documentation does not cover how to do this.

Version-Release number of selected component (if applicable):

6.2.0


How reproducible:

Trivial


Steps to Reproduce:

1. Read sections 4.7 and 4.8, both dealing with forms, from the 6.2 User Guide. 

Actual results:

There is no mention of providing styles for the form as a whole. Section 4.8.9 identifies where to enter label and style CSS class (or direct CSS) for individual fields. But it does not explain where CSS style definitions need to be deployed in order to be usable by forms (e.g., if I supply a CSS class name, where does the definition go?), nor does it identify where global or default style changes may be made.

Expected results:

There should be some explanation of how to deploy CSS styles and how to change default form styles globally (including form-level properties like background-color).

Additional info:


Note You need to log in before you can comment on or make changes to this bug.