Sales CRM
Set macro dates and reminder timing
Understand base times, calendar-day delays, application timezone and daylight-saving checks.
Where to start
Sales → Deals & pipeline → Select deals → Run macro → Base date and time
Fields and options
- Access needed
- The permissions required to preview and run a sales macro
- Permission and scope
- The permissions required to preview and run a sales macro
Before you begin
Open the correct company workspace and confirm The permissions required to preview and run a sales macro. Review the original record before following these steps. Open the relevant entry under the native Sales menu; the workspace tabs use shorter labels such as Deals, Reports, Relationships and Sales setup.
Follow these steps
- Read the application timezone shown in the run form.
- Choose the intended base date and local time for this particular run.
- Preview the selected opportunities.
- Check the resolved expected-close date and the exact due date/time of every reminder.
- Adjust the base time and preview again if the dates do not match the sales plan.
Check the result
Compare the preview with the intended calendar dates before acknowledging it. After applying, inspect the scheduled activities using the same application timezone.
If something does not look right
If a daylight-saving error appears, choose a local time outside the skipped interval and preview again. If reminders land on a weekend or holiday, adjust the base time or definition; calendars do not automatically skip those dates. If a resumed reminder is overdue, its original reviewed date has passed. Review and reschedule it through the normal activity controls if appropriate.
Fields, rules and limits
- Offsets use calendar days, including weekends and holidays. They are not business-day calculations.
- Expected close date is the base date plus its configured zero-to-365-day offset. It has no reminder time of its own.
- Reminder due times use the base local clock time plus a zero-to-90-calendar-day offset. A zero-day reminder uses the base date and time.
- For example, a base time of 1 November at 09:30 and a two-day reminder produces 3 November at 09:30 in the displayed application timezone.
- The system preserves local clock time across daylight-saving changes. A local time that does not exist because the clock moves forward is rejected; choose another base time. Repeated fall-back wall times follow the application’s normal local-time handling.
- Resolved dates must remain within the supported 2000-to-2099 range. A valid base date can still produce an invalid later date near that boundary.
- The base time is explicit and may be in the past. Preview the dates carefully; past due dates can immediately appear as overdue activities.
- A paused connection or interrupted run does not shift reminder dates. Resumed work uses the original reviewed base time and resolved dates.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.