Oracle Fusion Applications

Human Capital Management

Transaction Design Studio

What It Is and How It Works

WHITE PAPER / FEBRUARY 16, 2019

DISCLAIMER
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.

Transaction Design Studio – What It Is and How It Works Page 2

Table of Contents
Table of Contents

About Transaction Design Studio ............................................................ 5

Business Value of Transaction Design Studio........................................ 6

Accessing Transaction Design Studio .................................................... 6

Configuring Rules...................................................................................... 8

Basic Details ................................................................................................................................ 8

Common Parameters .................................................................................................................. 9

Show or Hide Regions ................................................................................................................10

Page Attributes ...........................................................................................................................13

Flexfields ....................................................................................................................................14

Managing Rules ....................................................................................... 15

Example of Rules Evaluation ......................................................................................................15

Ordering Rules ......................................................................................... 16

Transaction Design Studio – What It Is and How It Works Page 3

 Using Transaction Design Studio with Page Composer .............................................................17

Testing & Migrating Rules ...................................................................... 18

Testing ........................................................................................................................................18

Migrating Rules from Test to Production ....................................................................................19

Transaction Design Studio – What It Is and How It Works Page 4

ABOUT TRANSACTION DESIGN STUDIO

The Transaction Design Studio is available within the HCM Experience Design Studio in its initial BETA phase. There are
limited features and actions available to configure at this time, and you can encounter known and unknown bugs. If you run
into what appears to be a bug, please log a Service Request in My Oracle Support. If not all functionality or actions are here
yet, stay tuned for more functionality in each release.

Transaction Design Studio It allows you create rules to configure transactions and pages in the responsive user designed
pages. You can change how sections and fields are displayed, based on the user's role and the employee's business unit or
legal employer. You can:

• Control the visibility of regions and sections on the page.

• Control the visibility for attributes within a page, region, or a section.
• Change the required status of optional attributes.
• Control the availability of the questionnaire page for actions that use the guided process design.

You can create one or more rules for any page available in the Transaction Design Studio to manage your business needs.
For example:

• Make different fields visible and required in the new hire flow for employees in the US and employees in other countries.
• If employees in the US don’t get salary increases as part of a promotion, hide the salary and compensation regions for
US employees only, while making these regions available for employees in other countries when being promoted.
• Hide the Ethnicity and Religion fields from the Personal Details page for countries or legal employers that you don’t
want to store that information.

You can still modify the person spotlight and upload images for pages that use the HCM landing page design.

Transaction Design Studio – What It Is and How It Works Page 5

BUSINESS VALUE OF TRANSACTION DESIGN STUDIO

Using Transaction Design Studio is easy. The design is like any other newly designed responsive page for a seamless
experience. And when configuring a page or transaction, the sections and fields map directly to the user-facing page so you
know exactly what you’re looking at and configuring. Once you save a rule, you can quickly test it by accessing the page
from global search or quick actions to see the results of your configured rule. There’s no more guessing what part of the
page you need to edit or needing to use complex EL expressions to vary the page as when using page composer. You don’t
need a technical resource to create or maintain your rules, so as business rules change, your HR analyst can make the
change themselves.

Really complex business requirements may require you to use page composer, but in general, configuring your pages for
different populations of employees is just a lot simpler now.

ACCESSING TRANSACTION DESIGN STUDIO

The delivered Human Capital Management Application Administrator inherits the privilege Access HCM Transaction
Configurator (HRC_ACCESS_HCM_TRANSACTION_CONFIGURATOR) which gives access to the Transaction Design
Studio in the HCM Experience Design Studio. To access HCM Experience Design Studio, enable a sandbox and then
edit your pages at the Site level.

Transaction Design Studio – What It Is and How It Works Page 6

 Navigate to My Client Groups > Show more > HCM Experience Design Studio. From here, you can see all actions
available to configure using Transaction Design Studio. More actions are added in each release. You can check in the
Transaction Design Studio to see all actions available for a release.

Transaction Design Studio – What It Is and How It Works Page 7

CONFIGURING RULES
To get started, select the action you want to create. Only redesigned, mobile responsive pages are available to be
configured using Transaction Design Studio. In 19A, a smaller set of actions are available, but more actions and pages will
be added in each release. After each update, navigate to Transaction Design Studio to see new actions are available to
configure.

Click the Add button to create the rule. Transaction Design Studio may look a bit different for each action you configure.
This is because the transactional pages for each action varies, and TDS includes only configuration applicable to the
selected action.

Basic Details
These are the high level details for the rule. This includes the Name and Description which are required, and the criteria,
or parameters that determine when and for who the rule is applied. Parameters vary for each action. Only parameters
applicable to the selected action are available to set. Setting parameters is optional, you can set all or none of the
parameters. The application ignores the criteria for parameters left blank when evaluating the rule at runtime.

Transaction Design Studio – What It Is and How It Works Page 8

Common Parameters
The following parameters are common, but not all actions use all 3 of these parameters:

• Role of the user performing the action or viewing the page.

• Legal Employer of the employee being acted on.
• Business Unit of the employee being acted on.

The following parameters are only used when applicable to the selected action:

• When is the rule applied? {View other’s info / Viewing own info} is used when the page being configured is available to
both employees and other users, such as HR Specialist.
• (HCM) Action is used for transactions that use the action / action reason concept.
• Country is used when the Legal Employer does not fully support the requirement to create rules by country.

Some actions may also use additional parameters that are specific to that action.

Transaction Design Studio – What It Is and How It Works Page 9

Show or Hide Regions
For actions that include different regions, you will see the Show or Hide Regions section. For Promote, Transfer, and Hire
an Employee, for example, you see will see this section. These actions use the guided process design which includes
various regions of information. For actions that don’t use the guided process design but that are comprised of different
regions of information, you will also see the Show or Hide Regions section.

Transaction Design Studio – What It Is and How It Works Page 10

 You can’t change the order of the sections, but you can:

• Rename a section.
• Hide sections not delivered, as required.
• Make optional sections required.

For actions that use the guided process, where users can select the parts of the transaction to complete form the
questionnaire page, you can control the availability by questionnaire using the Show Questionnaire page list of values. You
know if an action uses the guided process when your users land on this questionnaire page when starting a transaction.

When you hide the questionnaire page, you navigate directly into the detail page to complete the transaction as shown.

Transaction Design Studio – What It Is and How It Works Page 11

 Note: If you previously enabled the profile option Questionnaire Displayed in Guided Processes
(HCM_TASK_CONFIGURATOR_RESPONSIVE_ENABLED), by setting the Site level value to Y, to show the
questionnaire, and have no rules defined that hide the questionnaire, the questionnaire page will display. If you then create
a rule that hides the questionnaire, the questionnaire will be hidden.

Transaction Design Studio – What It Is and How It Works Page 12

Page Attributes
When an action or page includes regions, you select the region to see a list of all attributes available. When attributes are
read only, there is no option to change the required setting.

You can’t add new attributes to a page, but you can:

• Hide fields not delivered as required.

• Make fields delivered as optional required.
• Enable descriptive flexfields segments.

Transaction Design Studio – What It Is and How It Works Page 13

Flexfields
Descriptive flexfields (DFFs) are identified by the pencil icon next to the flexfield attribute. Only DFFs are currently
supported.

To enable a Descriptive Flexfield (DFF) that has already been compiled, click the pencil.

Transaction Design Studio – What It Is and How It Works Page 14

MANAGING RULES
You can have multiple rules for the same action or page. There might be cases where employees meet the parameters
for more than one rule. When this happens, the application evaluates and applies rules.

Rules are evaluated in the order they appear in the Rules page of the Transaction Design Studio. For each rule, the
application evaluates the configured parameters. If any of the parameters don’t match at runtime, the application skips the
rule and moves on to the next one. If all parameters of a rule match at runtime, the rule is applied. If more than one rule
modifies the same region or attribute, the settings from the first rule are applied and settings in subsequent rules are
ignored.

Example of Rules Evaluation

This example illustrates what happens when employees match the parameters for more than 1 rule. Assume that the
salary and manager regions for the page being configured are delivered as visible, and grade and job are delivered as
optional.

Rule Parameters Region Configuration Page Attribute Settings

1 Role = Line Manager Hide Salary section Grade is required

Country = US, UK

2 Role = Line Manager Show Salary section

Country = UK

3 <no parameters are set> Job is required

Scenario 1: The logged in user is a line manager and is performing a transaction on an employee in the US. Rule 1 and 3
match. The salary section will be hidden and grade will be required when entering data for this employee (rule1). Job will
also be required (rule 3).

Transaction Design Studio – What It Is and How It Works Page 15

 Scenario 2: The logged in user is a line manager and is performing a transaction on an employee in the UK. Rules 1, 2,
and 3 match. The salary section will be hidden and grade will be required when entering data for this employee (rule 1).
Even though rule 2 matches, nothing from this rule will be applied since the configurations in this rule conflict with the
configurations in rule 1. Job will also be required (rule 3).

Scenario 3: The logged in user is an HR Specialist and is performing a transaction on an employee in Canada (or any
country, for that matter). Only rule 3 matches. When entering data for the employee, the salary section will be shown
(since it’s visible by default) and job will be required.

Scenario 4: The logged in user is a line manager and HR Specialist and is performing a transaction on an employee in the
UK. Rules 1, 2, and 3 match. Regardless from where the user initiates the transaction (My Team/My Client Groups Quick
Actions, Global Search, My Team, Spotlight Actions, etc.), the salary section will be hidden and grade will be required
when entering data for this employee (rule 1). Even though rule 2 matches, nothing from this rule will be applied since the
configurations in this rule conflicts with the configurations in rule 1. Job will also be required (rule 3).

ORDERING RULES
Best practice is to order rules that apply to a narrower group of employees (i.e. applies to a single country or legal
employer) first. Place broader rules (i.e. applies to all roles or all legal employers) last or lower in the list of rules. Use the
up and down arrows to change the evaluation sequence of the rules.

Note: Don’t create rules that conflict (as in the provided example). If there are conflicts, all rules may not be applied and it
will cause confusion.

Transaction Design Studio – What It Is and How It Works Page 16

 You can easily copy or delete a rule using the actions menu by clicking on the three dots on the left.

Using Transaction Design Studio with Page Composer

Before configuring any mobile responsive page using Transaction Design Studio, best practice is to remove all page
composer customizations. When you create a rule in Transaction Design Studio, the required and visibility settings you see
are based on whether the field is delivered as required or visible. It will not reflect changes you made using page
composer. When you start with a clean untouched page, using Transaction Design Studio is easy and straight forward.
Page Composer changes made prior to using Transaction Design Studio will cause confusion and inconsistency in what
you see in the application.

• Can I create a rule if Page Composer changes exist?

If you customize a section or field using page composer and then create a Transaction Design Studio rule for the same
page, the required and visibility settings in the transactional page may not match what you see in your Transaction
Design Studio rule.

Consider this example:

Bargaining Unit and Collective Agreement in the Promotions region of the Promote are delivered as hidden. You enable
both fields using page composer. When you create a rule for Promotion in the Transaction Design Studio, the visibility

Transaction Design Studio – What It Is and How It Works Page 17

 settings for both Bargaining Unit and Collective Agreement will be shown as hidden, since that is how they are delivered.
What you see in the Promotion page and what is in Transaction Design Studio will not match. To now hide Bargaining Unit
and Collective Agreement, you need to edit your Transaction Design Studio rule, and change the visibility settings for these
2 fields from ‘hidden’ to ‘visible’ and then back to ‘hidden’, and then save your rule.

• Will Transaction Design Studio or Page Composer be applied first?

If you’re modifying the same field or section on the same page using Transaction Design Studio and Page Composer
and the changes conflicts, the last change created in either tool, last will be applied.

• How do I know if changes I see on the page were made using Transaction Design Studio or page composer?

You should keep a log of Page Composer changes to avoid confusion. Visibility and required setting changes you make
using Page Composer will not be reflected in the settings you see when creating a Transaction Design Studio rules. If you
don’t have a log of Page Composer changes and your Transaction Design Studio rule is not being applied correctly, it’s
recommended that you remove all customizations from your page and start fresh.

TESTING & MIGRATING RULES

Testing
While in a sandbox, you can test your rules by exiting Transaction Design Studio and navigating to the page you just
configured. You will see the new configurations immediately and can modify them as needed. When you’re happy with
your changes, publish the sandbox.

If you see a rule you did not create, it means another administrative user created the rule and published the sandbox.
Your new rules will be applied on top of the already published rule. You can modify or delete the already published rule
from your own sandbox. But be aware that doing so may cause confusion between administrative users.

Transaction Design Studio – What It Is and How It Works Page 18

Migrating Rules from Test to Production
You migrate your design studio configurations from test to production using the Customization Set Migration tool, just like
you migrate Page Composer changes. For information about Customization Set Migration tool, refer to online help about
Importing and Exporting Customizations.

Note: When creating your customization set, for HCM customizations, only ‘Application Artifacts’’, ‘Analytics’, and ‘CRM
common components’ have to be selected.

Transaction Design Studio – What It Is and How It Works Page 19

ORACLE CORPORATION

Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA

Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com

CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0219
Transaction Design Studio – What It Is and How It Works
February 2019