Recommendations for Request assignment Group

[Jason Palaganas]

We are using OOB Request Management and have a handful of catalog items for users to select from.  When an item is submitted, approval is automatic and the request, request item and catalog task records are generated.  Depending on the catalog item submitted, the task records can go to one or several groups (as there could be several tasks per catalog item).

When running reports against request and request item records, we are seeing that the assignment groups are blank for these records.  Are there any recommendations for which assignment groups these records should be assigned to if at all?  

[Mike_R]

Most people do not use the assignment group field on request or request item. The only reason why they even exist on that table is because those tables extend the core task table.

Instead, report on the catalog task table to see what group worked on the task(s).

[sushantmalsure · Accepted solution]

Mostly AG on request is kept blank but can be used when you are confident enough there will be just 1 RITM below it.

and at other side we keep it blank when we have multiple RITMs below it (case of order guide).

The reason of that field to be present is just because its inherited from task table but can be useful in just one of above case.

So I would say having AG populated only on RITM makes more sense and can be useful when report is made on just RITM with confidence that AG will never be empty on RITM (be it single RITM or multiple RITMs as part of order guide).