Bug 1198509

Summary:	Configurable Workbench: Differences in parameter inputs
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Tomas David <tdavid>
Component:	Business Central	Assignee:	Alexandre Porcelli <porcelli>
Status:	CLOSED EOL	QA Contact:	Tomas David <tdavid>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	kverlaen, manstis, porcelli, tdavid
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 19:10:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas David 2015-03-04 10:03:37 UTC

Description of problem:
Parameters have different inputs. For exaple SplashScreen plugin: "Title" has to be between quotation marks, "body_height" is integer number, "interception_points" parameter has to be between square brackets and quotation marks. This has to be documented, some hint should be displayed, format must be identical or special inputs should be created.

Single error in parameters can cause that splashscreen is not displayed.

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

How reproducible:
-

Steps to Reproduce:
-

Actual results:
-

Expected results:
-

Additional info:
-

Comment 1 manstis 2015-03-04 10:23:43 UTC

Where/how are you modifying these parameters?

I assume you're modifying a "static" splash screen definition (i.e. the JavaScript file in the WAR)? You are correct - the data-type of these fields should be documented! If you're using the UI (in some way not obvious) please advise too - as we'd need to improve that as well.

Comment 2 Tomas David 2015-03-04 10:49:38 UTC

I use both types. If it is documented it will be probably ok.

Do you plan some validator for js plugins (or parameters)? As I said one error in code can cause that plugin is not displayed. I think for static plugin is ok because user use own tool or some text editor but for dynamic plugins some validation will be helpfull.

Comment 3 Tomas David 2015-09-24 06:44:09 UTC

*** Bug 1263967 has been marked as a duplicate of this bug. ***

Comment 4 Red Hat Bugzilla 2023-09-14 02:55:33 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days