| Release Notes (Printable version) |
| Administration |
| Web Server |
| |
|
Control of the data backup process is now fully available from the web interface.
Configurable parameters include:
* Backup state (active/inactive)
* Primary directory path
* Alternate directory path
* Interval between backups (in HH:MM)
In addition, you can force a backup to take place on the next pass of the scheduler. |
|
|
The settings used by the web servers session management engine can be configured from the Administration web page. The expiration timeout settings can be specified for:
* Anonymous users
* Logged-in users
* SrcMgr Explorer palette users
These values determine how long before inactive user sessions are automatically logged out of the web server. |
|
|
| Contents of the "Contact Us" page can now be set from the Variables section in 4D Client. Pure HTML must be pasted in. |
|
|
The data file can be marked for reference as:
* Production data
* Sample data
* Testing data
When non-production data file is used, a warning message will be presented at the top of every page on the web server so that users cannot be confused and mistakenly enter data into the wrong database.
Configuration is available from the Administration web page. The behavior of the backup engine can be altered based on how the data file is marked. For instance, backups can be suspended whenever sample data is used. |
|
|
A general information page has been added to allow administrators to view low level details of the 4D Server environment.
Items listed include:
* 4D application type and version
* Host OS and platform
* OS account 4D runs in
* 4D user account of web processes
* Path name of the 4D structure and data file/segments
* Code state (compiled/uncompiled)
A seperate table lists each table in the database with the corresponding number of records currently entered. |
|
|
| A new setting can be configured from the web site's administration/preferences page. The technique used to convert from 4D's native encodings to HTML character enties can be set as either mode 1 (default) or 2. The mode determines how the conversion takes place. Since the two modes produce exactly the same results, the only motivation to change the setting should be if one method is faster than the other. |
|
|
| User account creation is now possible from the web. Users from the Adminstrator group, including the default system account "Admin", can create other users and assign priviliges in a similar fashion as is possible from the 4D Client environment. |
| Logs |
| |
|
The Web and System logs are now much easier to view from the web.
Web Log:
* Only last 200 entries shown in list
System Log:
* Now divided into multiple categories for easier viewing
* Error text has been expanded to include more trouble-shooting info
* Only the first four lines of detail text is shown in the list. Click "View Details" for more. |
|
|
| In addition to being logged into the web server log table, requests for unknown URLs are now recorded as errors in the system log. This allows adminstrators and programmers to notice problems much more quickly than before. |
| Explorer Palette |
| Bulk Update |
| |
|
| New button "Kill Old Batch..." added that can close out an inactive batch. To be closed out the batch must be inactive for at least 5 minutes. |
|
|
| Some records could be left in an inactive state. This has been fixed. |
| Web Interface |
| Account Options |
| |
|
Users may change their password from the account options page. Passwords must be between 4-10 characters and may only contains these characters (excluding quotes):
"AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz0123456789" |
|
|
| Users can enable or disable the display of the Favorites and Recent sections of the SideBar. Additionally, the number of recent pages to be tracked can be set between 0 and 50. |
|
|
| Users can specify their preference in the "Account Options" web page. The setting is honored on many pages but not all. Additional pages will be updated in future releases. |
| General |
| |
|
| To enhance readability, dropdown lists on web forms will display an empty element instead of "N/A" to represent unchosen values. |
|
|
| All areas of the web site should now use HTML 4 & CSS for layout and rendering. The appearance should be more consistent throughout the application. |
|
|
| The web site should now correctly display and interpret extended ASCII characters and symbols. |
|
|
HTTP Header and HTML Header have been improved to prevent browser caching of pages. We rely on HTTP 1.1 cache controls and a single HTTP meta tag (cache-control) only. No "expires" or "pragma" are used.
Testing Results:
* IE 6 Win - Completely non-cachable (so far)
* IE 5 Win - Untested
* IE 4 Win - Completely non-cachable (so far)
* NN 4.8 Win - Not supported
* Moz 1.3 Win - Back/Forward buttons are cached but link clicks and form submissions are not.
* IE 5.1.6 Mac - Back/Forward buttons are cached but link clicks and form submissions are not.
* Safari beta - Untested |
|
|
Two sections, Favorites and Recent, have been added to the SideBar to assist users with site navigation. Pages within the SrcManager site that have been designated as trackable can optionally be shown in these sections. Common pages that are directly available from the Toolbar or Quick Actions section are generally not marked as trackable. Most data records are marked trackable. The User only needs to click the link on the SideBar to revisit the page they are interested in. This can be handy when editing many records as a quick way to jump around the site.
Favorites
Description: This section allows users to customize the SideBar to show quick links to the pages that the user visits frequently. For instance, if a user is working with a certain Project Request or Release, that record can be added to the SideBar so that it can be accessed without being searched for. The Favorites section can be updated frequently so users can feel free to manage it as they see fit. Items added will be displayed in alphabetical order.
Usage: When displaying a trackable page, a link is displayed at the bottom of the Favorites section reading "Add Current Page". As you would expect, clicking this will create a link to the current page in the SideBar. When visiting a page that is listed in the Favorites, the bottom section of the Favorites will change from "Add Current Page" to "Remove From List" allowing the page to be removed. When a page listed in the Favorites section is revisited, a ">" character will precede it's listing to indicate that the page is currently being displayed.
Recent
Description: This section will list trackable pages that have been viewed during the current site visit. Pages are displayed with the most recent page listed at the top and older views listed below. After logging out all history is forgotten.
Usage: If a currently listed page is revisted, it will be moved to the top from its lower position in the list. The user may also discard the history by clicking the "Clear List" link at the bottom of the Recent section.
Limitations
* It is not possible to remove a page from the Favorites that no longer exists for whatever reason. This will be improved at a later date.
* A page whose name is data-based (such as a ProVrsRls record like SrcMgr 1.0.1.1111) and is renamed by another user will not have its name updated in the SideBar until the page is revisited. |
| My Tasks |
| |
|
| Several changes have been made to make this page easier to work with. Advanced grouping and sorting has been added. Column layout has also been improved. |
| Project Releases |
| |
|
The statuses that can be assigned to a Project Release have been expanded to include two new stages. The beginning stages of the PrjVrsRls lifecycle have been expanded with new "Planning" and "Development" statuses. The new order is:
* Inactive
* Planning
* Development
* Active
* Maintenance Mode
* Retired |
| Project Requests |
| Editor |
| |
|
| A new field called "External Ticket" was added to the Project Req editor. The field is intended to hold ticket numbers of related material stored in external databases. The field is plain text with a maximum of 50 characters. |
|
|
| A bug was corrected that prevented files from being deleted from the list. |
|
|
| The summary field has always been limited to 80 characters in the database. However, the field on the web page allowed an unlimited number of characters to be typed. The field has been changed to accept only 80 characters. |
|
|
After successfully saving a PrjReq record, users are now returned to the page from which they came. The supported return-to pages are:
* My Tasks list
* Project Req list
* PrjVrsRls notes page
This should significantly reduce the time it takes to edit multiple requests as well as make the overall user experience more pleasant. |
| Listing |
| |
|
| The display has been improved in several ways. The "Last Update" column has been subdivided into three columns to help with readability. Relative date formatting (Today, Yesterday) has also been added |
|
|
| The color of action links at the top of the list (Query / Show All / Print) has been changed to better distinguish these functions from the rest of the page. The color was changed from black to blue. |
| Query |
| |
|
| It is now possible to search on the External Ticket field. |
|
|
A section has been added to the Project Request query form to enable searches to target the link between Project Requests and Project Releases. It is now possible to include or exclude all requests flagged as either "Affected" or "To Fix" for a given Project, Project Version or Project Release.
Also, a third column has been added called "All" which will allow you to find requests that are either "To Fix" or "Affected". By choosing "Yes" for the "All" of a project, you can get all requests for that project, even if they were not previously marked as "Affected" nor "To Fix". |
|
|
| The query form now has additional fields that may be used for searching. Type and Priority are now available. |
|
|
| The status dropdown has been removed from the query form and replaced by a status section. It is now possible to include or exclude project requests by combinations of Status and Sub-Status. |
| Project Versions |
| |
|
The statuses that can be assigned to a Project Version have been expanded to include two new stages. The beginning stages of the PrjVrs lifecycle have been expanded with new "Planning" and "Development" statuses. The new order is:
* Inactive
* Planning
* Development
* Active
* Maintenance Mode
* Retired |
| Release Notes |
| |
|
| Link created on the Release Editor page in the Release Notes header entitled "Printable version". Opens in new window. |
|
|
Rich text formatting support has been added to the Release Note Description Field. Formatting is controlled by using special symbols to markup the plain text.
The following symbols are supported:
* Bold [B]Sample[/B]
* Italics [I]Sample[/I]
* Link [LINK][URL]http://www.server.com/page.html[/URL][DESC]The Link[/DESC][/LINK]
* Image [IMG][SRC]/images/logo.gif[/SRC][DESC]A Description[/DESC][URL]http://www.url.com[/URL][/IMG]
* [ IGNORECODES] can be added to prevent any codes from being processed |
|
|
