Unknown MuleSoft Features You Are Coding When You Don't Have To

[@jacekbiaecki8076]

The whole video is GOLD but this fragment (12:00) is PLATINUM. Thank you for this advice, Jason!

[@sadikintegrations]

Jason : your topics are awesome .. I really love it. Its really base of our work. .every one should watch it once.

[@manishachotaliya3112]

Thank you for sharing the best practices,Jason...

[@AndyDaSilva52]

00:00:00 - Introduction 00:00:39 - Item 01 - DW Default Keyword 00:03:54 - Item 02 - HTTP Response Status Codes 00:09:02 - Item 03 - Logging Input Payloads 00:14:10 - Item 04 - Saving Payloads (Ref: Enterprise Integration Patterns - Content Enricher) 00:18:06 - Item 04 - Saving Payloads - Implement Content Enricher 00:19:22 - Item 04 - Saving Payloads - Demo of Content Enricher Implementation 00:21:17 - Item 05 - Triggering your Flow 00:25:59 - Item 06 - Persistence Storage

[@orayan11]

Really appreciate, i will use all of it and keep in mind. Thanks

[@giribabusaggurthi862]

Thanks a lot for the information

[@5atyaki]

Thank you!

[@adsfgasdfadsasdf]

Great video! If not the object store way, what would be a better way of making sure a flow (triggered by a scheduler) isn't already running?

[@JasonEstevan]

disallowConcurrentExecution doc: docs.mulesoft.com/mule-runtime/4.4/scheduler-xml-reference#scheduler-properties

[@adsfgasdfadsasdf]

@@JasonEstevan Wow, that's exactly what i was looking for. I wonder why that attribute can't be set directly from the UI. Big thanks! :)

[@ctingulz]

Does that log4j trick work in runtime fabric or is that ignored like many other things?

[@sushantshekher]

It's a good one, It will be really helpful if you can share such a sample code somewhere for a beginner like me.