DRAFT KB-XXXX "Invalid function" error and missing dependencies after object rename

Cause

The dependent objects that did not update to use the renamed rule's new name and were missing from the renamed rule's dependency list, were "by name references". This means, rather than the dependent object identifying the renamed rule by the UUID, it was only identifying it by name (Ex. EPC_reactivateUser rather than a_XXXXXXXXXX). When the rule was renamed, dependent objects know to update with the new name because they look at the renamed object's UUID (so even if the name is changed, the UUID does not, and the dependent object knows it is the same rule). However, dependent objects that do not reference the renamed rule by UUID, and do these "by name references" will not update on rename, because it does not know the object it is referencing has been renamed.

Normally, when re-naming a rule, a pop-up warning appears that dependents are using "by name references" and those dependents should be updated manually. However, there are some scenarios identified where this pop-up will not show. The product team has been made aware of these scenarios and are investigating them internally.

Action

• Try clearing app server cache / search server indicies
• Undo rule rename (rename back to original name)
• For any rules missing from the renamed rules dependencies list, resave them (ensure step 2 was followed for this to work)

Affected Versions

This article applies to all versions of Appian

Last Reviewed: October 2019