ORACLE CORPORATION

PeopleSoft Fluid Related Action Standards Fluid User Experience

November 2015

2

PeopleSoft Fluid Related Action Standards

Copyright © 2015 , Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

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.

3

Overview .......................................................................................................... 4

Access to Related Actions ..................................................................................... 4

Responsive Design .......................................................................................... 11

Mapping Between Fluid Transaction and Classic PIA Transaction ................... 12

Enabling Conditional Navigation .......................................................................... 12

Enabling Related Actions .................................................................................... 19

Using Buttons Versus Using Related Actions ......................................................... 19

4

Overview This standard describes the UI guidelines for Related Actions in Fluid based applications. The guidelines cover their usage on tablets, smartphones, laptops, and desktops.

Access to Related Actions

To access Related Actions, tap the Related Actions icon, which is available only when a related action is configured from the current transaction.

The following examples show how users can access Related Actions from various locations in fluid mode.

Accessing Related Action from Application Header

The Related Action icon appears next to the Employee name:

Figure 1: Accessing related actions from the application header

Accessing Related Action in a Grid

In this example, the Employee Photo is a column in the grid, and the Related Action icon appears next to the employee name:

5

Figure 2: Accessing related actions in a grid

You may want related actions to have a column in a grid, as shown in this example:

Figure 3: Accessing related actions in a dedicated column

Accessing Related Actions from a Card View

In a card view, the Related Action icon appears near the right edge of the card header:

Figure 4: Accessing related actions from a Card view

6

Accessing Related Actions from the NavBar

When using the second level of the NavBar, you can provide access to related actions as shown here:

Figure 5: Accessing related actions from the NavBar

If the row on the second level is tappable, it is recommended that you not use related actions to avoid mistapping. In the previous example, related action access is provided on the second level because the row is not tappable. For performance reasons, the related actions list is loaded only after the user taps the Related Actions icon.

Do not use related actions on the first level of the NavBar.

Accessing Related Actions from Search Results

You can configure related actions to appear with the Search results, as shown in this example:

7

Figure 6: Accessing related actions from Search results

Accessing Related Actions from Company Directory

In the Company Directory/Org Chart, the Related Action icon appears in the selected node next to the name (only if you are authorized to take configured related actions):

8

Figure 7: Accessing related actions from Company Directory/Org Chart

Accessing Bulk Related Actions

In a grid, you can configure related actions to be applied to multiple rows. The following example shows bulk related actions in a grid:

9

Figure 8: Accessing bulk related actions

Tapping a Related Action You initiate a related action by tapping it after accessing the list of related actions through the Related Action icon.

In most cases, a related action transfers the user to the respective transaction component to perform the action. In some cases, the related action opens in a modal window or it can run in the background.

In the following example, when the user taps the Performance related action from the Personal Details fluid page, the user is transferred to the Performance component:

Figure 9: Tapping a related action (1 of 2)

10

Figure 9: User is transferred to the Performance component (2 of 2)

In this example, when the user taps the Notify Resource related action, it opens in a modal window:

Figure 10: Tapping a related action, Notify Resource (1 of 2)

11

Figure 10: After tapping the related action, the component opens in a modal window (2 of 2)

Use a modal window for related action when it is important to keep the user in the current transaction once the related action is complete or when the current transaction provides required context to complete the related action.

Note: When the related action that opens a modal window is tapped from the NavBar, the NavBar should automatically be dismissed.

Responsive Design Related actions automatically render in the various form factors. The following examples show what two of the previous examples look like in a small form factor (smartphone).

12

Figure 11: Two examples of related actions in small form factor/smartphone

Mapping Between Fluid Transaction and Classic PIA Transaction Until all the PIA transactions are converted to corresponding Fluid transactions, you need to evaluate whether the Related Action from a transaction needs to take the user to the respective PIA transaction or the Fluid transaction.

Enabling Conditional Navigation

The following documentation details how Conditional Navigation works and how PIA/ Fluid component mapping is done. Each Fluid transaction must be reviewed to determine whether mapping between the Fluid transaction and the Classic PIA transaction is needed.

When Fluid transactions and Classic PIA transactions are mapped properly, users will navigate from one fluid component to another fluid component and have a consistent user experience with the same look and feel. Ideally, users will not see a mix of Fluid and Classic PIA transactions as they navigate the PeopleSoft system.

The guidelines for enabling Conditional Navigation mapping are as follows:

13

1. As a general guideline, if a Fluid transaction coexists with a respective PIA transaction (it may have only partially or completely replaced the PIA transaction), then the Related Action and menu navigation should take the user to the Fluid transaction.

Note: As an exception, you may want to transfer users to a Fluid transaction when they select the related action/menu item from a Fluid transaction and to the respective PIA transaction when they select the related action/menu item from a PIA transaction. Evaluate these scenarios according to your requirements.

If you want to give users access to both Fluid and PIA (Classic) components, do not implement Conditional Navigation because it will always take users to the fluid component and they will be forced to add a new CREF at their end to provide access to the PIA (Classic) component.

Note: PeopleTools allows you to add PeopleCode to ignore Conditional Navigation and to take users to respective PIA (Classic) components.

2. If a number of PIA transactions are replaced with a single Fluid transaction, then set up the Conditional Navigation such that only one related action and menu-label appears to take users to the respective Fluid transaction.

The examples that follow display the Personal Details Fluid transaction (related action and menu label) that replaces these Classic PIA transactions:

• Personal Information Summary

• Home and Mailing Addresses

• Phone Numbers

• Email Addresses

• Instant Message IDs

• Emergency Contacts

• Name Change

• Marital Status

• Ethnic Groups

Note: The Conditional Navigation for Menu and Related Actions should be in sync, that is, it should use the same labels and access for the items in both the menu and in related actions.

14

Examples

Figure 12: Example of Classic PIA menu items before Conditional Navigation (1 of 2)

15

Figure 12: Example of Personal Details Fluid transaction that replaced PIA transactions in the Classic menu based on Conditional Navigation setup (2 of 2)

Figure 13: Personal Details Fluid transaction that replaced PIA transactions in NavBar based on Conditional Navigation setup (1 of 2)

16

Figure 13: In small form factor, Personal Details Fluid transaction that replaced PIA transactions based on Conditional Navigation setup (2 of 2)

17

Figure 14: Example of related actions before Conditional Navigation

18

Figure 15: Example of Personal Details Fluid transaction that replaced many related actions based on Conditional Navigation setup (1 of 2)

19

Figure 15: After selecting Personal Details related action, user is transferred to the Personal Details Fluid transaction (2 of 2)

Enabling Related Actions

In general, when you are in a process (for example, Guided Self Service and Approvals), do not allow Related Actions so that the main transaction is not abandoned halfway through.

However, if you have Save for Later functionality in a process and you are not required to complete the process in the same session, then you may allow Related Actions.

For any new Fluid transactions and existing PIA transactions converted to Fluid, you must evaluate:

• Whether Related Actions from the transaction should be enabled.

• Whether a Related Action to this transaction should be enabled in other transactions.

Using Buttons Versus Using Related Actions

Use a button for an action that is intrinsic or a primary action for the transaction. The primary actions should be prominently displayed so that they are highly visible and accessible to users. If such actions are listed under the Related Actions icon, users will have trouble locating them, which will not be a good user experience.

In the following example, buttons are used for the primary actions Approve, Deny, and Pushback so that these are readily available for user to take required action:

20

Figure 16: Buttons are used for the primary actions like Approve, Deny, and Pushback

Related actions are not primary to the transactions, but users may want to access their functionality from within a given transaction. For example, while checking Benefits, a self-service user may also find it useful to access their last month’s paycheck to ensure that they were paid correctly. In this case, using a Related Action enables the user to navigate quickly to the Paycheck component, which is not the primary task on the Benefits component. Related Actions provide quick access to a functionally useful action that is related to the primary action.

Figure 17: Related Actions are used for the secondary actions to enable quick navigation