The combination allows Hubspot-style workflow automation, where an opportunity (deal) moving through a pipeline can trigger an process (SOP) at any pipeline stage. You can build out processes with task assignments, dependencies, and estimated durations. When triggered, the process spawns a project and tasks with the appropriate assignments.
Thanks to the current state of cross-doc, the opportunity is updated in the CRM to show the new project. Pretty cool!
Looking forward to continuing to deepen support for continuous improvement of business processes. Ask me anything!
I have a rectangle formula on a settings page, named “Modal Line Formula”. Then in any table I can add a text column and call the Modal Line Formula. In the modal I remove the label and centre it.
That’s clever! I have a bunch of views that desperately need some visual separation for the items and using this trick is going to help the users a lot.
Yeah exactly what I use it for. The other thing I do sometimes is make section header columns in the same color as the modal line. Just a text column with whatever the header text is, in a _Color formula (like _Color(“blue”,“my header”). Then in the layout remove the label and make it H2, put it beneath a line to define the section.
For sure - the primary automation is in the process manager. When an opportunity status in the cross-doc CRM table is updated, the corresponding process is run (button push in the process row).
The rest of the “automations” follow off of that button push, where a project and tasks are created from the template process and its steps. It’s a long one, and getting the dependencies to transfer over was pretty difficult.
