Prevent two pending compinfo or jobinfo transactions/workflows in Employee Central?

[Angie_Pullano]

Hello community,

Is there a way to prevent the creation of a new transaction/workflow on an employee when they already have a pending transaction? We regularly encounter an issue where users either a) don't scroll down to look at the jobinfo or compinfo sections to see that there is already a pending transaction for that employee or b) don't notice it or edit the current pending transaction. This results in duplicate transactions being created on the same day for an employee. Most of the time users just click on the "Take Action" button on the employee profile header without even reviewing their current information.

I was able to configure a business rule to prevent a new transaction from being created for the same effective date of an existing completed transaction/workflow. While employee central allows multiple actions on the same day, we need to enforce only one transaction per day for our business needs. When there is more than one action on the same day, pulling reports results in data inconsistency and it completely breaks our custom document generation email workflow notifications since the tokens cannot resolve correctly due to there being more than one record on that date.

I was not able to find a way in business rules to reference the attributes of a pending workflow to try to accomplish the same thing when there is an existing pending transaction also for the same date as the new request.

Thank you,

Angie

[jenaklein]

Did you ever find a solution to this??