Bug 1077332 - Unable to make a copy of a rule if the name of the copy contains spaces
Summary: Unable to make a copy of a rule if the name of the copy contains spaces
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ER1
: 6.0.2
Assignee: manstis
QA Contact: Lukáš Petrovický
Dawn Eisner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-17 18:30 UTC by Amana
Modified: 2020-03-27 20:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:04:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1067369 0 high CLOSED Copy, Rename: File name validation broken 2021-02-22 00:41:40 UTC

Internal Links: 1067369

Description Amana 2014-03-17 18:30:11 UTC
Description of problem:

Cannot make a copy of any rule type if the name of the copy contains spaces. The following error is showed in a popup after clicking on "Create Copy" button.

Unable to complete your request. The following exception occurred: Illegal character in path at index 105: default://master@Mortgages/MortgageApplication/src/main/resources/com/redhat/bpms/examples/mortgage/Jumbo Mortgage Test.rdrl.


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

BRMS/BPM 6 GA


How reproducible:

Always


Steps to Reproduce:
1. Open a rule (i.e. Jumbo Mortgage) and click on "copy" button;
2. In "New Name" fill out using a name with spaces (i.e. New Jumbo Mortgage);
3. Click on "Create Copy".


Actual results:

You will see the error "Unable to complete your request ..."


Expected results:

The rule should be created successfully.


Additional info:

Workaround: Once the copy is made with a name without spaces, you can rename the new rule to have a name with spaces.

Comment 2 Pavel Kralik 2014-04-29 14:29:38 UTC
Verified with bpms-6.0.2.ER2 and EAP6x.


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