Why don't Risk Statements and Control Objectives have a Number/ID Field?

edrussell
Tera Expert

Any idea why Risk Statements and Control Objectives don't have a Number/ID Field?  Is it an oversight or is there a specific reason tied to the "Content" data type? 

1 ACCEPTED SOLUTION

Community Alums
Not applicable

Hi @edrussell ,

Both Risk Statements and Control Objectives don't have a Number/ID Field as these are built on GRC Content tables and both doesn't have a Lifecycle like we get in Risk and Control respectively which are built on GRC Item table and they both have lifecycles.

If you want you can create a custom field which can store the unique numbers which will get auto generated.

 

View solution in original post

3 REPLIES 3

Community Alums
Not applicable

Hi @edrussell ,

Both Risk Statements and Control Objectives don't have a Number/ID Field as these are built on GRC Content tables and both doesn't have a Lifecycle like we get in Risk and Control respectively which are built on GRC Item table and they both have lifecycles.

If you want you can create a custom field which can store the unique numbers which will get auto generated.

 

Community Alums
Not applicable

Hi @edrussell ,

 

Community Alums
Not applicable

Hi @edrussell ,