Release Notes Documentum Release 1.4

Transcription

1 Release Notes Documentum Release 1.4

2 Released April 30, 2010 Copyright Pearson Education, Inc. and/or one or more of its direct or indirect affiliates. All rights reserved DCTM Release Notes 1.4 2

3 Contents Item Title Page Number Introduction CR CR CR CR CR CR CR CR CR CR CR CR CR CR CR CR CR s and solutions for both enhancements and bug fixes. Advanced searches for lifecycle states were nonintuitive. Users could not search for specific types of assets within specific types of folders. Users could only attach a single asset to a workflow at a time. Aborted workflow messages were not userfriendly. The URL for the Production environment was not user-friendly. FTP vendors could not add files to the repository when the files did not originate in Documentum. Documentum users and FTP vendors needed a one-way FTP process to send files both from and to the repository. An improper abbreviation was open to possible misinterpretation on the Folder Size: Info screen. A warning message about an unsupported version of Safari displayed in error when Mac users logged into Documentum. Custom folder icons based on the Folder Type attribute were needed. The non-supported browser warning message displayed for supported Safari Version Object Type was not retained during multiple file import. Controlled Vocabularies did not always display in the correct order in the drop-down lists on the Import: Object Definition and Properties screens. Object types were not mapped correctly to the file extensions during import. The automated notification for the Production Workflow provided performers a link to an outdated Documentum URL. The wording of the FTP Outbound folder was misleading. The OneWay FTP folder occupied the wrong node in the Navigation pane. Known s Known, but unresolved issues in the Release 1.4 build DCTM Release Notes 1.4 3

4 Introduction Release 1.4 is an enhancement and bug fix release to the prior Pearson CMS releases of Documentum 1.0, 1.0.1, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.2 and 1.3. Release Notes 1.4 describe: The issues and solutions for the (17) enhancements and/or bugs that were implemented and/or fixed in the Release 1.4 build. Known issues which have not yet been resolved. DCTM Release Notes 1.4 4

5 1. CR Advanced searches for lifecycle states were non-intuitive. When users searched for assets in a specific lifecycle state on the Advanced Search screen, they defined their search Properties by selecting Current State from the dropdown menu and by typing an integer from 1 to 4 to specify the desired lifecycle state. The equal sign was the default operator (See Figure 1.1). However, many users were unaware of the association between the integers and the various lifecycle states including: Initiate, Open, Review, and Final. The name of the Lifecycle State was only apparent in the Search Results (See Figure 1.2). Figure 1.1. The Advanced Search screen displays the former non-intuitive Current State search for assets in lifecycle states. Users had to type integers in the Properties textbox in order to search for assets in the Initiate, Open, Review, and Final states. DCTM Release Notes 1.4 5

6 Figure 1.2. User-friendly lifecycle states only displayed in the Search Results in the Content pane. The code has been reconfigured so that users search not by Current State but by the more intuitive Lifecycle State. In addition, users no longer search by integers but by one of four available states: Initiate, Open, Review, and Final (See Figure 1.3). The Search Results display all those assets with the appropriate lifecycle state attached. Figure 1.3. More intuitive options appear for users on the Advanced Search screen when they search for assets associated with a particulate lifecycle state: Lifecycle State, rather than Current State; the words Initiate, Open, Review, and Final instead of associated integers. DCTM Release Notes 1.4 6

7 2. CR Users could not search for specific types of assets within specific types of folders. A point of use metadata search, that is, the ability to search within a specific type of folder for a specific type of object was unavailable to users on the Advanced Search screen (See Figure 2.1). Figure 2.1. The default Advanced Search screen did not offer users the opportunity to search for a certain type of asset within a certain type of folder. DCTM Release Notes 1.4 7

8 The code has been reconfigured so that a new Point of Use Search is now available as a hyperlink from the Default Advanced Search screen (See Figure 2.2). In this way, users are able to search for a certain type of asset within a certain type of folder. On the Point of Use Search screen, users may: a. Select a specific type of folder from the Folder Object Type dropdown menu, as well as filter by properties specific to that folder (See Figure 2.3). b. Select a specific type of asset from the Asset Object Type dropdown menu, as well as well as specific properties specific to that asset (See Figure 2.3). Figure 2.2. To access the Point of Use Search screen, users click the Click Here hyperlink on the Default Advanced Search screen. DCTM Release Notes 1.4 8

9 a b Figure 2.3. On the Point of Use Search screen users may search for a certain type of asset within a certain type of folder, while further refining their search criteria for both assets and folders. DCTM Release Notes 1.4 9

10 3. CR Users could only attach a single asset to a workflow at a time. In the current Production Workflow, users could only attach a single asset to a workflow, which limited efficiency and speed as multiple assets often needed to be processed in a batch. In fact, if users attempted to attach a workflow to multiple assets, an error message displayed (See Figure 3.1). Figure 3.1. When users attempted to attach multiple assets to a workflow, an error message appeared. As a result of customization, workflow supervisors can now: a) select multiple assets at the beginning of the Production Workflow on the Start Workflow screen (See Figure 3.2), b) provide the same description for all of the assets (See Figure 3.2), and c) assign multiple assets to the same workflow performer (See Figure 3.3), while d) adding unique comments to each asset in the batch (See Figure 3.4). b a Figure 3.2. Several assets and a single workflow description appear on the Start Workflow screen. DCTM Release Notes

11 c Figure 3.3. The same Performer is attached to the batch of workflow assets. d Figure 3.4. Users may add unique comments to each asset in the batch of workflow assets. DCTM Release Notes

12 4. CR Aborted workflow messages were not userfriendly. When a workflow was aborted, the system generated an notification to end-users. However, the resultant message was unfriendly (See Figure 4.1). Figure 4.1. Sample unfriendly to end-user when a workflow was aborted. A customization was made so that when a workflow is aborted, the user-friendly message now states simply that The workflow <insert workflow name> is aborted by the wfsupervisor (See Figure 4.2). Figure 4.2. New user-friendly to end-user when workflow is aborted. DCTM Release Notes

13 5. CR The URL for the Production environment was not user-friendly. The URL for the Documentum Production environment was not user-friendly, which may it tedious for users to access the system. For example, users had to type the following URL to log in to Production: (See Figure 5.1) Figure 5.1. Non-user friendly URL for Documentum Production system. Users may now access the Documentum Production system with the following userfriendly URL: (See Figure 5.2). This simple URL routes back to the DAMtop server. Figure 5.2. New user-friendly URL for Documentum Production system. DCTM Release Notes

14 6. CR FTP vendors could not add files to the repository when the files did not originate in Documentum. The original FTP batch inbound process from the vendor, where the files originated at the vendor and not at Pearson, proved time consuming. For example, Pearson users had been creating multiple ghost files, or placeholders, for assets. The FTP vendors could not add files to the repository if the files did not originate in Documentum. The code has been modified to handle a new method for the ingestion of additional files from the vendor during the FTP process. When a file from Pearson arrives at the FTP Outbound folder in a container folder as part of a workflow, the FTP vendor alters the original file as needed and then posts any additional corrected files from their site into the container folder. The vendor next places the container folder in the Inbound folder for ingestion into Documentum. While the original file will continue on its workflow path, the other files are ingested into Documentum in the same folder as the original file; formats are automatically assigned based on filename extension. Any files ingested in this way are not attached to a workflow and start their life in Documentum without a lifecycle state. DCTM Release Notes

15 7. CR Documentum users and FTP vendors needed a one-way FTP process to send files both from and to the repository. Documentum users needed a one-way outbound process to send files to their FTP vendors, and FTP vendors needed one-way inbound FTP process to send files back to Documentum. However, such a process did not exist. As a result of Release 1.4, a new FTP process has been implemented so that Documentum users and their FTP vendors can work together more effectively. When Documentum users select files for FTP to their vendors, notification informs the vendors, summarizing what was sent and providing instructions for the files. So, too, when FTP vendors have files they need to add to Documentum, they deliver the files to the FTP. Then, notification informs the appropriate Documentum user to move the files from the FTP to the correct location in Documentum DCTM Release Notes

16 8. CR02667 An improper abbreviation was open to possible misinterpretation on the Folder Size: Info screen. When users checked the size of selected folders in Documentum, the Folder Size: Info screen displayed No of Files (See Figure 8.1). The improperly punctuated abbreviation for number was unclear to some users. Figure 8.1. The improper abbreviation of number as No on the Folder Size: Info screen led to misinterpretation by users. As a result of Release 1.4, the abbreviation is no longer used and the word Number is spelled out on the Folder Size: Info screen (See Figure 8.2). Figure 8.2. The word Number is spelled out for clarity on the Folder Size: Info screen, replacing the prior abbreviation. DCTM Release Notes

17 9. CR A warning message about an unsupported version of Safari displayed in error when Mac users logged into Documentum. When Mac users logged into Documentum using Safari 4.X or higher, a warning message displayed in error stating that the users version of Safari was unsupported. However, Documentum does support the operating system/browser combination of Mac OS X/Safari 4.X or higher. With Release 1.4, the warning message is suppressed. DCTM Release Notes

18 10. CR Custom folder icons based on the Folder Type attribute were needed. Documentum provided custom folder icons based on folder types. For example, a blue book icon represented a book level folder, whereas a green book icon denoted a lesson folder. However, as a result of the implementation of CR (generic folder types implementation) the custom folder icons needed to be based on the custom Folder Type attribute for both content and context folders (See Figure 10.1). Figure Custom folder icons need to be based on Type (crc_content_folder) and Folder Type (Book). Configuration changes were made so that custom folder icons for custom folder types, based on Folder Type, display appropriately within the Navigation and Content panes for both content and context folders (see Figure 10.2). Figure A blue book folder icon in the Content pane denotes a Curriculum Content folder where the attribute for Folder Type is book. DCTM Release Notes

19 11. CR The non-supported browser warning message displayed for supported Safari Version When Mac users logged into Documentum using the latest Safari Version 4.0.5, a warning message displayed in error stating that the users version of Safari was unsupported. However, Documentum does support the operating system/browser combination of Mac OS X/Safari 4.X or higher. With Release 1.4, Safari is added to the list of supported versions (cross-reference with CR028812) and the warning message is suppressed DCTM Release Notes

20 12. CR Object Type was not retained during multiple file import. When users imported multiple files of the same object type at the same time, they selected an object type from the Type drop-down menu on the Import: Object Definition screen (see figure 12.1). They assumed that the selected object type for the first file would be applied to all of the files. However, the object Type crc_layout appeared for subsequent files (see Figure 12.2). Thus, while the files imported successfully, only the first file had the object type the users had selected. The remaining files displayed the object type crc_layout on the Properties screen. While users could select the object type for each file, the selection process was tedious and time consuming. Figure The manual selection of the object Type PRSN Art (prsn_art) for an mp4 audio file applied to the first file in a multiple file import of files of the same type. Figure The automatic application of the object Type CRC_Layout (crc_layout)) to a subsequent mp4 audio file during a multiple file import of files of the same type. Release 1.4 fixes this bug so that it is not necessary for users to click through each asset in a multiple file import in order to select the correct object type. Object types assigned on the Import Object Definition screen will be retained on subsequent screens during a multiple file import of files of the same type (see Figure 12.3).. Figure During a multiple file import of files of the same type, object types are now retained. DCTM Release Notes

21 13. CR Controlled Vocabularies did not always display in the correct order in the drop-down lists on the Import: Object Definition and Properties screens. For attributes that have dropdown lists, controlled vocabulary values did not display in correct alphabetical and/or ascending order on Properties: Info and Import: Object Definition screens (see Figure 13.1). Controlled Vocabularies that are not implemented correctly are more difficult to use. Figure Controlled Vocabularies sometimes displayed in a nonalphabetical, non-ascending list. The code was configured so that the Controlled Vocabulary lists display results in correct alphabetical, ascending order. DCTM Release Notes

22 14. CR Object types were not mapped correctly to some file extensions during import. During the import process, object types should be automatically assigned to files based on their extensions on the Import: Object Definition screen. However, Illustrator (.ai) and Photoshop (.psd) files were not mapped to the correct object types. The code has been reconfigured so that Illustrator (.ai) files appear as object Type prsn_art format Illustrator 11.0 (see Figure 14.1) and.psd files appear as type prsn_photo format Photoshop CS2/CS3 (see Figure 14.2) on the Import: Object Definition screen. Figure Illustrator (.ai) files appear as object Type prsn_art format Illustrator Figure Photoshop (.psd_ files appear as type prsn_photo format Photoshop CS2/CS3. DCTM Release Notes

23 15. CR The automated notification for the Production Workflow provided performers a link to an outdated Documentum URL. The automated notification for the Production Workflow provided performers a link to an outdated Documentum URL ( rather than the latest URL. If users clicked this older URL, they had to open a second session of Documentum. Automated notification in the Production Workflow now links to the latest URL. 16. CR The wording of the FTP Outbound folder was misleading. The wording of the FTP Outbound folder misled users to that it was to be utilized during the Production Workflow. However, the FTP Outbound folder was actually part of the new OneWay FTP process (see CR015594). The name of the FTP Outbound folder was changed to FTP OneWay Outbound to provide clarity as to how and when the folder should be used. 17. CR The OneWay FTP folder occupied the wrong node in the Navigation pane. The OneWay FTP folder occupied the wrong node in the Navigation pane as part of the Science folder directory structure. The OneWay FTP folder was moved in the Navigation pane so that it is a first level folder directly below the Curriculum Cabinet. In this way, it is clearer that OneWay FTP is to be used by all Curriculum programs, not just by the Science Program. DCTM Release Notes

24 Known s The following are known issues in the Release 1.4 build; however, they are not resolved. SAR # CR Description The OK button on the folder selection window is disabled when users export a file. CR File Sharing Services (FSS): FSS is currently only CR recommended for linking files to InDesign. Use of full FSS CR functionality is pending fixes from the software vendor. CR CR Check-Out: When users check out an InDesign file, an error message appears. Although users are still able to check out the file, uses must close the error message and then refresh the screen. CR When users attempt to edit or check out an asset for which they do not have permission, an error is encountered. Users should select Yes when they are prompted to continue running scripts. CR The Page Number Field is not sorting correctly. For example, instead of sorting page numbers sequentially (xxiii, 4, 10, 18, 24, 30, 34), the pages are sorting in the following order: xxii, 4, 34, 30, 24, 18, 10. CR After users perform a Point of Use search, the search results header displays the file paths for each of the assets that are retuned in the search results instead of the default X results in the X repository. DCTM Release Notes