Workflow Documentation
Hey, I know that workflows are not released yet, but I am evaluating TwentyCRM and the only thing stopping me is lack of computed fields which workflows are meant to solve I think. So I'm trying to update a field in a record that I have just modified using a workflow. But I can't quite get the Code step to work as its completely undocumented as far as I can see.
Has anyone got a documentation link or any examples about how to update an updated record using the Code Step? Thanks!
7 Replies
Hi @Evil Raat, there is no doc today, this is a good point. We should work on this. I would be happy to get your feedbacks and to know where you are struggling in code steps 🙂
Just trying to understand the scripting interface - like how do I reference the current record properties in the serverless function?
My use case is that I want to update a field in the current Opportunity record after update, to compute a weighted amount of the opportunity which is Amount * Probability (custom field)
This pic kinda shows what I'm trying to do, but I don't see the relation between the fields that are selected in the 'a' and 'b' inputs and how they can be referenced in the script.
When I use the Test function and pass in a JSON payload as shown in the other pic, the function works, but I have no idea how the system is presenting the data to my function in the a and b parameters.
Do you have any examples of something similar?
Also how is the return value used in by the system? I would like to update the record in question but don't know what the syntax is to achieve that, or how the retun value should be structured.
The flow run details give more information but still not able to get this working. The feature I think is not quite ready as the object that is being operated on, which you can see in the graphql response payload, is missing key things in the before and after parts of the payload, like the amount.amountMicros being NULL.
I'm giving up on this investigation for now, until the feature is a bit more mature.
I'm giving up on this investigation for now, until the feature is a bit more mature.
Interesting, we definitely need a doc then. Thanks for sharing your use case, it can definitely be done using workflows.
First issue, when you set the variable
Record ID, you will only get the value and not an object. So your function should not expect {"Record ID": "ddd08..."} but only ddd08... as value for the variable a
Second issue, given what I just explained, b will not have the value {"Amount Micros": 1234.00, "Probability": 0.1}. It will read both values and concat into a number. So you probably received something like 1234.0001 for b. You need to separate into 2 distinguished variablesHere is the solution that you can try
Thank you @thomast - I was able to get the field updating correctly with your help.
For others in future, the attached setup allowed me to complete the above use case.
