Experience Design Studio Overview
Experience Design Studio provides customers with the ability to change the delivered behavior of Oracle Cloud HCM to meet the specific business needs. No two organizations are the same, which is why tis feature is a part of Oracle Cloud HCM’s out-of-the-box capabilities to provide starting blocks for organizations. By leveraging this tool, each organization can create the experience that they want for their users and their specific business processes.
June Farmer, Senior Director of Product Strategy for Oracle Cloud HCM shared why she believes customers are excited about Experience Design Studio in a video. Farmer elaborated on many of the features and benefits of the Cloud HCM product feature. She shared that through the Experience Design Studio, parameters such as their role, country, legal entity, or business unit can be used so that data or processes are presented differently to different users based. Data can also be defaulted or validated based on specific rules that reflect various company policies to prevent incorrect data entry.
Experience Design Studio is a no-code way to manage and construct additional rules that control data entry and change the behavior across different groups of people, making it easy to implement. It is also adaptable so that you can change the user experience as your business needs change. It has pre-set best practice processes and controls that are already set up as rules.
The following have flows have already been laid for users:
- Change locations
Rules are also included in Experience Design Studio to hide or display fields differently, change labels, or allow only certain field values, based on local country legislative requirements. However, the Experience Design Studio allows the user to use these constructs to create conditional rules that best support your business needs. For example, a legal entity may see different sections, fields, and labels than a business based on the rules created.
Oracle HCM Cloud is the only provider that allows customers to configure rules to reflect your specific company policies. One example is that you may not allow employees or managers to enter future data transactions. These rules can be simple or more complex rules to enforce data conditions or combinations of data across HCM Cloud.
Transaction Design Studio vs. Autocomplete Rules
Transaction Design Studio and Autocomplete Rules are both available in Experience Design Studio. To determine which to use when, it’s important to know the difference.
Transaction Design Studio – Enables you to tailor the user experience through fields & sections to show height or mandate based on action criteria
Autocomplete Rules – Elevates the user experience by allowing you to define specific criteria for default and validation across HCM products
According to an Oracle Transaction Design Studio and Autocomplete Rules video, the two differ in that the Transaction Design Studio is interface driven, allowing for a custom display of fields or regions in the UI in a specific context, and Autocomplete Rules is a data model layer extensibility framework with no direct knowledge of the UI. Autocomplete Rules are purely driven by the state of values in various fields or objects. Both are available in the Cloud HCM’s Experience Design Studio and can be used to help you engage your users and create memorable experiences for your workers.
For a quick rundown of what the Experience Design Studio allows your organization to do, take a look at these abilities:
- Configure the rules to reflect your company policies and culture
- Get started quickly using best practice business processes
- Control and validate rules as processes are in the flow of work
- Manage the look and feel of
- Digital Assistant Configuration
- Search Configuration
- Event Conditions
To see more of what this looks like within Cloud HCM and see how easy it is to use consider watching this full-length video: HCM Experience Design Studio.
The HCM Cloud Experience Design Studio is all about providing the right experience to the right user at the right time.
It empowers you to create user experiences that are easy, intuitive, mobile, and hyper-personalized. Setting up specific requirements and rules via Transaction Design Studio and Autocomplete Rules can save you time and effort downstream, as potential data issues are avoided. In addition to improving data quality, the tools of the Experience Design Studio will also help you to better guide your people.
If you’re considering a move to Oracle Cloud HCM, you may consider joining Quest’s Move to Cloud Community. If you’re already using Cloud HCM, connecting with other users is easy with Quest’s HCM Cloud Community.
For more Cloud HCM content resources, check out the Quest Learn Library.