Kris West

I think the use case for this issue needs work. As at present FDC3 assumes the same user is in each app, which is a foundational assumption for us: FDC3...

> But almost all desktop applications, log into back end services with a user id, which is usually not the logged in window user. True - but they are on...

> Could you have a second look at the PR please? I haven't yet had a chance for a full review, but as the query fields are restricted so is...

#753 needs to be merged before we can do this

Notes from #802: - Discussed use cases for both 'required' apps and 'related' apps in appD config - E.g. a micro-frontend related to a larger application, such as a 'CreateOrder'...

App D discussion group outcome: This is likely to be a candidate for standardisation in future, but maybe best done after more AppDs have been published and there are more...

@Yannick-Symphony I believe it's Create as in [CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete). It's following the naming conventions at https://fdc3.finos.org/docs/next/intents/spec#intent-name-prefixes (although looks like we went off-piste with 'Get' rather than 'Retrieve'. Note that intents also...

@pauldyson @milindchidrawar could you resolve conflicts - when you push it'll re-run the checks and should pass now.

Added suggestions for alphabetical order corrections, couldn't do them all unfortunately. If you do them here you can then merge this into your other PR #761 OR you can rebase...

@milindchidrawar don't forget to take a look at VInay's PR into this branch and resolve conflicts with master. It should then build ok.