This content has been marked as final. Show 2 replies
Maybe you have fixed this by now but it sounds like your AME rule is firing for every single SSHR transaction submitted.
It is more usual to add an extra Condition such as
if WORKFLOW_NAME = HR_CHANGE_JOB_JSP_PRC then true
and then combine that with your new attribute. In other words, only ever evaluate your attribute within the flows where it is important, not all flows.
I had a similar issue with a custom AME attribute. I resolved the issue by using an inline select script on the attribute. I needed to retrieve a value that existed on some Requisition Request Types but not all. The script provides the value if it exists and where it doesn't still returns a line.
Select (select pti.attribute_value
from por_template_info pti
where pti.attribute_code = 'IFT_100'
AND pti.requisition_line_id = prl.requisition_line_id)
from po_requisition_lines_all prl
where prl.requisition_header_id = :transactionId
I hope this helps you.