- follow-ups
- Meeting (appointment)
- To-do (task)
- Call (follow-up)
- documents
- mailings and form submissions
- chat sessions
Owner
Associate acts as the owner of the follow-up. If you don’t assign an associate to theAssociate property of the appointment, the current user will become the owner of the appointment and only one row will be added to the appointment table when the appointment is saved.
Create appointments
You can create an appointment at multiple levels of NetServer, for example web services and in CRMScript. For other options, see the linked “working with” sections at the bottom of this page.Invitations
When two appointments have a shared text record and different status values it can be called an invitation.Examples
- Create invitation - CRMScript
- Create invitation - web services
- Get invitations - web services
- Accept invitation - CRMScript
- Accept invitation - web services
Recurrence
A repeating follow-up is a series events scheduled to occur at regular intervals. For example, a weekly status meeting. A recurring appointment is stored in two parts:- A recurrence rule, which defines the pattern of the recurrence
- All the appointments created by the recurrence are created in the appointment table, and each one points to the recurrence rule that defines it.
- Create recurring appointment - CRMScript
- Create recurring appointment - web services
Example (SQL)
The system generates appointment records for all the recurrence instances:
Let’s look at the rule:
This recurrence rule has:
- pattern = 2 (weekly) (corresponds to the radio-button choice in the dialog).
- subPattern = 0 (none)
- cyclicWeek = 1 = “every 1 week(s)“
Reference
Frequently used database fields
For a complete list of fields, see the database reference.
Appointment types
Appointment status
Timestamp values
Relevant invitation statuses
Frequency
A cycle is the number of days between each recurrence.
The enum values correspond to what you see in the Pattern dialog.