Are you leveraging the full potential of Oracle Agile, or are you stuck in the past? Upgrading from older versions like Agile 8.5 or earlier to Agile 9.3.6 can elevate your user experience significantly. While it’s easy to get caught up in backend functionalities, the enhancement in user interface and user experience (UI/UX) offered by newer versions like 9.3.2 and beyond shouldn’t be ignored. Enhancements in Oracle Agile boost adoption, productivity, and job satisfaction while driving innovation to streamline operations effectively. Discover the top 10 features found in an Agile PLM upgrade that have users, change analysts, and administrators buzzing with excitement.
Top 10 Features Found in an Agile PLM Upgrade
10 – Object Edit Conflict Resolution
Previously, clicking ‘Save’ last won if two users were editing the same object simultaneously, overwriting the first user’s edits.
Besides irritating users, this could easily result in incorrect data being stored in the object.
The new SmartRule “Object Edit Conflicts” allows the system administrator to control the behavior by selecting one of the following options:
- Allow: continues the previous system behavior explained above.
- Warning: notifies the second user that they will be overwriting another user’s saved changes. The user can then decide whether to continue or cancel their Save.
- Disallow: forces the second user to cancel their Save action, refresh the object, and make their changes again.
9 – Removed Reset Password Option for LDAP Users
Before 9.3.3, LDAP users had the Change Password feature enabled for their User ID.
This used to be a big annoyance because, when synced to your company’s Active Directory, users cannot change their LDAP password through the Agile interface.
In version 9.3.3, Oracle has disabled the Change Password feature for LDAP users, effectively eliminating confusion and frustration.
8 – Navigator Expansion
We have added additional object tabs and object types to the Navigator functionality, greatly expanding its navigational usability and drag-and-drop capabilities. Previously, when pushing an Item to the Navigator it only included the BOM tab.
Now, you can browse through additional tabs from the Navigator, such as the Relationship, Manufacturers, Change History, or Pending Changes tabs.
New object classes that can be pushed to the Navigator include Changes, Product Service Requests, Quality Change Requests, Declarations, Specifications, Part Groups, and Sourcing Projects.
7 – PPM Gantt Chart Improvements
If you’re a PPM user, you’ll find substantial Gantt chart enhancements in Agile version 9.3.5.
You can now view and edit multiple projects in the same Gantt session using the new Project Navigator.
Improved Tooltips, custom filtering, and enhanced views for Task Assignment, Resource, and Comparative Gantt contribute to a more streamlined interface and improved efficiency. This leads to a more satisfying user experience.
6 – Controlled Visibility of PX access from Actions or Tools and Settings Menus
Process Extensions (PX) provide handy automation for users, but the ability to execute them sometimes needs to be restricted.
Before 9.3.6, any user could run a PX accessed from the Tools and Settings menu or from the Actions menu of objects that the user could discover and read.
Now, the Agile administrator has the power to limit this capability exclusively to users assigned a specific role, enhancing control and security.
This can save a lot of time and annoyance for users and administrators who have to undo changes made by the inappropriate triggering of a PX.
Click here to see every feature that was added to the 9.3x generation (9.3.3 to 9.3.6) of Agile PLM.
5 – Edit Search Criteria Button in Web Client Searches Folder List
Previously, you had to run the search first if you wanted to edit a saved search before Agile 9.3.6. Then you could edit the search criteria or format options.
For large searches, this could end up being a serious time waster. Now each search has an Edit Search button that lets you edit the search before running, if you choose.
4 – Save As New Search Bug Fix
Users love to save searches. It saves time and provides consistency.
Before 9.3.3, the “Save As” process had a bug when using saved searches to create a new search.
Instead of saving a new search, it overwrote the original one with new parameters, affecting criteria and output formatting.
Star Trek fans, if you are thinking that this sounds a bit like the Genesis Project, you are right. Users who constantly had their saved searches overwritten by this particular bug are delighted to see it has been flattened!
3 – New Rev as an Entry and an Exit Required Field on Workflows
Administrators can now make the New Item Revision field a required field at any Change Order status. Before 9.3.6, it was automatically checked before moving to the first released status.
Now, by simply running the standard status audit, you can ensure data is entered before the change undergoes review, streamlining the process.
2 – Introduction of Large Text Fields
This much-awaited new field type has finally arrived. You can utilize them as either very large multi-text fields or configure them to allow journal entry that behaves like a blog.
Unlike multi-text fields that max out at 4,000 characters, Large Text fields can contain up to 2 million characters. They can also be configured for rich text or HTML formatting options, such as font format, and the ability to add tables, images, URLs, etc.
Large text field types are a great way to incorporate data and communications that you may currently be storing in a company WIKI or other programs external to Agile.
Now, directly manage your data in Agile to seamlessly incorporate it into your Product, Change, Quality, Compliance, NPI, and Program Records, enhancing integration and accessibility.
1 – Workflow Audit Screen Enhancements
Many users find this Agile PLM update feature alone worth the price of admission. If you write or process change orders or other routable objects, you’ll love these updates to the Workflow Audit Screen:
- Each error and warning is now a hyperlink that takes you directly to the problem. Additionally, it opens the tab in entry mode. This works whether the audit error is about a field on the routed object or the affected item.
- Click the error/warning for “Unreleased Child” messages to add the missing part to the Affected Items tab in the change order.
- They’ve added an ‘Audit’ button directly to the Workflow Audit Screen for enhanced accessibility and efficiency. This works nicely to refresh long message lists and remove the errors and warnings already resolved.
Agile PLM Upgrade Grandfather Clause
Going forward, when you upgrade Agile PLM, all previously released features are automatically added to your software. Upgrade your environment from 9.2 to 9.3.6 for added features and fixes in each release version (9.3, 9.3.1, 9.3.2, and beyond).
Add to that, Oracle’s recently improved update model affords users the option, every other month, to install a light Release Update Pack (RUP).
From a user’s perspective, there have been some pretty handy improvements written into these past few releases.
Conclusion
In conclusion, upgrading your Oracle Agile PLM system to newer versions, such as Agile 9.3.6, presents a significant opportunity to enhance user experience, streamline operations, and drive innovation. The top 10 features found in an Agile PLM upgrade offer substantial improvements in functionality, usability, and efficiency. From resolving object edit conflicts to enhancing workflow audit screens, each feature contributes to a more productive and satisfying user experience. Leveraging these enhancements not only boosts adoption and job satisfaction but also ensures that your organization stays current with the latest advancements in PLM technology.
Disclaimer: The views and opinions expressed do not necessarily reflect the views and opinions of Domain Systems. The author takes full responsibility for the views stated here.
[…] into new, connected PLM. A PLM without obvious borders, and one which connects users and decision-makers to the vast amount of valuable data in a kind of giant […]