3
Procurement and sourcing > Setup > Policies > Business justifications
The Business Justification setup table currently allows a user to do a "hard delete" of values that are in the table even when there were dependent records. This removes the value completely from all records and conditional decisions in workflows that reference that field. It causes records and workflows to bomb out. This is completely inconsistent with how other tables with dependent records on documents and workflows work.
This should be modified to prevent users from completely removing the value when dependent records exist or at least allow for some sort of soft deletion or inactivation.
The Business Justification setup table currently allows a user to do a "hard delete" of values that are in the table even when there were dependent records. This removes the value completely from all records and conditional decisions in workflows that reference that field. It causes records and workflows to bomb out. This is completely inconsistent with how other tables with dependent records on documents and workflows work.
This should be modified to prevent users from completely removing the value when dependent records exist or at least allow for some sort of soft deletion or inactivation.
STATUS DETAILS
Needs Votes