#Salesforcecommunity28 debatiendo

Hi Nancy, 

Based on current market reviews (Gartner, G2, Capterra) rather than personal use, here's an honest picture on DemandFarm specifically for org chart customization: 

Strengths reported: DemandFarm's Org Chart module is consistently rated among the strongest on AppExchange (5/5 rating cited across review sites) — it auto-builds org charts from Salesforce contacts, supports drag-and-drop editing, auto-syncs when contacts/titles/account team assignments change in Salesforce, and lets you set rules for which fields display to reduce clutter. It's also genuinely native — plans, org charts, and whitespace data live as Salesforce objects tied to your Accounts/Contacts/Opportunities, not an external tool bolted on. 

Things worth knowing before committing: 

- Licensing is modular. Org Chart, Account Planner, and Opportunity Planner are often licensed separately, so pin down exactly which modules your quote includes — people frequently report higher-than-expected total cost from assuming one module included the others. 

- It's built for large/strategic key accounts. Reviews note it can feel like overkill if you're managing a broad, lighter book of business rather than a focused set of strategic accounts — worth confirming it matches your actual account portfolio size/complexity. 

- On G2, head-to-head against

CRUSH, reviewers rated Prolifiq somewhat higher overall (4.7 vs 4.4) and preferred its feature roadmap direction, though DemandFarm's org chart specifically remains well-regarded in isolation. 

Other org-chart-capable alternatives worth comparing against, since you're evaluating options: 

- Prolifiq CRUSH / Prolifiq Relationship Map — fully native to Salesforce (not just integrated), straightforward drag-and-drop org chart builder directly on the account page. 

- ARPEDIO — similar strategic account planning focus to DemandFarm, also Salesforce-native. 

- Squivr — specifically for org chart/hierarchy visualization if that's your primary need rather than full account planning. 

Given your stated need is specifically org chart customization (not necessarily the full KAM suite), it may be worth demoing Prolifiq's org chart module alongside DemandFarm's — several reviewers rate it as a simpler, fully-native alternative if you don't need DemandFarm's broader account-planning/whitespace features.

You’re correct that there isn’t a direct trigger point here. ProcessInstanceWorkitem doesn’t support Apex triggers or record-triggered flows, and reassigning the approval doesn’t update the Case itself. 

If you need to keep the standard Reassign action, I’d handle it with scheduled Apex:

1.  Run a scheduled job every few minutes. 
2.  Query new ProcessInstanceStep records where StepStatus = 'Reassigned'. 
3.  Use ProcessInstance.TargetObjectId to identify the related Case. 
4.  Query the pending ProcessInstanceWorkitem for that process instance to get the newly assigned ActorId. 
5.  Insert a FeedItem with the Case ID as ParentId. 
6.  Store the processed ProcessInstanceStep.Id in a small custom log object with a unique/external-ID field. 
7.  Skip any step already in that log so rerunning the job can’t create duplicate Chatter posts. 

I’d also test it by reassigning the same approval twice and then running the job twice. The expected result should be two Chatter posts total, with no additional posts from the second job run. 

If real-time posting is absolutely required, the other option is to replace the standard Reassign experience with a custom Flow/LWC backed by Apex. That custom action would update ProcessInstanceWorkitem.ActorId and create the Case FeedItem in the same transaction. But the existing standard Reassign action can’t be intercepted directly.

Hi @Swati Malkar

 Yes, Salesforce Spiff provides an Archive User option, but it is different from permanently deleting a user.

If a user has already been uploaded and added to Spiff, you can archive them by following these steps:

1. Go to Admin → Users in Salesforce Spiff.
2. Open the user’s profile.
3. Click Edit.
4. Deselect Make this user visible.
5. Confirm Archive User and save.

After archiving:

• The user will no longer appear as an active user in the regular Users page.
• Data syncing is automatically disabled.
• Existing statements and historical records are retained.
• The user cannot be assigned to new teams or plans.

If the user is synced from Salesforce or another external source, you should also review the source system and syncing settings.

Important: Archiving hides the user from active management, but it does not permanently delete their historical data. For complete permanent deletion, check your organization's Spiff data-retention policies and available Salesforce support options.

Reference: Archive and Unarchive User Accounts

Hope this helps! 😊  

If you find this response helpful, please mark it as the Accepted Answer, as it may also help other Trailblazers facing a similar issue. 😊  

@Nancy MagalhaesOne limitation I’d consider is the underlying data model: the native Relationship Map is primarily account/contact relationship-focused, so a true side-by-side “customer org + our internal org” hierarchy is difficult to maintain dynamically.

If this is a recurring sales use case, I’d model the internal stakeholders and customer contacts as related records with an explicit relationship type (Decision Maker, Executive Sponsor, Account Owner, etc.), then surface those relationships through a custom LWC. That would keep the visualization data-driven instead of relying on manually added cards, while still keeping everything inside Salesforce.