Return to Answer

• The date_offset (=259200) in the above rule corresponds to "3 days in advance", which may need review / tuning.

• If needed, you could also use the Field Permissions module to set field-level permissions to edit, view and create fields on any entity.

• Instead of just sending an eMail (as in the Rules Component), you could replace that by a more advanced option using the Message module (which has great integrations with the Rules module also). Here is an quote about that module (from its project page):

... enables logging and displaying system events in a number of different use cases. Events that are recorded over time are sometimes call activity streams. Exportable messages subtypes can be created for different use cases with custom fields and display (view) modes.

• The date_offset (=259200) in the above rule corresponds to "3 days in advance", which may need review / tuning.

• If needed, you could also use the Field Permissions module to set field-level permissions to edit, view and create fields on any entity.

• Instead of just sending an eMail (as in the Rules Component), you could replace that by a more advanced option using the Message module (which has great integrations with the Rules module also). Here is an quote about that module (from its project page):

  ... enables logging and displaying system events in a number of different use cases. Events that are recorded over time are sometimes call activity streams. Exportable messages subtypes can be created for different use cases with custom fields and display (view) modes.

Add a field to the "user" entity with machine name (say) field_next_appointment. Allow only 1 date (to store the "next" appointment), but don't make it required.

Here is the Rules Component to be created (in Rules export format, just import it in your own environment via copy-paste):

Here is the Rule to be created, in Rules export format (just import it in your own environment via copy-paste):

Note that the above rule refers to the Rules Component from the previous step.

Add a field to the "user" entity with machine name (say) field_next_appointment. Allow only 1 date (to store the "next" appointment), but don't make it required.

Here is the Rules Component to be created (in Rules export format, just import it in your own environment via copy-paste, which you can do using the "Import rule" link located at admin/config/workflow/rules):

Here is the Rule to be created, in Rules export format (just import it in your own environment via copy-paste, which you can do using the "Import rule" link located at admin/config/workflow/rules):

Note that the above rule refers to the Rules Component from the previous step.

Also note the machine name of field_next_appointment in this rule, which is the field's machine name created in Step 1 (if in step 1 you used another machine name, then also replace the machine name field_next_appointment in this rule with the machine name of the field created in Step 1 (if you don't have such field yet, or the field names don't match, then the import of the above rule might not work).

Add a field to the "user" entity with machine name (say) field_next_appointment. Allow only 1 date (the store the "next" appointment), but don't make it required.

Add a field to the "user" entity with machine name (say) field_next_appointment. Allow only 1 date (to store the "next" appointment), but don't make it required.