Can you share an example in the given workflows where there is an update to a record field in a module that the triggering action is not in, but is in the same namespace?
Is this possible using the low-code workflow builder?
Can you share an example in the given workflows where there is an update to a record field in a module that the triggering action is not in, but is in the same namespace?
Is this possible using the low-code workflow builder?
An example is one workflow that ships with the CRM. The workflow is called “CRM - Quote - Insert Number”.
This workflow uses a custom Quote Number counter which is stored in the Settings module. A new Quote is created and the Settings module is retrieved. There the workflow gets the next Quote number, stores it in the Quote and then adds 1 to the field in the Settings module with the handle “QuoteNumber”. And finally it saves the Settings module (with now a new next quote number".
Thank you! This helped me solve my problem.