About Resolving References

This topic describes some use cases for resolving references.

Important: When you import a set of process apps (by pointing to Import and Export from the Composer menu and then selecting Import), the process apps keep the same internal identifiers and the references will be preserved. When you create a set of process apps (using New from the Composer menu), the process apps get new internal identifiers and you must resolve the references explicitly.

Use Case: Two Existing Process Apps

You have an existing process app with a reference to a field in another existing process app. The field in the referenced process app was deleted, so the reference becomes invalid. When you try to deploy the referencing process app, you get an error message about the missing field.

When you double-click the error message, the Property Editor for the missing field is displayed. In the Property Editor, you can select another field to use as a reference.

Use Case: Ignoring Unresolved References

You create a new process app that meant to work with another process app, so it contains unresolved references.

You do not need the other process app now, so you decide to ignore the unresolved references. To do this, right-click the unresolved reference in App Explorer and select Ignore Reference. The reference and any design elements in the referenced application are marked through, and when you validate the process app, no unresolved reference warnings are displayed in the Validation Results.

About Resolving References

Use Case: Two Existing Process Apps

Use Case: Ignoring Unresolved References

Related Topics