...
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
The following section provides recommendations and guidance regarding the configuration of specific areas of the application within the customer's Salesforce.com org. This section is intended to detail any specific functionality within these areas that Administrators need to be aware of prior to deploying the Motivate application within their organisation.
...
Queues can be created that contain one or more users that in turn help teams manage the distribution of Leads within an org. When new Lead records are created within the org, the owner of the Lead can be manually or automatically (see Assignment Rules 228145481 below) assigned to an individual user, or to a pre-defined queue.
...
SELECT OwnerId User, COUNT(Id) Value FROM Case WHERE Status = 'Closed' AND Owner.Type = 'User' GROUP BY OwnerId
Behaviour Criteria
Behaviour Criteria cannot be used in conjunction with Aggregate Scheduled Behaviours in Version 8 and higher, therefore any Behaviour Criteria on Aggregate Scheduled Behaviours will not be assessed. If additional criteria need to be included as part of the Behaviour, these criteria should be incorporated into the Query statement that is set directly on the Aggregate Base Behaviour. This can be achieved by using a 'HAVING' clause that allows aggregate functions to be specified, which cannot be achieved in a 'WHERE' clause.
An example of this is in the following Aggregate Scheduled Behaviour that records when a user has logged in at least 5 times in a week:
SELECT UserId User, COUNT(Id) Value FROM LoginHistory WHERE logintime = this_week GROUP BY UserId HAVING COUNT(Id) >= 5