HRSD: Practical Use Cases for Business Rules, Client Scripts, UI Policies, UI Actions and other

[sarthakkach]

Hi Everyone,

I am currently working on the HRSD module and would like to understand in which practical scenarios we typically use the following configurations:

• Business Rules

• Client Scripts

• UI Policies

• UI Actions

Specifically, I’m looking for real-time HRSD use cases (like HR Case Management, Lifecycle Events, HR Services, etc.) where each of these is most appropriate.

For example, when should we prefer a Business Rule over a Client Script in HR cases? In what situations are UI Policies sufficient instead of scripting? Where are UI Actions commonly used in HRSD?

Would appreciate guidance with practical examples from your experience.

Thank you in advance!

[pjftenorio]

For UI Actions, I believe that this are commonly used in HR Agent Workspace

[its_SumitNow · Accepted solution]

Hi @sarthakkach 

Business Rules are what I use when I need something to happen on the server no matter how a record is updated. For example in HRSD, when a case is submitted I want it to be assigned to the HR service team based on the COE. This needs to happen every time so I use a Business Rule. Another time I use Business Rules is when I want to update the HR case state when all tasks are completed.

Client Scripts are great when I need something to happen away on the form. Like when an employee selects "Maternity Leave" as the HR service I want to show a due date field away. Client Scripts are perfect for this because they happen in time and do not need the page to reload. However I have to remember that Client Scripts only work in the browser so I should not rely on them for checks.

UI Policies are really useful and often not used enough. In HRSD situations they are all I need and I do not have to write any code. For instance if I want to make a field required when a certain type of leave is selected or hide a field unless the case type is Grievance I use a UI Policy. If I need to show or hide a field or make it required I always try UI Policies before writing any code.

UI Actions are what I use when I need custom buttons or menu options on HR cases. For example I might want a "Send to Manager for Approval" button that starts a workflow or sends a notification. This is something that an HR agent has to do rather than it happening automatically. Another example is a "Reopen Case" button that only appears when the case is closed.

Here is what I always keep in mind:

If something has to happen every time I use a Business Rule. If I need something to happen away, on the form I use a Client Script. If I need to show or hide a field or make it required without writing any code I use a UI Policy. If I need a custom button or menu option I use a UI Action.

I hope this helps you, If it helped please mark helpful & Accept as Solution 🙂

Regards

Sumit