Overview

You have selected a particular service within your Service Gateway environment, and after about 20 seconds, you see a message modal appear. The modal shows a title of "common_fault_finder_title" and content of "common_fault_finder_msg". This is preventing you from editing the affected service.

Reviewing the browser console shows the following error, "Cannot find Condition for GUID: <GUID>."  Within the Encore.log, you identify FinderExceptions indicating that a referenced object does not exist.

Solution

This behavior often appears when the affected service references a particular template or its conditions, which no longer exist within your database. You can use the steps below as a reference to investigate this within your database and remove these missing references. 

1. Collect the affected GUID from your Browser Console.
   1. Navigate to the Services menu within the Service Gateway UI.
   2. Press F12 to open the Browser Console.
   3. Reproduce the behavior and identify the "Cannot find Condition for GUID: <GUID>" error.
   4. Collect the <GUID> from the error for use in the SQL queries below.
2. Verify that the GUID no longer exists
   1. The SPRT_SG_CONDITION table contains the primary reference to the GUID as its primary_key.
   2. To confirm the affected GUID no longer exists, you can execute a SELECT using the GUID collected above:

      SELECT * FROM SPRT_SG_CONDITION 
      WHERE GUID = <GUID_COLLECTED_FROM_CONSOLE>;

3. Locating the Invalid Reference
   1. Once you have verified that the GUID does not appear, you can check for hanging references within the other tables that reference the GUID.
   2. The GUID column within this table is referenced within five other tables that should also be checked and updated:
      
      1. SPRT_SG_SERVICE_TC_XREF
      2. SPRT_SG_POLICY_ACTION
      3. SPRT_SG_POLICY
      4. SPRT_SG_EXPRESSION
      5. SPRT_SG_CSR_RTP
   3. Each of these tables contains a field SG_CONDITION_GUID that references the GUID primary_key within the SPRT_SG_CONDITION table.
   4. As above, you can use a Select to locate any invalid references:

      SELECT * FROM <Table_Above> 
      WHERE SG_CONDITION_GUID = <GUID_COLLECTED_FROM_CONSOLE>;

4. Removing Invalid References
   1. For any of the tables above that contain instances of this invalid GUID, you can set the SG_CONDITION_GUID value to NULL:

      UPDATE <Table_Above> SET SG_CONDITION_GUID = NULL 
      WHERE SG_CONDITION_GUID = <GUID_COLLECTED_FROM_CONSOLE>;

   2. For example, if your Browser Console showed "09bef6f0-5c93-11eb-8c85-f55dc39d05cc" as the affected Condition GUID and you located references of it in the SPRT_SG_EXPRESSION table: 

      UPDATE SPRT_SG_EXPRESSION SET SG_CONDITION_GUID = NULL 
      WHERE SG_CONDITION_GUID = 09bef6f0-5c93-11eb-8c85-f55dc39d05cc;

Testing

After removing all of the orphaned GUID entries within your database, return to the affected service and verify that you can now edit the services without the error modal appearing.