Parking Lot Features
The Parking Lot allows users to temporarily remove Accounts, Contacts, or other configured records from the Org Chart while maintaining visibility and control over their status.
Parking Lot Reason Field
A new field, Parking Lot Reason, is available on the Contact and Account objects.
This field is a picklist controlled by the global value set Parking Lot Reason.
When the field contains a value, the associated Contact or Account appears in the Parking Lot.
Using the Parking Lot on Other Objects
To enable the Parking Lot for additional standard or custom objects:
Add a picklist field to the object that references the Parking Lot Reason global value set.
Update the Org Chart Global Settings to populate the Parking Lot Reason field for the newly configured object.
Moving Records To and From the Parking Lot
From the Org Chart, users can drag and drop supported records to and from the Parking Lot.
This action automatically updates the Parking Lot Reason field value.
Accounts and Contacts are preconfigured to support this behavior out of the box.
Removing Independent Records in Bulk
Users can also move records to the Parking Lot in bulk using the Remove Independent Contacts action.
What Is an Independent Record?
Using Contacts as an example, an Independent Contact is defined as:
A Contact that is a direct child of the Account currently in view
A Contact that does not have a Reports To value
A Contact that is not referenced as the Reports To value for any other Contact
When the action is executed, all qualifying records are moved from the Org Chart to the Parking Lot.
Using the Parking Lot with Account Contact Relationships
Note: This section applies only if your Org Chart hierarchy is configured using Account Contact Relationships.
Indirect relationships can be managed using the Parking Lot in the same way as direct relationships. However, there is one key difference:
When an indirectly related Contact is moved to the Parking Lot, Squivr updates the
IsActivefield on the AccountContactRelation record to false.
This ensures the relationship is properly deactivated while preserving historical data.
Default my contacts to the Parking Lot initially after installation
There are a few ways to accomplish this, depending on whether you want to update existing records, new records, or both.
Updating Existing Contacts
Perform a data load to populate the
squivr__Parking_Lot_Reason__cfield for all existing Contacts with a value such as “Other.”
Defaulting New Contacts to the Parking Lot
If you want all newly created Contacts to be placed in the Parking Lot going forward, you have two options:
Set a default value on the Parking Lot Reason global value set.
Create a Salesforce Flow to populate the field when a Contact is created.
Important: If you default the picklist value, all newly created child Accounts will also be placed in the Parking Lot by default. Use this approach only if that behavior is desired.