For more information, please refer to this announcement explaining best practices for getting answers to questions.
How to suppress call to autocomplete rule during transaction processing
Summary:
How to suppress call to autocomplete rule during transaction processing
Content (required):
Hi Team,
Greetings!
We have an autocomplete rule which restricts data change for the employee moving from blank grade ladder to non-blank grade ladder and vice versa.
We want this rule to get suppressed (not get invoked) when the similar change is being made in a transaction (like Transfer, Promotion, etc.) on transaction console.
i.e. such transactions (which apprear on console and undergo the BPM approvals) should not get evaluated through the autocomplete rule.
How can this be handled? Is there any such check we can add in the logic of autocomplete rule to identify that the data change is being initiated from a transaction and not through the other means like HR Super user/admin change or HDL load or Mass update etc.