New follow-up does not remember current object

Is this intended behavior? this is different from current/existing follow up dialog, which does fill in the current entities when creating from the new button.

It is due to the 'config screens' that we have changed this now - iow. a deliberate change :)
When you create a new follow-up from the archives, we expect it to be natural to link the follow-up to the current sale/project, where these fields are filled in.
When using the New button to create a follow-up, it can be a bit more random. And if these fields are not displayed (ref. 'config screens'), you will not see the link either, but it will be there and appear in f.ex. search and selection.

Strange solution, I would expect that a field that is not present on the screen is not pre-filled, regardless from where I am opening that screen.

This is going to break the 'workflow' of customers who work a lot with projects and sales and have been instructed over the years to use the new button to create an activity on the entity (project/sale/company/etc) that they currently have in front of them.

Thanks for clarifying this a bit more Frode. To be honest, I will expect this to be a painful change for many customers and I also think this is not "the way to go" as I think this new logic does not have any benefits from a user perspective.

To be honest, I really enjoyed the "single point of entry" by referring to the New-button at the top. The button is always visible and available in the interface and is always using related information from the entity you are currently looking at (Person, Company, Sale, Project). As a consultant, I have always encouraged my customers to "always use" the New button at the top instead of the "Add" button in activities - reason: simplicity, efficiency, and the "single point of entry" logic (simply always use "New" as your starting point for registration).

Now you create new logic which is less intuitive in my opinion - as it requires to be in a specific "archive" to start efficient registration (efficient = have the correct entities linked immediately in your appointment, instead of manually selecting them).

Considering your technical explanation, I would expect the following "ideal situation" to be applied:
- Evaluate if a field is visually available or not (in the config screens design)
* If a field is unavailable: exclude the field logic (e.g. "Sale") in the interpretation
* If it is available: apply the logic, if it is part of the related entity you are currently looking at

Personally, I consider this to be core logic(s) which will become less intuitive. Also, related to this: Consistency will be more difficult to understand > see some examples below:
** if I use "New >> Appointment" when actively viewing the "Sale entity": it will link the company and the contact of the sale I am looking at, but it will not directly link the sale itself
** if I use "New >> Appointment" when actively viewing the "Project entity": it will link the company and the contact of one of the project members in the project, but it will not directly link the project itself
** if I use "New >> Person" when actively viewing the "Company entity": it will link the company to the new person card (I like this, but it is not the same logic as the "new logic")
** if I use "New >> Person" when actively viewing the "Project entity": it will take into account the company of the project member that has been selected/the last selected project member (I like this, but it is not the same logic as the "new logic")
** if I use "New > > Sale" when actively viewing the "Project entity": it will take into account the company and the person of the project member that has been selected/the last selected project member (I would expect the Project to be linked automatically as well)

My conclusion is that with this new logic:
- Contact and Company will be prefilled - if applicable
- Sale and Project will not be prefilled automatically - unless when selecting them via the "add" button from the Activity archive, having the project/sale as a main card.

Main question would be: what benefits would users have from this new logic/change? Wouldn't it be more consistent if the prefilling of data would always be the same, regardless of the entity?

Also agree with David.

Our Goal should allways be to reduce clicks. this in general applies to add the current sale/project, when currently you need at least 2 clicks more or even 4 if you need to add a project and a sale.