Hi!

In Bob Analytics, is it possible to track usage at the use-case level?
For example, I have multiple use cases:
UC1 – Generate new microservice
UC2 – Generate an API for an existing microservice
Each use case is implemented using multiple rule files, and some of these rule files are shared across different use cases.
What I'd like to understand is whether Bob Analytics can distinguish and track usage by specific use case rather than just by individual rule files. The goal is to identify which use cases are being used the most and the least, even when they share common rule files.

Thank you!

Hi,

Good question.

As you know Bobalytics tracks by individual user, so within a team it is easy to track each user.  But, with reference to a particular user, there is no easy way to track by Use Case.  Since the rules are shared, the only way I see is to use Modes for specific use case above.  "Generate microservice" vs "Generate API".  Bobalytics tracks by Modes, which could be leveraged here.  It does track by markdown, json, python etc but since theya re shared, modes is the only workaround I see in this case.

This could be a suggestion for the product team for enhancement , maybe a tag of Use case somewhere.

Regards,

Naren

I agree Narendra that I think custom Modes is probably the best way to track at the moment (as an indication), where they would have to be specific to avoid any overlap and ensuring the right mode was used. My concern here would be in version 2 where the human in the loop default to the agent mode, without recognising.

I wonder if potentially using the workflows might be possible to track the usage in later additions (i.e. RPG fixed to free / Java modernisation), where they could be based on use cases.

Kind Regards

Hi Narenda,

Thanks for the feedback. Can you share which part of Bobalytics shows the mode tracking? I tried checking it, there is no filter for that when I clicked "User" or "Team" view. Is this somewhat available only if the role is Admin? Currently on User role only.