My Visits

Before you start

• Sign in to the correct company.
• Confirm your role and company subscription allow this module.
• Complete required master data in connected source modules before starting a transaction.
• Use demo or authorized data while learning.

Workspace map

1. Show the last 30 days of your own visits

This is a user-visible operational capability in the module. Use it after reviewing the current record, required fields, and available permission; then verify the resulting status or document and its downstream handoff.

2. Search by client name

This is a user-visible operational capability in the module. Use it after reviewing the current record, required fields, and available permission; then verify the resulting status or document and its downstream handoff.

3. Filter by written, pending, completed, off-site, or in-progress visits

This is a user-visible operational capability in the module. Use it after reviewing the current record, required fields, and available permission; then verify the resulting status or document and its downstream handoff.

4. Load older visits

This is a user-visible operational capability in the module. Use it after reviewing the current record, required fields, and available permission; then verify the resulting status or document and its downstream handoff.

5. Open a saved report or record a pending one

This is a user-visible operational capability in the module. Use it after reviewing the current record, required fields, and available permission; then verify the resulting status or document and its downstream handoff.

Recommended operating sequence

1. Show the last 30 days of your own visits
2. Search by client name
3. Filter by written, pending, completed, off-site, or in-progress visits
4. Load older visits
5. Open a saved report or record a pending one

Troubleshooting

• If an action is not visible, check role, permission, record status, and plan entitlement.
• If data is missing, correct the source module and refresh this workspace.
• Read the validation message before retrying; an approval or configuration step may be required.
• Do not bypass protected correction or reversal by creating a duplicate record.