Bug 1014428 - All editors should show title as EditorName: ResourceName and the resource file type should be removed
Summary: All editors should show title as EditorName: ResourceName and the resource fi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ER6
: 6.0.0
Assignee: manstis
QA Contact: Tomas David
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-02 01:34 UTC by Catherine Robson
Modified: 2014-08-06 20:20 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:20:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Catherine Robson 2013-10-02 01:34:27 UTC
Description of problem:
On the editor title bars (process designer, rule editor, form builder, etc), file names with extensions are currently shown.  This is not desirable for business users as the back-end file names are not relevant to their experience with the product.  To make the product feel more seamless and less complex, all titles should be changed to EditorName: ResourceName and any file extensions should be removed.

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

Comment 2 Mauricio Salatino 2013-10-02 08:58:12 UTC
I would suggest to have an icon for each type of resource, that will make it clear for every one to know that (Icon) + EditorName: ResourceName is from a certain type, avoiding the need of the file extension. Also it will be good to have an alias (or a friendly name for the resource) so you don't end up having in the editor the File name which is usually obfuscated

Comment 4 manstis 2013-10-04 10:35:26 UTC
We already hide the file extension (there was another BZ for this).

Jervis, I believe you have another BZ that might relate to this too.

Comment 5 manstis 2013-11-29 11:19:52 UTC
I checked and we appear to be removing the file extension already. Can you please confirm and advise whether any further action is required?

Comment 6 Tomas David 2014-01-16 11:09:56 UTC
Verified on BRMS 6.0.0.ER7.


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