Table ProfileGroups - TrackingChains/TrackingChain GitHub Wiki

This is a very important table as it manages the profiles of incoming Tracking requests.

Id: Random GUID
AggregationCode: Currently always NULL as it will be used in one of the upcoming improvements.
Authority: Currently always NULL as it will be used in one of the upcoming improvements.
Category: Each tracking request in the Triage will always have a category name associated with it (in addition to the pair of values to be saved on-chain). This allows linking requests to different profiles, which will be stored in different smart contracts.
ProfileName: Name associated with the profile (only useful for displaying it in the frontend).
Name: Name used by front-end.
SmartContractId: Id of smart contract linked.
Priority: If a request matches multiple rows, the one with the lowest value will be selected.

---

Note: Future improvements will introduce more complex profile scenarios. The Authority fields will be used, for example, to filter profiles based on the authenticated user on the APIs. The AggregationCode will enable grouping codes into subgroups, allowing for routing to different profiles based on a regex match or other programmable configurations. There is also an upcoming improvement that will enable parallelization of requests within the same profile, indicating if the current profile can handle requests with different codes concurrently.