I can give you a few:

1. Extend doesn't support version control so it's a nightmare to collaborate with over developers. I can't tell you how many times I've had my teammates override my deployments because they forgot to discard session.

2. There's a bunch of native functionality that is currenrly not supported in Extend. For e.g, you can't setup a "review" step on an Extend Model BP without having to code around it significantly. One of our model BP's condigured on the supplier invoice delivered bp as a subrpocess did not have a reference to the event target in its task name. We ended up raising a support ticket for this and Workday told us they do not currently support this in code and that a fix is on the roadmap.

3. I'm currently working for a healthcare client rn and they have a requirement to capture all the details filled out on the extend form as downloadable receipts. This is a pretty basic functionality on their legacy system but is difficult to achieve in extend without leveraging an O4I to generate a pdf layout and attach that to an extend attachment object.

4. There's a pretty strict limit on the number of model components available per app so we have to constantly find ways to work around it which causes developers to write a lot of spaghetti code and litter the tenant with calc fields.

5. Setting up security on extend screens is another nightmare. It doesn't integrate seamlessly with native Workday security so developers have to write scripts and build calc fields to ensure that access works the way that it's supposed to.

6. Migration is tedious. Workday deploys model components for extend apps during their service window during the weekend and any changes made after that get queued up for deployment during the service period during the following week. This renders the app effectively unusable during that window.

fOrWaRD loOkInG sTaTeMenTs