Meeting default acceptanceStatus

[esforim]

UPDATE: This parameter is not intent to work. See post: https://forum.espocrm.com/forum/feat...6334#post66334

Tested using the demo version: Version 6.0.9

Issue: Setting the default enum field: acceptanceStatus does not work in entity Meeting

What should happen: newly added Contact should have the default status.

How to reproduce:

1. Go to https://demo.espocrm.com/?lang=en_US...ceptanceStatus

2. Change Default status to: Accept

3. Click "Save"

4. Create new meeting > https://demo.espocrm.com/?lang=en_US#Meeting/create
(You can also open existing meeting or create meeting from contact entity, none of these method work for default status).

5. On the side panel, under Contact, click "^" button, choose any Contact.

6. Default status remain as "None", it should have "Accept" as we set that as default.

7. However there is a trick! You can go back to Go to https://demo.espocrm.com/?lang=en_US...ceptanceStatus
and re-order Accept to be on top and it will choose Accept as the "default".

[item]

Hum,
i think it's same as what i have respond here : https://forum.espocrm.com/forum/feat...different-user

i think you can't "decide" (law) for contact/user/... accepted by default.
you need interaction with contact/user/...

imagine a entreprise who do default accept users.. . so on meeting user is not there ... 1 time.. 2 time .. then entreprise can revoke users because never join meeting...and user never see invitation.

to brainstroming .. but we can "set default acceptanceStatus" i think.

[esforim]

Also item, user is not the same as contact.

user = employee/staff/can log in/portal(?)
contact = client/people/not our employee

[esforim]

Hi item, it more about a feature (able to set default status) that is available (change enum default) but it does not work as intended.

---
Offtopic:

As for discussion whether we should default "accept" is just a matter of the people who use the CRM, we not an enterprise and the numbers of user on our system is almost zero! To use the CRM step-by-step there is many process you need to do but if you wait till you need to do every step it, you will never use CRM.

Usually with meeting that I added it is already confirm that it will happen. For example: We either make the happen mandatory (you need to be at our office), or we confirm that if this time and date is OK.

We don't really send email "Invitation", we don't triple logs task>call>meeting either if the only purpose is to schedule for an meeting. For example:
Task: Schedule meeting to sign documents
Call: Call the client to schedule when they can come in.
Meetings: Client coming in tomorrow at 9am

We just jump straight to:
After meeting end: "Can you come in again at 9am tomorrow?" "Yes."
Meeting > Mr John Smith > 9am tomorrow > Accepted.

In term of ratio from my experience, 90% meeting is Accepted, 5% is Tentative, 1% decline (this rate will be higher if we ever do mass email campaign), 4% custom (cancelled, re-schedule)

[yuri]

Hi,

I believe I never intended to have this parameter working. It's available because every enum field has it by default and I should have hidden it for this non-standard field.

I will consider this as a feature request, but not as a bug.

[esforim]

Cool. As a work around I just move "Accept" to the top, please don't "fix" this if this feature never get added.