SAP NetWeaver MDM 7.1 SP02 Release

[] [] [] [] [] [] [] [] [] [] [] []

  1. Installation of SAP NetWeaver MDM 7.1 on IBM iSymptom Additional information needed when installing SAP NetWeaver MDM 7.1 system and other MDM related services on an IBM i host. Other terms as400, as400, iSeries, i5, IBM i, MDM 7.1, Installation,...
  2. MDM: Extraction of Master Data Objects from SAP systemsSymptom You use SAP NetWeaver Master Data Management. You want to load master data from a SAP Remote System (R/3, ERP, CRM, SRM) into your MDM repository.You use MDM’s local extractor (transaction...
  3. MDM 5.5 Release Restriction NoteSymptom Information on Release Restriction for MDM 5.5 Other terms MDM, Master Data Management, NetWeaver Reason and Prerequisites The statements made here, especially those referring to availability dates, reflect current planning and...
  4. MDM GDS 1.0 Release Restriction NoteSymptom Information on Release Restrictions for MDM GDS 1.0 Other terms SAP MDM, SAP Master Data Management, Global Data Synchronization, GDS Reason and Prerequisites The statements made here, especially those referring to...
  5. MDM 5.5: Generic extractor for Customizing dataSymptom You use MDM 5.5 Support Package 4 and want to use the new extractor for customizing data for initializing the Support Package 4 repositories. Other terms SAP Master Data Management, MDMGX...
  6. Load stand. Material/Product Repository into GDS-RepositorySymptom You use standard Material Repository or Product Repository of SAP MDM and want to load data into GDS-Repository GDS 2.0 from the Material Repository or Product Repository instead of loading data...
  7. Manual steps of the upgrade process from GDS 1.0 to GDS 2.0Symptom This note contains the neccessary manual steps when upgrading from GDS 1.0 to GDS 2.0 Other terms SAP NetWeaver MDM global data synchronization, SAP GDS 2.0, SAP GDS 1.0 Reason and...
  8. Solution expected in MDM 7.1 SP04Symptom Bug has been identified and needs to be fixed or a new feature is requested. Other terms Build release fix bug patch problem issue MDM service pack development SP4, Service Pack04,...

Symptom

SAP NetWeaver MDM 7.1 SP02 Release Note
Other terms

MDM, Master Data Management, SAP NetWeaver MDM, Service pack 2, Service Pack 02, SP2, MDM 71, 7.1.02.59, 7.1.2.59

Solution

Enhancements & Bugfixes coming with SAP NetWeaver MDM 7.1 SP02

MDM CLIX
Enhanced: Allow CLIX to receive error code from failed UnArchive operation. Prior to this, CLIX received a successful return even if Unarchive failed.

MDM Console
Enhanced: Tuples can now be used in calculated field calculations.Enhanced: Remote System Key Generation Range is now 64 bits. Previously it was 32 bits and only allowed values smaller than 2^32. Now To and From values smaller than 2^64 are allowed.Enhanced: Archive by mask is now enabled together with other options such as archive without originals or variants.Fixed: When deleting a unique field, MDS needs to send out a notification of “unique constraint removed”, and Console needs to refresh UI to show the changes. (O1156411 2009).Fixed: In iViews ordering the display field is done in alpha numeric order (1-10-11-2-21′) (O10934 2009).

MDM Schema Migration
Enhanced: Enhanced dependency generation for Schema Migration.
The “AtLeastOne” constraint was added to ensure that at least one instance must exist for mandatory objects such as main tables.The “Rename” constraint was added in order to prevent “changes are too complex” errors due to name collisions. This constraint will, if necessary, allow an object to be given a temporary name in order to avoid a name collision.

Enhanced: Improved logging for transport load and update operations.Fixed: Map transport did not work for XMLs of over 10 MB. (O115575 2009).Fixed: Console problem with “Import Schema” that prevented the user from acknowledging an Import Schema failure. The MessageBox would appear but the wait cursor would prevent the user from clicking it (O115575 2009).

MDM Data Manager
Enhanced: Improved UI in Validations tab: The table selector now enables tuple selection as well as table selection and is Auto focused.Enhanced: The mini-search control is now always used for main table lookups. Support for wild-cards has been added for text field. The “*” character is the wild-card and can be used at the beginning, end, or both ends of the string. Previously, in the mini-search control, all of the display fields had to be filled in before before the Lookup Record Selector dialog would be displayed. Now, only one display field has to be filled.Enhanced: Added support for popup HTML windowsEnhanced: The delete button in the Edit Record Key Mappings dialog is now disabled when there is nothing to delete.Enhanced: Added Data Manager support for validation messages when moving a node in a hierarchy.
If a node is moved in hierarchy mode, and it causes a validation warning or error, the user now gets the standard validation dialog.Enhanced: GM Time fields are now editable in Data Manager.
The GM Time field is displayed in either the local or the GM time zone, depending on the setting Configuration->Options->Display time stamp fields in local time.Performance Improvements: Multiple performance improvements including:If the Retrieve Modifications Delay is set in the registry it’s now randomized by +-20% to keep all clients from retrieving updates a the same time.Added support for an “Auto Relimit” registry setting to turn off updates to the Search pane when adding or modifying records.Fixed: Enabled support of fractions for time measurement fields. (O939407 2008).Fixed: Fixed a problem with the relative date search control.Fixed a problem that would sometimes cause a relative search to be displayed as an absolute search. (O186157 2009).”Fixed: Added support to the Data Manager to deal with LF-only text for large text fields. The affects the display of large text fields in the Records pane, in the Record Detail tab, and in the Language Detail tab. Data in LF-only format would display as a single long wrapped line, possibly with boxes where the LF characters are. (O4266244 2008).”Fixed: Added carriage return (0×0d) to the list of white-space characters to trim. (O165149 2009).Fixed: The result pane was not updated properly after duplicating a record and the assignments were not triggered by the workflow job. (O229116 2009).Fixed: Fixed a problem with object merge. Under some circumstances it would complain that not all of the selected records were used, even when they were. (O239341 2009).Fixed: Changing the order of the search tabs isn’t saved after log off and log on to the Data Manager (O29851 2009).Fixed: Validation expresion “Required_Fields” can’t be used (O989392 2008).Fixed: Free form search filters don’t work as expected. (O921149 2008).

MDM Import Manager
Fixed: XMl schema with multiple elements with the same name at the same level was not being processed properly. (O117344 2009)Fixed: Import Manager source preview grid does not show XML data properly. After scrolling down, data is missing from grid (O186735 2009).Fixed: During Import via Import Manager multiple records were being created for single valued tuples. These extra records caused import via Import Manager to fail for the next import. (O169168 2009).Fixed: In Import Manager in the Connect Source Dialog when processing fixed text through port, the “Columns” data was set into the wrong data member. (O1005379 2008).Fixed: Import: The configuration of which workflow to use was not saved after the import map was exported and reimported. (O161207 2009).Fixed: After exporting and importing the maps the replacement rules caused the wrong values to be replaced. (O245953 2009).

MDM Import Server
Optimal MDIS Chunk and Slice size: The optimal MDIS chunk size to use in MDM is 2000 and the MDS slice size is 100.Fixed: When XML schemas contained multiple elements with the same name at the same level, Import Manager and MDIS were not processing them correctly.. The schema parser is now fixed to ignore the multiple instances of the same element at the same level and not to add an extra node to the schema tree. (O117344 2009).Fixed: Map transport did not work for XMLs of over 10 MB.Map export and import did not work with separators of 0×0B. (O115575 2009).Fixed: Changed the color coding for errors in Import Logs to red so they would be more visible when viewed via the browser. (O2741328 2008).

MDM Installer
MDM 7.1 Installation Master Build 21:Installation Master was extended with an version information file. The file MDM_IM_VERSION[.TXT] can be found in the root folder of each installation master. The contents should be added to all customer message in the area of installation.For Windows OS : SAPLOC share is ignored:will not be created by MDM installerwill not be used to determine the SAP Installation locationFor Windows OS : Instance Profile parameter DIR_INSTANCE is set hardcoded to installation location.For Windows OS : Bugfix for setting the correct permission on the registry entries for the installed SAP System.See SAP Note 1318150 “MDM 7.1 Install fails on Windows due to Registry Permissions”The installer shall disable Wily Instrumentation level during installation. If customers decide to turn on the instrumentation, the default instrumentation level shall be set to 10.

MDM Java API
Enhanced: Implemented a level by level retrieval of tuple records with searching and sorting and paging capability. (new protocol GetLimitedTupleValues())

Enhanced: Added new input parameter ‘isRetrieveDisplayValue’ to all commands retrieving Records. This parameter enables specifying whether the display values should be loaded from the server or not.Enhanced: Language specific actions and statuses of workflow tasks:Added a new method for getting the language specific action name of a workflow task: WorkflowTaskAction.getTypeName(Locale)
Added two new methods for getting language specific status name of a workflow task:
WorkflowTask.getStatusName()
WorkflowTask.getStatusName(Locale)Enhanced: Added new properties:
TextAttributeProperties.isKeyMappable
TextAttributeProperties.setKeyMappableEnhanced: The WorkflowJob class was changed to make the API workflow functionality more like the functionality in Data Manager.
Priority field marked as deprecated in WorkflowJob class.
The old constructor and priority field getter method was marked as deprecated.
A new constructor was added.
The ActiveWorkflowTask hierarchy classes were updated:
A priority field and priority field getter method was added.
The old constructors of ApprovalWFTask, MatchingWFTask, and PostValidationWFTask were marked as deprecated.
Added new constructors to all ActiveWorkflowTask classes.The SetWorkflowTaskPriorityCommand was updated:
Setting the priority of an inactive workflow task is now prohibited.
WorkflowHelper:
The convertFrom(WorkflowBoxData info) static method was updated due to changes made in the ActiveWorkflowTask classes.
Updated javadoc of all classes.Enhanced: Provided a new method called RC.toString(Locale, int) for localized messages.Enhanced: Added a new command to check if the Java API is compatible with a running MDS.Enhanced: Added two new methods called FieldProperties.getSortIndex and FieldProperties.setSortIndexEnhanced: Added the new methods:
SimpleConnectionFactory
getConnectionCreationTimeout
setConnectionCreationTimeout
ConnectionPoolFactory
getConnectionCreationTimeout
setConnectionCreationTimeout
(O1022488 2008)Enhanced: Added the two methods isDefaultToCurrentTime and setDefaultToCurrentTime to the class GMTimeFieldPropertiesEnhanced: Added these new methods:
CreateRecordCommand
boolean isCommitOnWarning()
void setCommitOnWarning(boolean isCommitOnWarning)
ValidationResult getValidationResult()
ModifyRecordCommand
boolean isCommitOnWarning()
void setCommitOnWarning(boolean isCommitOnWarning)
ValidationResult getValidationResult()
DuplicateRecordCommand
boolean isCommitOnWarning()
void setCommitOnWarning(boolean isCommitOnWarning)
ValidationResult getValidationResult()”Enhanced: Added AttributePriorityModified event when AttributeLinkModified event is sent
2) Minor changes:
a) Change name RecordsRollBackEvent to RecordsRollbackEvent
b) Add abstract class for check-in, check-out and rollback events”Enhanced: Changed name from RecordsRollBackEvent to RecordsRollbackEvent.Added a new method TupleValue.getLookupDisplayValueFixed: Prevented possible NullPointerException while invoking *.clone() method of checked in classes.The clone() method implementation was updated for the following classes: RepositoryIdentfier, RegionProperties, TableProperties, AttributeLink, AbstractAttributeProperties, CoupledAttributeProperties, NumericAttributeProperties, TextAttriuteProperties, TextAttributeValueProperties,
MultilingualString, RegionalString, UserProperties, RoleProperties, PortProperties, RelationshipProperties, RemotesSystemProperties, ImageVariantProperties, TupleDefinitionProperties, FieldProperties, BooleanFieldProperties, TimeStampFieldProperties, UserStampFieldProperties.Added testing for null value of object before invoking clone() method for all other checked in classes.Enhanced: Tuple requirement for searching and retrieving tuple values for thousands of tuple records.
New interfaces:
1. New class TupleSearch
2. New class RetrieveLimitedTupleValuesCommand
1. New method ResultDefinition.isLoadTupleValues
2. New method TupleValue.getDisplayValuesChanges to the existing interfaces are:
1. TupleRecordId will extend AbstractUniqueId instead of AbstractId
2. TupleValue will also extend marker interface RepositoryItem
3. Enable getLookupDisplayValue(FieldId tupleFieldId) for a tuple field, both Record and TupleValueFieldValuesBasedRepositoryItem was slightly modified.Enhanced: Added two new methods to MdmValueFormatter class formatLocalizedFieldValue and formatLocalizedAttributeValue. Unlike the formatFieldValue and formatAttributeValue, these new methods format values according to custom locale parameters. The locale parameter is the first priority for value formatting. If locale is null, the formatting is performed using the region parameter. If the region parameter is also null, formatting is done using the default locale.Enhanced: Added a method method called TupleValue.containsField similar to the Record interface.Fixed: Creating and Launching a Workflow job via Java API on a workflow with an assign step, where the assign step will fail causes TaskAction[5] where action type = 100 (perform) to be disabled. In the job’s context menu in Data Manager the perform action is available.(C1538254 2008).

MDM Portal iViews
Enhanced: Tuple field supported (see details in SAP Note 1327520 “Working with Tuples in Item Details iView – MDM 7.1 SP2″).Enhanced: Text Blocks field value selector is supported for Item Details iView on main table (O417384-2008).Enhanced: The “Enable Add Attribute Values” property was added to Item Details to enable adding taxonomy attribute values “on the fly”(O160431-2009).Enhanced: A new tab was added to the Item Details Multi-lookup selector (popup) for listing the selected values. The same new tab was been added to the Picklist search iView configure popup(C4972678-2008)Enhanced: Create job popup: Add/Remove records to job actions in the Result Set automatically generates an internal event updating the ‘number of records’ columns in the UWL Result Set.Enhanced: Item Details Multi-value fields representation was enhanced to include a leading numerator: [counter] – listing the number of values assigned to the field.Enhanced: Item Details and Result Set view mode to support currency and measurements fields formatting according to user locale, even if portal users locale language is missing from MDM repository (O957205-2008, O229316-2009)Enhanced: Tool-tip for Item Details Multi-value fields lists 5 first values while in View mode.Enhanced: On the fly upload of Blobs using Main table Item Details Blob fields. The blob object is added to the repository and linked to selected record.Enhanced: iView error & warning messages now exclude un-translated text messages (O999123-2008)Enhanced: Text Search iView on Text blocks only supported Is Null operator. Now all operators are supported.Enhanced: Default Search constraint on Portal Page level is now supported.Fixed: Server Password input field was removed from system object wizard (C5062293-2007)Enhanced: Item Details on Blob tables (Images, PDF etc) are now supported. The Add button on the Blobs Result Set was depracated.Enhanced: The Item Details Taxonomy attributes UI was changed to accommodate accessibility standards.Enhanced: Text Search iView ‘Group Layout’ property was added. This enables changing from default Grid to Group view.Fixed: Qualifiers search was not working when two or more main tables exist for the repository (O30482-2009)Fixed: Item Details PDF links were not working when a thumbnail was missing (O132775-2009).Fixed: Blobs table Result Set comparison Tab failed when DataID or PrintSize fields were included as one of the comparison fields.Fixed: Real, Currency and Measurement fields have been enhanced to support different languages/locales settings (O135216-2009, 957205 -2008).Fixed: isNull and isNotNull Validations were incorrectly enforced (O138388-2009).Fixed: Taxonomy attributes linked to parent nodes in Data Manager were not visible when viewed from Item Details iView when selecting a record referencing the taxonomy child node (O122481-2009).Fixed: Item Details sorting of qualified links was not working if one of the qualifiers was a lookup field (O155411-2009).Fixed: text search iView wizard did not allow adding Single Text Block Field or Multi value HTML.Fixed: Item Details single hierarchy lookup selector (for large hierarchy lookup tables) initial popup load was very slow (O185568-2009).Fixed: When a user has no permissions to edit Qualifiers of specific types (Date, Boolean, Large Text etc), saving the modified record would fail (O185568-2009, O221924-2009,C1448309-2009).Fixed: Item Details design-time Editor displays Relationship field codes instead of field names (O127498-2009).Fixed: Item Details design time editor fails when trying to edit a Relationship field that has Quantity or Is Required (O127498-2009).Fixed: Item Details failed if Multi valued Hierarchy field was displayed as a list box and an empty string value was selected (O2312-2009).Fixed: Result Set EPCF event with strings containing double quote failed (O176329-2009).Fixed: Result Set and Item Details iView on Image table would not display PrintSize and Format fields.Fixed: When a relationship field has a Required or Qty, their values were not visible in the Item Details iView.
Now when ‘All fields’ option is selected in the Item Details editor for the Relationship field, 2 leading columns are displayed listing the Quantity and Required values for each Relationship record (O127498-2009).Fixed: When Non Qualifier Row Selection property is set to Allow Edit, and Enforce Non-Qualifier Record Uniqueness property is set to true, then for Add, Edit and Duplicate action for qualified links, uniqueness is not enforced for the qualified link.Enhanced: saveRecord EPCF event is now supported. Custom applications using this event, can initiate a Save on an MDM standard Item Details iView.

MDM Server
Enhanced: Logging:Added logging of DBMS client library version and DBMS server version in MDS.log.Removed the file path from the log messages’ file name.Added a new hidden MDS.ini setting “Max Number Of Log Files” to specify the maximum number of server log files to keep. The default value for this setting is 20. If user set Max Number Of Log Files=0, the system will still keep one log file.Enhanced: Added a Normalize function to the validation builder menu that enables evaluation of a normalized text field within an expression.Enhanced: On purge deleted items in Publisher, the list of deleted items and object properties context references is now cleared so that it is more consistent.Enhanced: Family Spreads are now updated in Publisher as soon as changes are made.Enhanced: Introduced a new repository metric which shows whether a repository is fully loaded or not.Enhanced: MDS prevents unarchiving or duplicating repositories that have more languages than can be supported by the target DBMS.Previously either the unarchive operation would continue until an error would occur or else unarchive would be sucessfull but an error would occur during load time. Now the Duplication or Unarchive will stop very early on in the process with appropriate error messages output.
This behaviour can be overridden to allow continuation after the error is noticed by setting the following in mds.ini:
Unarchive Ignore Language Count=True

Enhanced: Presentation text now has a record ID strand which further enables the ability for granular refresh of pieces within the text. This was introduced as a workaround for a bug in the IBM DB2 i5/OS where arrayed Deletes, Updates, and Inserts cause the client program to fault. By adding the setting: DBMS Array Binding=false to the mds.ini file, all arrayed DBMS operations will be run in single row mode. While this parameter will work with any brand of DBMS, it has a large performance penalty, so we recommend it only in the case where MDS is crashing.Presentation text now has a record id strand which further enables the ability for granular refresh of pieces within the text.When import retrieved all lookup table values, MDS was sorting the records alphabetically by display value. However, the import code always resorts the values by id, so the sort on the server was unnecessary. This also removed the need to manually unlock before sorting, so now the function locks and unlocks in the standard way. This is similar to feature request ‘347, ‘Display all attributes of related items’, which is still an open issue. However, record-set publication nodes, ‘518 ‘622, are a more direct way of handling presentations of unrelated records (why make MDM core data relationships only for the meta data purpose of grouping unrelated records layout presentation in Publisher). It should be noted that record-set publications should one day have functionality to ‘fake’ relationships, but that day it not now. Anyways, this feature allows all attributes (linked to all the families relevant to the record-set) to be configured and effect the table generation for a selected record-set publication node.Enhanced: Added new fields “ParentTableId” and “ParentRecId” in A2i_CM_HistoryEnhanced: The synchronize slave progress indicator now shows accurate timing information both for Console and for CLIX.Enhanced: When too many repositories are created on a certain database so that the file system is too full MDS now returns a more accurate error including code RC_CM_DB_DBMS_FULL.Enhanced: Depracated the BULK_IMPORT_SILO_LEVEL mds.ini setting which received a numeric value and replaced it with the Bulk Import Silo setting which receives true/false or 0/1 values. If your BULK_IMPORT_SILO_LEVEL is set to 3 (or missing), then Bulk Import Silo will be set to true, otherwise it will be set to false.Enhanced: Added support for Depth, Parent, and Child for hierarchy tables in the validation expression builder.Enhanced: Enabled Multithreaded Matching using the following mds.ini setting:
Multithreaded Matching=TrueEnhanced: Unarchive by mask is now enabled for repositories having multiple main tables.Fixed: Workflow changes were not synchronized correctly from Master to Slave.Fixed: Imports that triggered non-checked out workflows failed when some destination records were already checked out and some destination records were not checked out because workflow does not allow mixing checked out and non-checked records in one job. Now imports that trigger a non-checked out workflow, separate imported checked out records from imported non-checked-out records and put them in two separate workflow jobs.Fixed: Multiple Update events are being triggered instead of a single event when a record is modified that triggers a recalculation on another calculated field. (O111598 2009).”Fixed: MDS/NCS was writing files with cryptic names. There was a mismatch between non-unicode NCS library and unicode enabled RFC library. Now MDM makes use of unicode version of NCS. (C4473351 2008).Fixed: Publisher will not properly display Presentation or Spreads. (C3040891 2008).Fixed: Out of date and lock errors appeared when trying to synchronize slave when master repositories were out of sync with their slaves due to failed updates. This change causes the slave ignore lock versions. Further development is planned in order to make lock version update conditional upon the success of the operation. (O501461 2008).Fixed: Files in distribution folders will be reported under repository metrics. Database connections metric will be reported under server (C3412672 2008).”Fixed: MDS crashed during repository load on AIX. (O1017281 2008).Fixed: E-Mails sent by workflow contained “None” in the “Sent” field instead of time and date. (O901864 2008).Fixed: E-mail notification step in workflow sent E-mails that are missing the body of the mail while using Exchange 2007. (O3104641 2008).Fixed: Error description on import server not reasonable. The problem was that the low level error message was replaced by high level error message that is too general. The fix appends the high level error message to the low level one. (C2405981 2007).Fixed: Cannot modify attribute image when change tracking is on. (O129980 2009).Fixed: Slave repository will not synchronize after Java API update and slave repository will not synchronize after iViews update. (O871026 2008).”Fixed: Server crash when trying to run a workflow with validation that has a corrupted expression. (O964577 2008).Fixed: Changed passwords were not synchronized from Master to Slave. (O9978 2009).Fixed: RC_CM_RECORDNOTFOUND error appeared and syndication aborted if records selected by a syndication query were deleted or merged while a syndication that included qualified lookups was ongoing. (O857965 2008).Fixed: A negative score was received on matching caused by records trying to match themselves. (O45294 2009).Fixed: After record merge, the matching score display was not correct. (C687537 2009).Fixed: New records created by merge were being added to a workflow job (C636116 2009).The fix will update the unlaunched jobs when the records are merged.The fix will prevent the merge if there are source records that are in more than one workflow job.”Fixed: After verifying the repository user gets the following error message: “$$$ Non-Fatal error (1357): Hierarchy Tabelle A2i_16’s primary display Field F2 8 must be at least 30 characters long.” (O28506 2009)Fixed: A Partial Set Error and a value exception was received on import via MDIS due to calculated text qualifier field values incorrectly getting written to the DBMS, leading to inconsistencies between the cache and the DBMS.Fixed: Added a safe silo mode that may perform as well as turning silos off for import. (O900256 2008)When an import fails, it’s silos can be turned off by setting mds.ini BULK_IMPORT_SILO_LEVEL=0As an alternative, one may leave it at =3 and then instead set Safe Silo Mode=True.When a bulk import operation fails due to referential integrity problems, the problem should go away when either Silos are turned off or safe silo mode is turned on.Fixed: Records failed to import because MDS and Import Manager didn’t use the same symbol for concatenating display fields which caused an incorrect matching (O1094543 2008).Fixed: Qualified table calculated fields were not re-calculating. The problem is that calculated qualifier field that depends on other calculated field, just gets the current value of the depended calculated field instead of recalculating the depended calculated field. During load update indexes, this dependent calculated field may not have its value computed yet. The fix involves recalculating the dependent calculated fields. (O2825537 2008).Fixed: Role with constaints on look up couldn’t check out a new record (O175083 2009).Fixed: MDS ignored the difference between upper and lower cases when importing to case sensitive fields. (O21711 2009).Fixed: MDS now verifies that the Database Character Set is Unicode and reports an error if it is not. An error is now logged when a non-Unicode character set is in use. (O1070962 2008).Fixed: Presentation text now has a record ID strand which further enables the ability for granular refresh of pieces within the text. (O1034485 2008).Fixed: When user duplicates record and a validation with “Automatic Execution=Error” is triggered, the error message is general and not the error message defined by the user. Now the error message that the user defined for the validation will be generated.(O968449 2008).Fixed: Importing multilingual Text HTMLs from Excel to Data Manager failed (O69248 2009).Fixed: Publisher crashed when moving nodes around in Taxonomy mode of Data Manager while a Publisher session was open with the Family Tree. (O842070 2008).Fixed: “Record Add” workflow triggers “Record Update” Workflow (O226500 2009).Fixed: Cascaded workflow with trigger Update was launched twice, once because of the cascade and once because of the update (O179318 2009).Fixed: Reconnect to Photoshop if connection breaks. Occassionally, the connection between our imaging library and Photoshop becomes broken. Previously, this was detected and an error would be returned. With this fix, the imaging library tries to reestablish the connection with Photoshop, and only if the connection cannot be restablished is an error returned. NOTE: it is still not known why the connection with Photoshop gets broken in the first place. (O716981 2008).Fixed: Improved MDM performance in the following areas (C1071945 2009).Opening Data ManagerKeyword Search using containsRestoring searchesFixed: Improved MDM performance of synchronise slave following import and syndication.

MDM Layout Server
Fixed: A NULL access violation was corrected with a check first. Although the crash is fixed and a template node is now generated, there is still further feature development yet to be done in the template area (O4879451 2008).Fixed: A small code addition was made to make the Presentation Object Snapshots pane behave better in reflecting up to date aspects of the snapshot for the selected item. There are still limitations with this pane in the UI for 7.1. For example, the generated preview must be visible for the Presentation Object Snapshots pane to work.Fixed: Adding a record to a stack pivot family corrupted the title. A bug in Publisher caused previous text stores not to be cleared out on re-select. MDLS also uses F5 to clear the cache when record sets are added to enable the calculated data to be correctly reflected in Publisher immediately(C2884244 2008).Fixed: Copy Block Expression window has been made ML resizable (C2715446 2008).

MDM Syndicator
Enhanced: A new menu item called “Update Maps” was added under “File” menu. This enables the user to update all the syndication maps at once.If there is any change to the current map, Syndicator will pop-up a message box to ask user if he wants to save the current map or not, and save/discard changes before the update operation.If there is no change to the current map, Syndicator will start updating maps.When the update operation is finished successfully , a pop-up message will show “Total n syndication map(s) updated.If there are no out-of-date syndication maps in the repository, a pop-up message will show “All syndication maps are up-to-date, no update needed!”Fixed: Refreshing output items pane should preserve the items order (O1045677 2008).Fixed: Syndicating Images/Videos/PDFs meta-fields is now re-enabled as it was in MDM 5.5. No actual BLOBs can be syndicated (O99616 2009).”Fixed: The Remote keys iterator could advance before the record syndication started. This caused the first record to be skipped in the preview. Syndication to a file was not affected and produced correct results (C3330356 2008),(C3376782 2008).Fixed: Do not generate remote keys when “suppress records without a key” property is checked (C4780661 2008).Fixed: When a user does not have sufficient rights to save a map, he should get proper message instead of “duplicate map” one. (O990471 2008).Fixed: Syndication logs from Unix machines can’t be viewed using the Console. (O1073713 2008).Fixed: Removing a field may cause assertion in DEBUG and remove item mappings in RELEASE during syndication map import or transport (O175001 2009).

MDM Publisher:

Enhanced: Improved UI includes:Condensed tabs.Expand/Collapse properties in the Item Layout Pane.Default item slot height in property panes.No default icons in dialogsIcons in tabsLayered tabsEnhanced: When you select ‘Add Non Family-> Text’ from spread pane, the item is added at the location where you clicked.Enhanced: Added a new type of presentation called Recordset Publication. When creating a Recordset Publication you need to specify a hierarchy field in the main table that the structure will be based upon. You will thereby obtain a pruned down hierarchy with leafs of record set publication nodes based on the core Data Manager hierarchy. Furthermore, the record set in the record set publication node is also pruned down as determined by the mask specification.
In order to create “Recordset Publication” type presentation:Select the “Recordset Publication” in the combo box.Select a hierarchy table from the “Organize by” box.You can select a mask with more than one “Organize by” option.The Presentation Hierarchy tree should now be partitioned by the organized field, according to the Hierarchy.Enhanced: Swatches Elements are now displayed in exported XMLs.Enhanced: Added a new MDM Hierarchy window to InDesign plugin. This displays the MDM hierarchy tree and will show the leaf nodes corresponding to items you select in InDesign.Enhanced: Added a new column “Adopt” to Records tab, enabling configuration of adopted relationships as meta data to the presentation. Any record can be configured as the parent adaptor of any set of children available in the Records pane. If the Relationship field is shown, then the value for such an adopted child will expand.Enhanced: Added a new option to InDesign #Ignore Image Refresh# for Image field . This option allows refresh on just the text parts of the item such as image description, image name, footnotes, etc.Enhanced: Added #Synchronize Publication Tree# under #MDM Hierarchy# window to InDesign.Enhanced: The Hierarchy tree in InDesign displays icons that indicate what the MDM synchronize status was last time the tree was synchronized.
Icons:Synched (kRegistrationMarkIcon)Could not synch (kQuestionMarkSmallIcon)Synched but node id has changed (kChainIconNotConstrained)Synched but name has changed (kChainIconConstrained)

MDM Webservices
Enhanced: MDM Webservices can now create, retrieve, update and delete tuples.Enhanced: WAS 710 is now supported for use with MDM Webservices.Enhanced: Improved logging and tracing to further comply with SAP standards.

MDM Workflow
Enhanced: Wait step was added to Workflow.The records coming from syndication or import and one of the record field contains the date that a Wait step should wait for. The dates may be different for different records.When the user moves the workflow job to a Wait step, the user can choose a date at run time.Wait Step Properties:
Name
Description
Assignee Type: User or Role (enables more users to maintain the wait step)
Assignee Users
Assignee Roles
Wait Type:
GM Time Field or Literal Date FieldGM Time Field
A combo box enabled only when the Wait Type is the GM Time Field. It lists all the GM Time type fields in the table. With GM Time field, the user can input both the date and time.
During execution time, it reads the date and time from the GM Time field of the records and uses it as the wait until time.
In Data Manager, the GM Time field is displayed in either the local or the GM time zone, depending on the setting Configuration->Options->Display time stamp fields in local time.
Literal Date Field
A combo box enabled only when the Wait Type is Literal Date Field. It lists all the Literal Date type fields in the table.
The step reads the date from a Literal Date field of the records in job.
In Data Manager, the Literal Date field is not affected by the setting Configuration->Options->Display time stamp fields in local time.
The time of the day is 00:00:00 am in the MDS server local time zone.Wait step cannot be added to Group step.Fixed: When the Max Records is set to 0, it should only disable the launching based on the number of records. Similarly, when the Max Time is set to 0, it should only disable the launching based on the time. (C4584418 2008).Fixed: It was possible to assign a record to more then one workflow job (C2967441 2008).Fixed: When a workflow job rolls back records at the Stop step, it used to work only when the current user is the job owner. The fix removes this restriction. (O1050941 2008).Fixed: Fixed the problem that the Workflow stencil could not be restored if it was closed. (O889532 2008).Fixed: User A could add a record to workflow although record was already checked out exclusively by user B (C4220592 2008).

Please refer also to the more detailed release information on the SAP Service Marketplace (see http://service.sap.com/installmdm71) and the Release Restriction Note No 1244358 for more information.
Upgrade
If you are upgrading from earlier MDM versions find all necessary information in the MDM 7.1 Upgrade Guide, available on Service Marketplace. (see http://service.sap.com/installmdm71)

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment