ULTRA 3.0 Release Notes
Release notes are divided into the following categories:Documents, Submissions, and Deliveries
No confirmation required when cancelling document(s) or submission(s).
When a qualified manager chooses to cancel one or more documents and/or submissions, the action will be taken immediately after the Go button is clicked, with no confirmation dialog or warning given, and no way to undo the action. Because of this, users should take great care when using the Cancel Document or Cancel Submission actions.
(Issue #2339)
Item checkboxes visible to users lacking permissions to take actions on items.
A user lacking permissions required to take action on documents, submissions, and/or deliveries will see a selection checkbox for each document/submission/delivery item, though no actions will be available. Selecting item(s)in this situation will have no effect.
(Issue #2531)
Grid lines not visible in printed Submission Report.
A printed version of a Submission Report will lack the table grid lines visible on the screen.
(Issue #3995)
Source language information always displayed in Submission Report.
When running a submission report without selecting the source language in the "Select Language(s)" field, a column listing the source language will be displayed in the report.
(Issue #4281)
"Edit Delivery" action available for "pull" type deliveries.
The "pull" type of delivery has no address, as it takes place only when ULTRA is polled by the submitting application. The Edit action, available on the Delivery Browser page, causes the Edit Selected Deliveries page to open when "pull" type deliveries are selected. The user is then faced with a page lacking any configurable settings, with the only options being Cancel and Save buttons.
(Issue #4552)
Cancelling all target documents does not cancel corresponding source documents.
If the "Cancel All" action is taken on a project's target documents while one or more of the documents have not yet completed all the tasks in their source workflows, those documents will not be cancelled in source workflows and all remaining source workflow tasks will be completed before work is halted. To avoid this situation, the user should not cancel target documents until they have actually reached a target workflow task.
(Issue #4734)
Filter settings not reapplied after Change Task action in Document Browser.
If a user specifies document display settings using the filter fields and/or lists in the Document Browser, then performs a "Change Task" action on one or more documents, the filter settings will not be reapplied to displayed documents upon the return to the Document Browser page. This will be evident only when the "Change Task" action changes a document's properties in a way that should disqualify it from display under the filter settings. For example, a user filters for "Translate" in the Task column, selects one of the displayed documents, and uses the "Skip one or more tasks" action to skip the document to the Proofread task. After the action is completed, the changed document will still be visible in the Document Browser, in spite of its changed task, until the Update Query icon is clicked.
(Issue #4773)
"Modify All Documents" actions have no effect on source documents accessed via Submission Browser.
If a submission's documents are viewed by clicking the Documents In This Submission icon on the Submission Browser page, actions taken on all source documents (using the Assign [all], Revert [all], Cancel [all] or Change Task [all] actions) will appear to be executed properly but will not actually take place. It is necessary to select the documents in question, using the checkboxes, and use one of the Modify Selected Documents items. This issue applies only when the Document Browser was accessed via the Documents In This Submission icon on the Submission Browser page; all Document Browser actions work normally when the Document Browser is accessed from the Project Browser.
(Issue #4973)
Cancel Delivery page has incorrect header wording.
After choosing to cancel selected delivery or deliveries, a confirmation page will open. Beneath the navigation tabs, a header reading "Cancel Selected Submissions" will be visible, though submissions are not cancelled by the Cancel Delivery action.
(Issue #4983)
Browser refresh after "Change Task" action results in error message.
Changing a document's task from the Document Browser, then performing a Web browser refresh (using the browser's Refresh button or the refresh link in the application page) will result in an error message reading "Another user has saved a change to this page after it was originally displayed to you. You will have to re-enter your changes." For this reason, the browser window should not be refreshed after performing a Change Task action.
(Issue #5259)
Changing task of image document to "Waiting for Translate" task may freeze workflow.
An image document that has completed the Graphics Source and Graphics Transcription workflows will enter the Graphics Target workflow. If, at this point, a Change Task action is performed to restart the workflow at the "Waiting for Translate" task, the document will sit at this task forever. For this reason, managers should avoid restarting the workflow at the "Waiting for Translate" task.
(Issue #5571)
General User Interface
Bad Project Access Codes may cause ULTRA PM to block all submissions from IP address.
If a GlobalLink project is set up with an incorrect or invalid Project Access Code, repeated authentication failures may cause ULTRA PM to interpret the authentication attempts as a security hazard and refuse to accept any content from the IP address used by that GlobalLink server. To prevent this, GlobalLink project managers should be told to double-check all projects' ULTRA PM Project Access Codes during the GlobalLink project setup procedure.
(Issue #2541)
Application database server crash results in "Invalid Password" error message.
If the underlying database connection dies, users attempting to log in to ULTRA PM will receive an error message indicating an invalid password. In this situation, the log file will contain a message similar to the following: rollbackTransaction -- OracleContext 0x205cc8: Unable to rollback transaction Sep 17 07:48:08 UltraPM[5428] (alert): Exception NSInternalInconsistencyException: rollbackTransaction -- OracleContext 0x205cc8\: Unable to rollback transaction
(Issue #3422)
Document display preferences do not affect Delivery Browser display.
The items chosen for display in the Selected Statuses list on the Miscellaneous Preferences page will have no effect on the documents visible on the Delivery Browser page. All documents, regardless of status, will be shown.
(Issue #3757)
Default timezone in Preferences does not match timezone set for user.
A user whose timezone was established during the user setup process will not see that timezone as the default on the Preferences page. For example, a user's timezone was set as GMT-02 (Mid-Atlantic). When this user goes to the Preferences page, he or she will see the GMT-00 (London, Dublin) as the default timezone setting.
(Issue #4889)
ULTRA PM incompatible with Apple WebObjects Monitor application.
The Apple WebObjects Monitor application must not be run simultaneously with ULTRA PM. A crash will result.
(Issue #5106)
Special search characters may be utilized in query filter fields.
In addition to the asterisk ( * ) wildcard character, several additional special characters may be used to refine queries made using query filter fields throughout the ULTRA PM application. These characters are:
Equal sign ( = ) Used to specify an exact-match search. Place the equal sign before the search text. For example, entering the text "=Blue.html" in a filter query field will produce matches only for documents named exactly matching that text.
Greater-than sign ( > ) Used to search for documents with beginning characters having a sort value greater than the character following the > sign. For example, entering the text ">8" in a filter query field will produce matches for documents named 95.html and Neptunium.html, but not for a document named 7X.html.
Less-than sign ( < ) Used to search for documents with beginning characters having a sort value less than the character following the < sign. For example, entering the text "<X" in a filter query field will produce matches for documents named 25.jpg and Strontium.jpg, but not for a document named Zero.jpg.
(Issue #5107)
Calendar interface causes security alert warnings when using SSL.
A user accessing ULTRA via an SSL connection will see browser-generated security alert popup windows when clicking on any of the ULTRA PM application's calendar interface buttons. No actual security danger is present in this situation.
(Issue #5462)
Projects
Volume-hourly Project Vendor Rates not reflected on invoice
Currently, ULTRA has no means of determining the number of hours worked on a project task. For this reason, if the "Volume-hourly" type of Project Vendor Rate is set for a project's task(s), the values entered in the Minimum and/or Tiers fields will not have any effect when the invoice is generated.
(Issue #2528)
Add Team page accessible even when no qualified users exist.
It is possible to reach the Add Team section of Work Assignments in Project Setup even for language(s) with no qualified users available for assignment to the team. Since no users may be added in this situation, the created team will be irrelevant.
(Issue #3456)
Domains not alphabetically sorted on Add Rule page.
When adding or modifying a Work Assignments rule, the domains displayed in the "if domain of expertise is" drop-down list will not be arranged in alphabetical order.
(Issue #3960)
Schedule comment with more than 300 characters causes error.
Entering a comment containing more than 300 characters into the Comments field of the Modify Schedule page will cause an error message reading "An unknown error occurred while saving your changes" to appear. Schedule comments must be limited to 300 or fewer characters.
(Issue #4042)
No error message when attempting to use the same language for both source and target.
An attempt to add a language pair to a project using identical source and target languages will be unsuccessful (i.e., the language pair will not be saved in the project), but no error message will be displayed indicating what has happened.
(Issue #4058)
Modify Gate/Schedule pages can be accessed without selecting task(s).
Clicking the Modify Gate or Modify Schedule buttons with no task(s) selected on the Schedules section of Project Setup will result in the Modify Gate or Modify Schedule page opening, though any specifications made will have no effect on actual gates or schedules.
(Issue #4402)
Projects navigation tab visible to users lacking sufficient access permissions.
Users with Vendor Manager or User Manager roles will see the Projects navigation tab at the top of the application window, though their roles' permissions do not permit them to view or modify project information.
(Issue #4710)
Fractions of days or hours can be entered in schedule field, though fractional amounts are ignored by ULTRA.
When creating or modifying a project schedule, it is possible to enter a fractional amount (for example, 1.5) in the # Hours or # Days fields of the Modify Schedule section. However, ULTRA will ignore the fractional amount, so that an entry of 1.95 days will be treated as 1 day.
(Issue #4976)
Existing hour range values not prepopulated when modifying Work Assignment rule.
If a Work Assignment rule uses an hour range ("If documented was submitted between the hours of..."), the specified hours will not be prepopulated in the Edit Rule page when a user chooses to modify the rule.
(Issue #5252)
Cannot specify today's date for Block-Word type project vendor rate.
Entering the current date as the starting date for a Block-Word type of project vendor rate will result in an error message reading "Invalid value for start date. Start date must be in the future."
(Issue #5622)
When modifying existing Work Assignment rule, hour range values are not retained.
The hour values listed on the Edit Rule page will not show previously defined values when modifying an existing rule.
(Issue #5626)
Users
Language Pairs in user qualifications not alphabetically sorted.
On application pages that list user qualifications, language pairs will not be displayed in alphabetical order.
(Issue #4564)
Address information not duplicated when using Duplicate User feature.
While all qualifications will be prepopulated when duplicating an existing user, the contact information fields (telephone, address, etc.) on the User General Info page will be blank.
(Issue #4747)
Read Only Manager from external Agency Vendor can view all target documents.
A Read Only Manager will be able to view all of a project's target documents, not just those for which his or her agency is qualified to work with. For example, a Read Only Manager from an agency that deals only with English-to-Russian localization will be able to view the project's Arabic target documents as well as the Russian ones.
(Issue #5611)
Changing an existing user's vendor to a nonexistent vendor name causes error.
Changing the information in a user's Vendor field to an invalid or nonexistent vendor name will result in an "Unknown error occurred while saving your changes" error to appear. At this point, entering a correct vendor name will result in an additional error.
(Issue #5214)
Domains of expertise not copied when duplicating a user.
A user created with the "Duplicate User" feature will not have the domain qualifications of the original user; these will need to be selected manually. The other qualifications will be copied.
(Issue #5634)
Vendors
Cannot change vendor of assigned team.
If you change the vendor for an assigned team, you may lose some of the data set for that team. If you wish to change the vendor for a team, create an identical team with the new vendor information.
(No issue number)
Agency Vendor created by Agency Vendor Manager will not be visible to that manager after completion of creation process.
If a Vendor Manager (VM) who works for an Agency Vendor creates another Agency Vendor with his or her own vendor specified as the parent production center, the newly-created vendor will not be visible to the vendor immediately after the creation process or in subsequent searches. However, the new vendor will be visible to qualified managers of the vendor's parent production center(s).
(Issue #5450)
Project Vendor Rates section shows vendors assigned only to reference content-related responsibilities.
If a Project Task Manager from an external vendor is assigned a role as Instructions Editor, Glossary Editor, or Style Guide Editor, this vendor will be displayed in the Project Vendor Rates section of the Project Setup Portal. It will be impossible, however, to set rates for this vendor, as no services will be available.
(Issue #5451)
Required vendor qualifications can be removed from external vendors.
If a Project Task Manager from an external vendor is assigned to a project and one or more of the qualifications required for the project is removed from the vendor, the Project Task Manager will still remain assigned to that role within the project, though lacking the necessary qualifications from his or her vendor.
(Issue #5518)
Project Task Managers from external Agency Vendor may have access to documents outside their area of responsibility.
A Project Task Manager from an external vendor may be able to view and take action upon types of documents other than those for which he or she has been given responsibility. For example, a Project Task Manager from an external agency is assigned to manage the Graphics Engineer role for the project; this Project Task Manager may be able to access the project's non-graphics documents.
(Issue #5609)
Workflows
Rejection to disabled task results in document moving to next enabled task.
If an ULTRA Desktop user rejects a document using a "Send back to [workflow task]" rejection reason and the task specified has been turned off in the ULTRA workflow, the document will proceed to the next enabled task in the workflow. For this reason, ULTRA Desktop users cannot be 100% certain that the document will actually go to the intended workflow step.
Turning off Assessment (LA) primary workflow task leaves Assessment Prep (LA) auxiliary workflow task intact.
A user wishing to eliminate all Assessment tasks in a project's Standard Text (Source) workflow may turn off the Assessment (LA) primary workflow task without also turning off the Assessment Prep (LA) auxiliary workflow task. In this case, a document failing the Convert to RTF task will be directed to the Assessment Prep (LA) task. Users must turn off auxiliary as well as primary Assessment workflow tasks in order to completely avoid this type of task.
(Issue #3704)
Notification messages for late documents are not sent until document reaches scheduled workflow task.
An email notification is automatically sent out to a task's Project Task Manager when a document in the task misses a scheduled deadline. However, each deadline is task-specific, so a document must actually be at the scheduled workflow task in order to trigger a notification when the deadline lapses. For example, a schedule of January 10 is set for a document to complete the Edit workflow task, but a problem with the preceding Translate task prevents the document from reaching the Edit task until January 15. In this case, the late notification for the Edit task would not be sent out until January 15. For this reason, the Project Task Manager should set a separate schedule for each workflow task.
(Issue #4622)
Work assignment rules that separate GTX file from associated image may prevent GTX file from being checked out.
If a Work Assignment rule is established that results in a GTX image-transcription file and its associated image being sent to separate resource teams, ULTRA Desktop users will be unable to check out the GTX file, as associated image cannot be downloaded. For example, a rule that specifies that documents with filenames ending in .gtx will be assigned to Team A, while all other documents will be assigned to Team B, will cause the split between the GTX file and the image file. For this reason, work assignment rules that might split the two files should never be established.
(Issue #5630)
Members of custom assessment team cannot view reference documents for Classify task.
If a custom Resource Team is created for the Assessment task and Classification is enabled for the project, documents submitted from GlobalLink as part of a Reference Submission will not be visible to the team members, even though a rule is in place to assign such documents to the team. Manual assignment to a specific user, rather than assignment by rules, is necessary in this situation.
(Issue #5633)
Skipping a document's remaining tasks will prevent document delivery.
Using the "Skip all remaining tasks" action on a document will cancel all remaining tasks, including the Deliver task, meaning that delivery will never take place. To skip remaining workflow tasks and still permit document delivery, it is necessary to use the "Skip to specific task" action and skip the document directly to the Deliver task.
(Issue #5645)