You are currently reviewing an older revision of this page.

DRAFT KB-[SP-7316] Application import fails with missing precedent error on node output

Symptoms

This section is r

Cause

A process variable is being identified as a missing precedent, usually when the process variable has the same name as a constant that does or used to exist in the environment. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.

Workaround

  1. If not installed, install the Content Tools Plug-in from the App Market.
  2. In an empty expression rule run getcontentdetailsbyuuid(objectUUID:"<UUID>"). The result value should be a constant name, such as cons!<NameOfProcessVariableInAffectedPM>
  3. Rename the conflicting process variable in the affected process model to a different value. Ensure references to this process variable are updated as well.
  4. Re-perform the import. There should be no missing precedent error at this point.

Affected Versions

This article applies to all versions of Appian 21.2 or later.

Last Reviewed: December 2021