There is a workflow that works on VendorBills, Eve...
# ask-stanley-ai
i
There is a workflow that works on VendorBills, Events: On Create, On View Or Update and all Trigger Types. In initial state of this workflow there is a "Set Field Value" action on After Record Submit is not executed when a bill is created from RESTlet. It looks like workflow is triggered after the record is created from ResrtLet, not at the moment of creation. What should be changed in workflow or restlet, so transaction field to be changed according to the workflow action?
c
AI generated answer (using internal Slack threads):
Based on the conversations, it seems like the issue is with the sequence of events in the workflow. The "Set Field Value" action in the "After Record Submit" trigger of the workflow is not being executed when a bill is created from RESTlet. This is likely because the workflow is triggered after the record is created from RESTlet, not at the moment of creation. To resolve this issue, you could consider the following steps: 1. Change the trigger type in the workflow: Instead of using the "After Record Submit" trigger, you could use the "Before Record Submit" trigger. This would ensure that the "Set Field Value" action is executed before the record is submitted, which might resolve the issue. 2. Modify the RESTlet: You could modify the RESTlet to trigger the workflow at the moment of record creation, rather than after the record is created. This would ensure that the "Set Field Value" action is executed at the right time. 3. Add a custom workflow action: If the "Set Field Value" action is not working as expected, you could replace it with a custom workflow action that sets the field value and saves the record. This might trigger the User Event script correctly. Remember to test these changes thoroughly to ensure they work as expected and do not introduce new issues. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.861023
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.860839963
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.859619141
Please provide your feedback on this answer.