Bug 724288 (BRMS-233) - out of date screenshots in BRMS Userguide
Summary: out of date screenshots in BRMS Userguide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-233
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.0.2
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks: BRMS-285 SOA-285
TreeView+ depends on / blocked
 
Reported: 2009-10-02 15:14 UTC by Jaroslaw Kijanowski
Modified: 2010-09-03 14:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-03 14:20:00 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-233 0 None None None Never

Description Jaroslaw Kijanowski 2009-10-02 15:14:58 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2010-04-09 01:05:34
securitylevel_name: Public

This is left from BRMS-219

page 25:
feature areas mentioned below figure 4.1 not in sync with this figure 

page 51:
There are also many third-party WebDav clients are available for most platforms.
double 'are'

figure 4.6, 4.7, 4.8, 4.9, 4.10, 4.17, 4.18, 4.23 from old jbrms

Comment 1 Dana Mison 2010-02-09 03:55:04 UTC
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]


Comment 2 Len DiMaggio 2010-04-05 17:27:47 UTC
Link: Added: This issue is a dependency of SOA-285


Comment 3 Dana Mison 2010-04-09 05:05:34 UTC
Figure 4.1 and the "feature areas" text has been updated.

Comment 4 Len DiMaggio 2010-04-16 14:44:34 UTC
Link: Added: This issue is a dependency of BRMS-285


Comment 5 Dana Mison 2010-04-19 05:26:09 UTC
double "are" fixed.  The first couple of screenshots have been fixed up.   Will need assistance for the remaining ones 

Comment 8 Dana Mison 2010-05-05 04:54:29 UTC
Thanks to Jaroslaw for his help with the more complicated ones.

These have all been updated.


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