Skip to main content

I am building a complex workflow for a project-based business. In this workflow, if multiple customers are associated with a job, the job is duplicated for each customer (City Building 1, City Building 2). Furthermore, if multiple versions of the job are required by customer A, there might end up being City Building 1 and City Building 1.1, and then City Building 2. In the end, there will just be one job selected (ex: City Building 2). 

I know that comments copy over at the time a record is duplicated, but I'm wondering if there is a solution for somehow keeping all the comments for City Building together without a bunch of annoying copying and pasting. Sometimes there are addendums etc, in addition to the multiple versions of a job. Basically, I'm trying to preserve the historical record inside the record (rather than in email threads). I also don't want to just use a notes field because then users cannot @ each other...

Is there another out-of-the-box solution I'm overlooking? Should we be considering integrating with Slack or something else? TIA!

Hmm, comments are generally meant to be pretty transitory in my experience, they don't integrate really with automations and such. Someone more experienced with scripting might have some other ideas, but the two solutions I can think of would be...

  • Leverage comment email notifications to devise some kind of automation that extracts comment info from the autogenerated notification emails and moves it into a Notes field. 
  • Create a separate Notes table that uses the Assigned field to @ users, then you can rollup/lookup the long text fields into the other tables as desired.

I do actually like that second option the more I think about it, as you could include an attachment field for relevant docs that need sharing to reference in a note, add priority flags to comments, that kind of stuff. 

Terms & ConditionsAccessibility statement