Bug 797859 - Designer shows only Task node
Summary: Designer shows only Task node
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-27 11:32 UTC by Tomas Schlosser
Modified: 2012-04-02 13:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-28 07:30:56 UTC
Type: Bug


Attachments (Terms of Use)
Designer canvas (47.22 KB, image/png)
2012-02-27 11:32 UTC, Tomas Schlosser
no flags Details

Description Tomas Schlosser 2012-02-27 11:32:27 UTC
Created attachment 566016 [details]
Designer canvas

Description of problem:
When 

Version-Release number of selected component (if applicable):
BRMS-5.3.0-ER4 (standalone)

How reproducible:
Every time

Steps to Reproduce:
1. create a new process file
2. open Shape repository
  
Actual results:
Only "Task node" is present whatever perspective is selected

Expected results:
At the very least start and task events are needed to create a process

Additional info:

Comment 1 Tihomir Surdilovic 2012-02-27 14:28:56 UTC
Can you show a screenshot of this? In both the Full and Minimal perspectives the start event is present. If you have picked up a new Designer version for testing you should clear your browser cache before testing and let me know if this is still an issue.

Comment 2 Tihomir Surdilovic 2012-02-27 14:30:27 UTC
Sorry saw you did attach a screenshot. Definitely please clear your browser cache and reload the page. If this issue persists look at the Javascript console to see what error(s) you get and post them alongside your browser type and version.

Comment 3 Tomas Schlosser 2012-02-28 07:30:56 UTC
Yes, that was the problem. Cleaning the cache helped. Thank you Tiho.


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