In the realm of software development, as AI-generated code strides into the spotlight, a journey of epic proportions awaits. Picture this: you, the vigilant powerplatform citizen developer , must embark on a quest much like Frodo Baggins, the unsuspecting hobbit, did in J.R.R. Tolkien's "The Lord of the Rings." Your companion, the wise and all-powerful Gandalf, is none other than Co-Pilot. It's not about merely following your AI companion's lead; it's about taking the reins, for you must be the pilot when using co-pilot
I want to test how Co-Pilot can help me create an automation that triggers an AI builder when I receive an email with the subject ‘INVOICE’ and an attachment. The first glimpse super promising and exciting.
The inquisitive spirit of Frodo Baggins within me, the developer's side, led me to delve deeper into the flow generated by co-pilot. As I explored the flow, I quickly discovered a few aspects that I might not have explored otherwise.
1) The Trigger for the cloud flow was not configured in optimized manner. As a developer would have always picked email with attachment and always used attachment to build the subsequent steps of automation. The filtering criteria was not considered by the Co-Pilot
2) Redundant step added to the automate by the co-pilot.
3) The name of the flow is the actual prompt. Would have be nice to get recommendation and use the prompt as a starting point for the description
4) The frustrating aspect was that the flow had been created, yet there was no option to save or edit it. The default environment did not grant privileged access to modify the newly generated flow
As a low code developer the practice should be to use Co-Pilot editor to edit the flow.
The Unwritten Chapter:
Co-Pilot can be a powerful ally, swiftly generating code. However, like any trusty companion, it has its quirks. Due diligence is essential to ensure the quality of the code. Remember, you are the Pilot, steering the ship through the vast code seas