Page History
...
| Info | ||||
|---|---|---|---|---|
We recommend data requests be limited to DATA_LDS users (irrespective of Admin path role - admin, user, manager) and data exports be limited to MANAGER users (irrespective of data path role - data_lds, data_agg,data_obf, data_deid). The user role determines if exports/requests are visible and runnable. | ||||
| QT_QUERY_RESULT_TYPE | user role | User-created data request | data Request Manager | Visibility/Actions |
DATA_LDS | DATA_LDS | Success | Success | Only user-created requests |
MANAGER with DATA_LDS | DATA_LDS | Success | Success | All user-created requests |
MANAGER without DATA_LDS | MANAGER | ? | ? | ? |
Admin | Admin | ? | ? | ? |
QT_BREAKDOWN_PATH
Refer to section on User Roles and Actions |
QT_BREAKDOWN_PATH
QT_breakdown_path logs the table_instance_id and the stored procedure EXEC statement for creating the Data file. QT_breakdown_path logs the table_instance_id value and the result_instance_id. to be associated with the ptset. query.
- The Table_instance_id is logged in the Name column when the user saves the table_definition.
- The Value column logs the EXEC statement of the stored procedure that generates the data file. The result_instance_id variable gets updated with the numeric value from the Query_result_instance where ptset query result_type_id =1 at the time of creation of Data file.
...
