Prev | Next |
Edit WebEA Model Connection settings
After you select the option to edit a Model Connection, the configuration options for that connection are displayed.
In the simplest case, the connection can be defined by only updating the 'Protocol', 'Server', 'Port' and 'Model Name/Alias' fields. A number of additional options are provided for configuring settings such as authentication, available functions and display options.
Connection Options
Item |
Description |
See also |
---|---|---|
Protocol |
Identifies the protocol to be used to connect to the Sparx Systems Pro Cloud Server. |
|
Server |
Identifies the fully qualified machine name or IP address of the server hosting the Pro Cloud Server. |
|
Port |
Defines the TCP Port used to connect to the Sparx Systems Cloud Service. This Port number must match one of the Ports that the Pro Cloud Server Windows Service is listening to or, in the case of an IIS setup, the IIS Port servicing this repository. |
|
Model Name/Alias |
Defines the name or alias of the model connection. This corresponds to the Database Manager's 'Alias' in the Pro Cloud Server Configuration Client or the 'Model Name' on the Enterprise Architect's 'Cloud Connection' screen. The value is case sensitive. |
|
Validate SSL Certificates |
Defines whether self signed SSL certificates can be used. If you are using HTTPS and a self signed certificate, then this should be set to 'No'. Note: This option is only applicable when the Protocol is set to HTTPS. |
|
OSLC Access Code |
When configuring a Pro Cloud Server model connection / database manager an optional 'OSLC Access Code' can be defined. If the model connection has an 'OSLC Access Code' assigned then it will need to be entered in this field to allow WebEA access. |
Configure Database Manager |
Authentication Options
Item |
Description |
See also |
---|---|---|
Authentication Code |
Defines the authorization code all WebEA users must enter before they can access the model. If this value is blank, WebEA users are not prompted to enter a code. This option is only used for basic username/password authentication and is not used for Windows Authentication or OpenID. It is possible to set this option and also set a Model User. In this case the user will be required to enter the access code only and will not be prompted for a username or password. |
|
Model User |
Defines the model user login (as defined in Enterprise Architect User Security) that will be used in combination with the 'User Password' option to log in to a security-enabled model.
|
|
User Password |
Defines the password (as defined in Enterprise Architect User Security) that will be used in combination with the 'Model User' option to login to a security enabled model.
|
|
Allow blank passwords |
Defines whether or not WebEA will attempt to send blank passwords to the Pro Cloud Server for validation. |
|
Automatic Windows Login |
When set to Yes, WebEA will automatically attempt to login using Windows ID (bypassing the 'Login' screen). If the Windows login fails then the 'Login' screen will be displayed, allowing the user to manually enter credentials. Note: This option only applies if the model has the user security 'Accept Windows Authentication' option enabled. See the 'Maintain Users' help topic for details. |
Configure Model Users |
General Options
Item |
Description |
See also |
---|---|---|
Default Package Layout |
Defines the default layout when viewing the contents of a Package (or an element with children) in WebEA's main view. WebEA can display child items in one of three layouts, either Icon view (the default), List view, or Notes view (resembling the Enterprise Architect Specification Manager view). |
|
Object Order |
Defines the order of objects in the Browser and Object List views. There are three different ordering behaviors:
Note: Regardless of the 'Object Order' setting, WebEA displays diagrams, then Packages, then elements. The 'Object Order' applies to the items within each of these groupings. |
General Options WebEA - Browser WebEA Main View - Object List |
Favorites as Home |
When set to 'Yes', the WebEA 'Home' page will display the user's 'Favorites' Packages in the 'Browser' or 'Package' view. This is loaded when first accessing the model, and also when using WebEA's . Notes: When set to Yes, this overrides the 'default_diagram' setting Favorites are defined using Enterprise Architect; refer to the link in the See Also column for details If a user has no Favorites defined then the Model Root or Default diagram (if one is defined) will be loaded instead |
Refine Browser Content |
Default Diagram |
Defines the GUID of the diagram that should be automatically loaded when users log onto the model. The GUID of any diagram can be obtained from WebEA using the 'Obtain direct link to the current page' icon in the Navigation bar. If this option is not set then WebEA will load either:
Note: The entire GUID (including {}) must be used. |
User and Model Default Diagrams |
Mini Properties Navigates |
When set to 'Yes', selecting certain 'navigable' elements will cause WebEA to navigate to the target of these elements. Examples of such 'navigable' elements are Hyperlinks and Navigation Cells. For all other elements, selecting them will display the properties of the element in the Properties View. This option has no effect when the Properties View is not shown. |
|
Diagram Elements Navigate |
From WebEA version 3.01.23.1690 (in Pro Cloud Server 3.0.23) onwards, the default selection of some objects on diagrams matches Enterprise Architect's behavior. This applies to i) Composite elements and ii) Package elements that contain a diagram.
When 'Diagram Elements Navigate' is set to 'No', selecting either a Composite element or Package element on a diagram will display the selected element's properties. |
|
Recent Search Days |
Defines the number of days the predefined 'Recent ...' searches should consider. For example if this value was set to '7' then whenever a user invokes the search for 'Recent elements', all elements modified in the previous 7 days will be returned. |
|
Show Browser |
Defines the default visibility of the Browser. Notes:
|
Login WebEA - Browser |
Show Diagram Objects |
Select Yes to show diagram-only objects such as Notes, Text and Boundaries in the Browser. These objects are grouped in an collapsible [...] node. |
WebEA - Browser |
Show Properties View |
Defines the default visibility of the Properties View. Notes:
|
Login WebEA - Properties View |
Show Path Button |
Select 'Yes' to show the in the navbar. The Path button is used to display a list of all Packages/objects from the current object up to the model root. |
WebEA - Model View |
Show Breadcrumb |
Select Yes to show the full path to the current object in WebEA's navbar. When set to No, the navbar will display the current object name only. |
WebEA - Model View |
Collaboration Options
Item |
Description |
See also |
---|---|---|
Show Journal Entries |
Defines whether Journal entries are accessible in WebEA. When set to 'Yes', Journal entries will be accessible via the Discuss & Review - History window's 'Journals' tab. Journal entries will also be accessible via the Object Properties View, if the object has any Journal entries defined. |
|
Show Model Chat |
Defines whether Model Chat is accessible in WebEA. When set to 'Yes', Model Chat will be accessible via the Discuss & Review View's 'Chat' tab. Note: As with Enterprise Architect, Model Chat is not available in models which do not have user security enabled. |
|
Chat Notification Frequency |
Defines how frequently (in seconds) WebEA will check for new Chat messages and display/update the Chat Notification which appears in the WebEA status bar. By default this value is set to 30 (seconds). |
|
Show Model Mail |
Defines whether Model Mail is accessible in WebEA. When set to 'Yes', Model Mail will be accessible via the Collaboration View's 'Mail' tab. Note: As with Enterprise Architect, Model Mail is not available in models which do not have user security enabled. |
|
Mail Time Period |
Defines how many days worth of messages are displayed in the Model Mail Inbox and Sent Mail lists. By default this is set to 90 (days). Reducing this number can improve performance when loading the Inbox/Sent Mail. |
|
Show Discussions |
Defines whether Discussions are accessible in WebEA. When set to 'Yes', Discussions will be accessible via the Collaboration View's 'Reviews' and 'Discussions' tabs. Discussions and Reviews will also be accessible via the Main View - Object Properties, and the Properties View. |
|
Add Discussions |
Defines whether or not new discussions on Packages and elements can be added to the model. Note: This option is disabled when Show Discussions is set to 'No'. |
|
Participate in Reviews |
When set to 'Yes', users are able to Join discussion reviews. In order to make full use of this option the 'Show Discussions' and 'Add Discussions' options would also have to be set to 'Yes'. |
|
Use Avatars |
When set to 'Yes', all discussion and chat messages are displayed with the creating user's avatar. When set to 'No', a set of generic images representing discussions and replies is used instead. |
Object Update Options
Item |
Description |
See also |
---|---|---|
Can add Objects |
Defines whether or not new objects (elements, diagrams, or Packages) can be added to the model. |
|
Edit Object Notes |
Defines whether an object's notes can be edited. |
|
Can add <type> |
The remaining options in this section define whether or not elements of the given object type can be added to the model. Note: If the 'Can add Objects' option is set to 'No', then this overrides the individual 'Can add <type>' options. |
Object Feature Update Options
Item |
Description |
See also |
---|---|---|
Can add Object Features |
Defines whether or not element features (such as Changes and Tests) can be added to the model. |
|
Can edit Tests |
Defines whether or not the details of element tests can be edited in the model. |
|
Can edit Resources |
Defines whether or not the details of element resource allocations can be edited in the model. |
|
Can add <feature type> |
The remaining options in this section define whether or not specific feature types (such as Changes or Tests) can be added to elements in the model. Note: If the 'Can add Object Features' option is set to 'No', then this overrides the individual 'Can add <feature type>' options. |
Property Section Options
The Property Section Options define whether specific properties are available and/or visible when viewing the properties of an element in WebEA. By default, all property sections are set to be visible ('Yes').
Note: When viewing the Properties of an element in WebEA's Main View, the feature buttons to display specific properties are only displayed if the element has features or properties of that type.
For example, if an element has no Tagged Values, then the 'Tagged Values' feature button will not be displayed (regardless of Property Section Options).
Default Watchlist Options
Item |
Description |
See also |
---|---|---|
Days to Watch |
Defines the default activity period of the model watchlist. The value is a number of days; for example, look for activity in the last 10 days. |
|
Cookie Retention |
Defines the period over which a WebEA user's set of Watchlist options is stored. The value is the number of days that the cookies will be retained for. |
|
Recent Discussions |
Define whether or not the watchlist should display a count of elements that have had discussions during the activity period. |
|
Recent Reviews |
Define whether or not the watchlist should display a count of review elements that have been added or modified during the activity period. |
|
Recent Diagrams |
Define whether or not the watchlist should display a count of added/modified diagrams during the activity period. |
|
Recent Elements |
Define whether or not the watchlist should display a count of added/modified elements during the activity period. |
|
Active resource tasks |
Define whether or not the watchlist should display a count of elements with active resource allocations during the activity period. |
|
Ending resource tasks |
Define whether or not the watchlist should display a count of elements with resource allocations ending during the activity period. |
|
Overdue resource tasks |
Define whether or not the watchlist should display a count of elements with resource allocations that fall overdue during the activity period. |
|
Recently passed tests |
Define whether or not the watchlist should display a count of elements with tests that passed during the activity period. |
|
Recently failed tests |
Define whether or not the watchlist should display a count of elements with tests that failed during the activity period. |
|
Recently deferred tests |
Define whether or not the watchlist should display a count of elements with tests that were deferred during the activity period. |
|
Recent tests not checked |
Define whether or not the watchlist should display a count of elements with tests that were not checked during the activity period. |
|
Tests not run |
Define whether or not the watchlist should display a count of elements with tests that were not run during the activity period. |
|
Verified changes |
Define whether or not the watchlist should display a count of elements with verified changes during the activity period. |
|
Recently requested changes |
Define whether or not the watchlist should display a count of elements with requested changes during the activity period. |
|
Recently completed changes |
Define whether or not the watchlist should display a count of elements with changes completed during the activity period. |
|
New changes |
Define whether or not the watchlist should display a count of elements with new changes added during the activity period. |
|
Incomplete changes |
Define whether or not the watchlist should display a count of elements with incomplete changes during the activity period. |
|
High Priority events |
Define whether or not the watchlist should display a count of elements with events set to high during the activity period. |
|
Verified defects |
Define whether or not the watchlist should display a count of elements with verified defects during the activity period. |
|
Recently reported defects |
Define whether or not the watchlist should display a count of elements with defects reported or 'requested' during the activity period. |
|
Recently resolved defects |
Define whether or not the watchlist should display a count of elements with defects completed during the activity period. |
|
New defects |
Define whether or not the watchlist should display a count of elements with defects added during the activity period. |
|
Incomplete defects |
Define whether or not the watchlist should display a count of elements with incomplete defects during the activity period. |
|
Verified issues |
Define whether or not the watchlist should display a count of elements with verified issues during the activity period. |
|
Recently reported issues |
Define whether or not the watchlist should display a count of elements with issues reported or 'requested' during the activity period. |
|
Recently resolved issues |
Define whether or not the watchlist should display a count of elements with issues completed during the activity period. |
|
New issues |
Define whether or not the watchlist should display a count of elements with issues added during the activity period. |
|
Incomplete issues |
Define whether or not the watchlist should display a count of elements with incomplete issues during the activity period. |
|
Verified tasks |
Define whether or not the watchlist should display a count of elements with verified tasks during the activity period. |
|
Recently reported tasks |
Define whether or not the watchlist should display a count of elements with requested tasks during the activity period. |
|
Recently resolved tasks |
Define whether or not the watchlist should display a count of elements with tasks completed during the activity period. |
|
New tasks |
Define whether or not the watchlist should display a count of elements with tasks added during the activity period. |
|
Incomplete tasks |
Define whether or not the watchlist should display a count of elements with incomplete tasks during the activity period. |
|
Recently reported events |
Define whether or not the watchlist should display a count of elements with requested events during the activity period. |
|
Incomplete events |
Define whether or not the watchlist should display a count of elements with incomplete events. |
|
Verified decisions |
Define whether or not the watchlist should display a count of elements with verified decisions during the activity period. |
|
Recently reported decisions |
Define whether or not the watchlist should display a count of elements with requested decisions during the activity period. |
|
Recently resolved decisions |
Define whether or not the watchlist should display a count of elements with decisions resolved during the activity period. |
|
New decisions |
Define whether or not the watchlist should display a count of elements with decisions added during the activity period. |
|
Incomplete decisions |
Define whether or not the watchlist should display a count of elements with incomplete decisions during the activity period. |