CODA has several analyzers of different categories and types, among them: performance, security, maintenance, code smell, bug prone etc.
It is natural that for each analyzer, we look at different fields and tables. For example, for Do not use client side GlideRecord issue, there is no need for our mechanism to look at tables and fields referring to the instance server-side.
But with so many analyzers, after all, where in instances does CODA look for the information to be analyzed?
Same table, different analyzers
As mentioned above, our analysis mechanism is able to differentiate the type of issue sought and then define what information that specific analyzer needs and where to get it from. This means that from the same table, information from different fields may be being collected for each different analyzer.
For Configuration Type analyzers, CODA runs a query on target table and then analyzes the results. So in practice, for these analyzers, we don't save values from this fields, we just look at them.
All tables and fields
| Label | Name | Fields |
|---|---|---|
| Widget Angular Providers | sp_angular_provider | script |
| Widgets | sp_widget | client_script, link, script |
| UI Scripts | sys_ui_script | script |
| Client Scripts | sys_script_client | script |
| Catalog Client Scripts | catalog_script_client | script |
| UI Pages | sys_ui_page | client_script, processing_script |
| Business Rules | sys_script | script, condition, filter_condition, description |
| Script Includes | sys_script_include | script |
| Access Controls | sys_security_acl | script |
| Record Producers | sc_cat_item_producer | script |
| Search Resources | sp_search_source | data_fetch_script, facet_generation_script |
| Email Scripts | sys_script_email | script |
| Notifications | sysevent_email_action | advanced_condition |
| Transform Scripts | sys_transform_script | script |
| Table Transform Maps | sys_transform_map | script |
| Field Maps | sys_transform_entry | source_script |
| UI Actions | sys_ui_action | script, condition |
| Images | db_image | size_bytes, category |
| LDAP Servers | ldap_server_config | attributes |
| System Properties | sys_properties | name, value |
| Reports | sys_report | name |
| User Preferences | sys_user_preference | name, value, user |
| Workflow context | wf_context | state, started |
| Scheduled Job | sysauto | name, active |
| Workflow Activity | wf_activity | name, published |
| Scripted REST Resource | sys_ws_operation | name, active, requires_authentication, requires_acl_authorization, http_method |
Internally, we follow a rule of developing analyzers and articles together. That way you can see all of our analyzers through the article menu and also have accurate solutions to your ServiceNow issues!