You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The createLogEntry function is useful, but it could be more useful if the registration linked the log to records that it either finds, or creates as part of the registration. Add new lookup fields to the Account, Contact, Case and User objects and populate these at the various points when calling the SiteUtilities.createLogEntry() method.
The log entry will not always be fully populated with all fields depending on configuration. For example:
If you do not query cases then this field would never be populated.
If you're using Accounts, the Contact would need to be populated with the PersonContactId.
If using Business Accounts, then it would be just the Contact Id.
If a record is matched, need to use that Id, if creating a new record then use that Id instead.
User may not always be created if there was a failure creating (For login component, not sure if the Site class returns the Id of the user it is trying to login, or if we can get it from the loginHistory table when we check the status.
The text was updated successfully, but these errors were encountered:
The createLogEntry function is useful, but it could be more useful if the registration linked the log to records that it either finds, or creates as part of the registration. Add new lookup fields to the Account, Contact, Case and User objects and populate these at the various points when calling the SiteUtilities.createLogEntry() method.
The log entry will not always be fully populated with all fields depending on configuration. For example:
The text was updated successfully, but these errors were encountered: