Selected Product Hub Bug Fixes in This Update
This update includes some bug fixes that can change the way Oracle Product Hub works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.
Visibility of Product Management Quick Actions on the Home Page
Before update 25A, the following quick actions under Product Management on the Home page were visible even if you didn't have the necessary privileges to access the tasks:
- Manage Engineering Items
- Manage Commercialization Change Orders
- Manage Engineering Change Orders
- Manage New Item Requests
- Manage Documents
- Manage Ideas
As of update 25A, these quick actions will be visible only if you've been granted the privileges to access the tasks.
Oracle reference: 37029408
Visibility of Template Items in Product Management Redwood Search
Before update 25A, template items were returned in the search results when searching for items using the Product Management Redwood search. After update 25A, template items won't be returned in the search results. For this change to take effect, you must rebuild the item index after update 25A.
Oracle reference: 36482696
View the History of All Data Changes for Item Attributes
Before update 25A, under some conditions, the History tab on the Edit Items page didn't display a few data changes made to item attributes. After update 25A, you can view all the data changes for item attributes enabled for audit.
Oracle reference: 36998055, 37103651, 36750237, 37135417, 37365622, 37504408, 37326190, 37549794, 37555553
Modify Predefined Healthcare Attribute Groups and Attributes
Before update 25A, healthcare attribute groups and their corresponding attributes were predefined as Protected and hence, you couldn't edit their properties. After update 25A, these attribute groups and attributes are modifiable. Also, you can add new attributes and add or update context usages in a healthcare attribute group. If you attempt to save changes for properties that can't be updated, an error message is displayed. You can't delete a predefined healthcare attribute group or attribute.
To add or remove values from a value set, you can create a new value set and associate it with the corresponding healthcare attribute. However, before updating the value set, review if you've created items and populated values for the attribute. Also, review all the related references. After updating the value set, make sure that all associated references are updated. For instance, if a value from the older value set is being used in an Item Rule, modify the rule suitably and save the rule set. Or use the Optimize Rules action to regenerate the rule. If you've a Smart spreadsheet that contains the healthcare attribute, generate the spreadsheet again and select values from the new value set to proceed with a successful import.
Oracle reference: 37514151
Modify Healthcare Library per GUDID Standards
Before update 25A, the healthcare attribute group GUDID Storage Conditions (ORA_GUDID_STORAGE_CONDITIONS) had the following attributes with first four as the unique key:
- Storage and Handling Type
- Low Value
- High Value
- Unit of Measure
- Special Storage Conditions
After update 25A, a new unique key attribute called Sequence Number has been added to this attribute group. The Storage and Handling Type, Low Value, High Value, and Unit of Measure attributes have been marked as non-unique. This change enables you to create Special Storage Conditions records and values aren't needed for Low Value, High Value, and Unit of Measure attributes. The predefined import map Item Enrichment with External Healthcare Catalog has also been accommodated with this new Sequence Number attribute.
To adhere to the GUDID standards, the length, precision, and scale has been adjusted for the healthcare attributes as listed in the following table:
| Attribute Group | Attribute Name | Before Update 25A | After Update 25A | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Old Value Set | Old Length | Old Precision | Old Scale | New Value Set | New Length | New Precision | New Scale | ||
| Healthcare GUDID Primary | Labeler D-U-N-S Number | ORA_HC_20_CHAR | 20 | ORA_HC_LABELER_DUNS | 15 | ||||
| GUDID Package Device Identifiers | Package Type | ORA_PACKAGETYPE_30_CHAR | 30 | ORA_HC_20_CHAR | 20 | ||||
| Premarket | FDA Premarket Submission Number | ORA_HC_20_CHAR | 20 | ORA_HC_10_CHAR | 10 | ||||
| Premarket | Supplement Number | ORA_HC_20_CHAR | 20 | ORA_HC_SUPP_NUMBER | 4 | ||||
| FDA | Product Code | ORA_HC_10_CHAR | 10 | ORA_HC_PROD_CODE | 3 | ||||
| FDA | Product Code Name | ORA_HC_500_CHAR | 500 | ORA_HC_300_CHAR | 300 | ||||
| Healthcare GUDID Primary | FDA Listing Number | ORA_HC_20_CHAR | 20 | ORA_HC_FDA_LIST_NUM | 7 | ||||
| GMDN Attributes | GMDN Name | ORA_HC_500_CHAR | 500 | ORA_GUDID_GMDN_NAME | 150 | ||||
| GUDID Size Attributes | Size Type Text | ORA_HC_500_CHAR | 500 | ORA_HC_200_CHAR | 200 | ||||
| GUDID Storage Conditions | Special Storage Conditions | ORA_HC_500_CHAR | 500 | ORA_HC_200_CHAR | 200 | ||||
| GUDID Package Device Identifiers | Quantity Per Package | ORA_HC_QUANTITY | ORA_HC_QUANTITY | 9 | |||||
| ORA_GUDID_DEVICE_COUNT | Device Count | ORA_GUDID_DEVICE_COUNT | ORA_GUDID_DEVICE_COUNT | 7 | |||||
| GUDID Size Attributes | Size Value | ORA_DEVICE_SIZE_VALUE | ORA_DEVICE_SIZE_VALUE | 38 | |||||
| GUDID Storage Conditions | Low Value | ORA_GUDID_STORAGE_VALUE | ORA_GUDID_STRG_VAL | 6 | 4 | ||||
| GUDID Storage Conditions | High Value | ORA_GUDID_STORAGE_VALUE | ORA_GUDID_STRG_VAL |
6 |
4 |
||||
If you have a smart spreadsheet that contains any of the listed healthcare attributes, regenerate the spreadsheet to proceed with a successful import.
Oracle reference: 37514151
Steps to Enable
You don't need to do anything to enable this feature.