This is very useful for any developer, we should always consider the "no code" solution first and Flow Designer is a key feature for doing this. Thanks Gaurav, well done
Very clear explanation. "Flow Designer" is getting verry populair. I would like to see some examples of tesing: Is a record created, If yes then .... ; If no .... Like, Is a User member of a group, Yes, No action required, only send an e-mail No, create the recordandsend an e-mail
Thanks a lot SAAS With ServiceNow team for sharing such a great learning material with us. Since I'm coming from non technical background. These tutorials really helped me to gain lots of knowledge about servicenow development and administration . As part of hands-on experience, could please share or prepare use cases for below key points. It will really help us and improve our technical skills. 1. Client script 2. Business Rules 3. Script included 4. Workflow 5. Flow designer
The project I’m on atm wanted us to use flow designer for the catalog process engine. I find it takes a fair bit of time to apply it’s stuff to the ritm created. Rather than it being almost immediate for business rules. I hear the delay is because it’s asynchronous, and is just slow. It’s left the client needing to wait or F5 the page for the flow to take effect. Is that normal? Or should flow be just as fast as bus rules / client scripts Edit: just finished the video. You mentioned the slowness! Good to know it’s not just me. I like flow, but too slow for prime time imo
It depends on the the type of requirement. If you are fine to get delay of few more seconds, i dont think thats a big problem. For example, you are creating something automatically on a day then you should not worry about delay.
I have a question regarding the task creations. For the coding and documentation task, the action was "Create Record" and for the other 2, the action was "Create Task". What are the differences and why did you do it that way?
Create Task gives you option to create Task record directly and you can also enable option to wait for completion of task which you will not find in other general record creation.
This is very useful for any developer, we should always consider the "no code" solution first and Flow Designer is a key feature for doing this. Thanks Gaurav, well done
Thanks Alberto.
Very clear explanation.
"Flow Designer" is getting verry populair. I would like to see some examples of tesing:
Is a record created, If yes then .... ; If no ....
Like,
Is a User member of a group,
Yes, No action required, only send an e-mail
No, create the recordandsend an e-mail
Thanks a lot SAAS With ServiceNow team for sharing such a great learning material with us. Since I'm coming from non technical background. These tutorials really helped me to gain lots of knowledge about servicenow development and administration .
As part of hands-on experience, could please share or prepare use cases for below key points. It will really help us and improve our technical skills.
1. Client script
2. Business Rules
3. Script included
4. Workflow
5. Flow designer
Great to hear!. Please check this out. ua-cam.com/play/PLzTvAeLiW8Af0B4mGuOcRz48b-87UX653.html
Need more videos on Flowdesigner in depth Videos..it will be helpful..and nice work 👍👍
Sure 👍
Simple and very easy to follow tutorial .. Thanks
Glad it was helpful!
Very informative for a beginner. Thanks!
Glad it was helpful!
This is a boon for snow devlopment.🙏. Thanks for this
So nice of you
Thank you makeing video in this topic..
Could you explain more videos flow designer
Yes, sure
This is so good, please make some more videos on flow designer
Sure, working on whole flow designer training.
@@SAASWithServiceNow It was really Informative but please assist with more use cases to explore it.
Thanks for the sharing. I want to know more about how we can debug the flow if 4 of your scrum tasks cannot be created normally.
Flow Designer shows all the executions and you can know where exactly it got failed which can help to debug flow.
The project I’m on atm wanted us to use flow designer for the catalog process engine. I find it takes a fair bit of time to apply it’s stuff to the ritm created. Rather than it being almost immediate for business rules. I hear the delay is because it’s asynchronous, and is just slow. It’s left the client needing to wait or F5 the page for the flow to take effect.
Is that normal? Or should flow be just as fast as bus rules / client scripts
Edit: just finished the video. You mentioned the slowness! Good to know it’s not just me. I like flow, but too slow for prime time imo
It depends on the the type of requirement. If you are fine to get delay of few more seconds, i dont think thats a big problem. For example, you are creating something automatically on a day then you should not worry about delay.
I have a question regarding the task creations. For the coding and documentation task, the action was "Create Record" and for the other 2, the action was "Create Task". What are the differences and why did you do it that way?
Create Task gives you option to create Task record directly and you can also enable option to wait for completion of task which you will not find in other general record creation.