Author: admin

Introduction

A month back, I successfully completed my first employee central implementation project for a world’s leading bike manufacturer based out of USA. And the entire implementation period has been a great learning experience for me. It has been almost like starting afresh on a new product solution. And here I am, after a long hiatus, to share a knowledge capsule with all of you.

Client Requirement

Our client wanted to hide the field “Date of Death” in Biographical Information (personInfo) portlet in People Profile for all except HR Admin and HR Technology Support team. Below screenshot shows the field I am referring to.

The fields in SuccessFactors are generally hidden using Role Based Permissions (RBP). However, in case of Biographical Information (personInfo) portlet, you can either hide or view the whole portlet using RBP, but not do the same for fields within the portlet. This is because RBP doesn’t provide options for fields within Biographical Information (personInfo) portlet. Please refer the below screenshot for your reference.

Solution

Since I couldn’t use RBP to restrict visibility of field “Date of Death” in Biographical Information (personInfo) portlet, I leveraged business rule to achieve this requirement.

Before that, we need to create a permission group that will include members who will have access to view the field “Date of Death” in Biographical Information (personInfo) Portlet. You can either search for “Manage Permission Groups” in the search bar or follow the below path to open up “Manager Permission Groups”.

Admin Center > Manage Employees > Set User Permissions > Manage Permission Groups

I created a permission group called “Group_View_Date_Of_Death” and added the eligible members in the group. I have used username as the category for the People Pool for this document. However, I would recommend you to use category like job classification or department etc. to keep the permission group dynamic. Below screenshot shows the permission group I created.

 

The next step is to create business rule using configure business rule. You can either search for “Configure Business Rule” in the search bar or follow the below path to open up “Configure Business Rule”.

Admin Center > Company Settings > Configure Business Rules > Create New Rule

I created the rule as shown in the below screenshot.

Since we have to hide a field in Biographical Information (personInfo) portlet, the base object to be used is Biographical Information (personInfo) Model and not Biographical Information (personInfo).

The logic in the rule implies that if the logged in user is not in the permission group – “Group_View_Date_Of_Death”, then the field – Date of Death – is not visible to the user.

We need to assign the business rule to the Biographical Information (personInfo) portlet. You can either search for “Manage Business Configuration” in the search bar or follow the below path to open up “Manage Business Configuration”.

Admin Center > Manage Business Configuration > personInfo

The business rule has been added to the Biographical Information (personInfo) portlet with event type as “onView” and base object as “Biographical Information Model” as shown in the screenshot below:

With this, the solution configuration is complete. Let us test the solution for different scenarios.

Solution

Scenario 1: User in the permission group “Group_View_Date_Of_Death” viewing “Date of Death” in his People Profile.

Aanya Sing (username: sfadmin) is a part of the permission group “Group_View_Date_Of_Death” and is able to view the field “Date of Death” in her People Profile. Please refer the below screenshot.

 

Scenario 2: User in the permission group “Group_View_Date_Of_Death” viewing “Date of Death” in People Profile of another employee.

Aanya Sing (username: sfadmin) is a part of the permission group “Group_View_Date_Of_Death” and is able to view the field “Date of Death” in People Profile of employee “Pieter Evert”. Please refer the below screenshot.

Scenario 3: User is not in the permission group “Group_View_Date_Of_Death” and trying to view “Date of Death” in his People Profile.

Pieter Evert (username: PEvert) is not a part of the permission group “Group_View_Date_Of_Death” and is unable able to view the field “Date of Death” in his People Profile. Please refer the below screenshot.

Scenario 4: User is not in the permission group “Group_View_Date_Of_Death” and trying to view “Date of Death” in another employee’s People Profile.

Lisa Felix (username: lfelix) is not a part of the permission group “Group_View_Date_Of_Death” and is unable able to view the field “Date of Death” in People Profile of Pieter Evert. Please refer the below screenshot.

Here, I come to the end of this knowledge artifact. I hope this solution approach will be helpful to restrict visibility of fields in portlets like Biographical Information.

Warm regards,

Vivek Barnwal

******************************************************************************************************************

You can also refer to other knowledge artifacts created by me at the below link:

One Stop Shop of my Knowledge Artifacts in SAP HCM http://bit.ly/2nNt0wG #SAP #SAPCloud #AI

#ICYMI: #InternetofThings #AI https://goo.gl/fzd4rR #Technology #IoT #ML

Hospitals do their best to keep us alive every year, but there is always room for improvement. To be honest, they do come out with technological advancements all the time. We’ve just never seen something so powerful as deep learning before.

It will introduce changes we could never have imagined was possible a few decades ago. In the future, you’ll feel safer if anything is wrong with you. Here is a quick rundown of ways it’s being incorporated into our health institutions at the moment.

1. Chatbots Are Starting To Help Patients Out

If you searched for a Canadian pharmacy online you might find yourself talking to a chatbot. Websites are using them extremely effectively right now. It seems like hospitals have been quick to jump on the bandwagon too.

Do you have any idea how they actually work? We can look at an example you’ll find in a hospital setting. You might need to see a doctor because you’re sick, but you don’t necessarily know which one to speak to.

You’ll be able to communicate with a chatbot capable of answering thousands of questions. The amount will keep increasing as it learns. When you are finished you’ll be referred to the right doctor.

2. Preventing Emergencies Before They Occur

A hospital doesn’t have a room with crystal balls, but deep learning is allowing it to predict the future. It’s now possible to prioritize patients when they turn up looking for treatment, which doesn’t sound too fair.

Fortunately, it’s saving lives and that is the number one priority. It can assign beds and dispatch ambulances quicker than ever before. Also, to save money it will discharge patients instead of letting them stick around for ages.

The chances of you surviving a medical emergency will increase because of software. If you’re in hospital it could predict something bad is going to happen hours in advance, so it could be prevented altogether.

3. Knowing How To Treat Patients Effectively

Do you know anyone who suffers from a certain condition with more than one treatment available? For example, if someone has cancer they could have radiation therapy, chemotherapy, or a transplant.

Hospitals will have systems in place to determine which one is right for you. The one they choose should keep you alive while minimizing your risks. A computer using millions of data points is more trustworthy.

People will see better outcomes as time goes on. It can work out more advanced things too, but it needs enough data to see patterns. It can determine the right medication you’ll need for an illness if there are dozens of options available.

Healthcare Is A Very Delicate Industry

Deep learning will advance quicker when it comes to things like fraud detection and marketing campaigns. It’s because healthcare is a lot more delicate and we need to be careful. It’s literally a case of life or death.

It’s still impressive how things are progressing so far. We’re only going to see deep learning used in even more capacities as time goes on. If you’re lucky it will help prolong your life an extra couple of years. http://bit.ly/2nKatS5 #SAP #SAPCloud #AI