crm issue.docx (209.4 KB)
pls check the attached file Geofence Radius (100 meters) but the checkout from 45km pls look into the matter.
@ssplmkt Hello Sir,
Thank you for sharing the references.
Upon analyzing the issue, I found that the activity was created manually, and the check-in was performed directly on the activity itself. As a result, geofencing did not work as expected. This has been identified as a bug.
We will address this in a future release.
1 Like
@ssplmkt Sir,
This issue has been resolved. The problem occurred because geofencing was not enabled for the Task module, and the check-in was directly attempted there. We have now enabled geofencing for the Task module and tested it successfully.
Kindly confirm if it is working as expected on your end.
Pls. see the video not working properly
@ssplmkt Sir,
This is not an issue.
Since geofencing is applied to the Task module, the related record must have an address. This is necessary to validate whether you are within the radius of the related record’s address during check-in.
To resolve this, kindly link the Task to any record that contains an address value and try again, sir.
2 Likes