Bug 1019842

Summary: XLS decision table uploaded to business central cannot be opened
Product: [Retired] JBoss BRMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: manstis
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: etirelli, rrajasek, trikkola, vigoyal
Target Milestone: ER5Keywords: Reopened
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Summary: In Business Central a user can not open an uploaded Decision table which is created in a XLS file. There is neither an error message displayed during or after the upload, nor an exception shown in the problem window. This is a known issue and currently there is no workaround for it. Cause: Consequence: Fix: Result:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:19:31 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:
Bug Depends On:    
Bug Blocks: 999885    
Attachments:
Description Flags
model JAR
none
xls decision table none

Description Radovan Synek 2013-10-16 13:33:54 UTC
Created attachment 812930 [details]
model JAR

Description of problem:
Decision table created from uploaded XLS file cannot be opened. Problem window is empty, as well as server log, no message appears.

Version-Release number of selected component (if applicable):
BRMS-6.0.0.ER4


Steps to Reproduce:
1. Create some project.
2. Upload attached JAR with model.
3. Add the jar as a dependency to the project.
4. Create new decision table (spreadsheet) and upload the .xls file in the attachment.
5. Try to open this decision table in Project Explorer. 
=> nothing happens

Comment 1 Radovan Synek 2013-10-16 13:34:17 UTC
Created attachment 812931 [details]
xls decision table

Comment 2 Toni Rikkola 2013-10-17 09:07:48 UTC

*** This bug has been marked as a duplicate of bug 1005707 ***

Comment 4 Radovan Synek 2013-12-02 11:27:43 UTC
Verified on BRMS-6.0.0.ER5