"Serverless", "Web Service", "Patterns" and other choices are missing on Discovery Schedule/Status form, if Cloud Provisioning and Governance Core plugin is installed, or depending on other combinations of Discovery/Service Mapping/CPG, and install orderDescription"Serverless", "Web Service", "Patterns" and other choices are missing on Discovery Schedule and Discovery Status forms/tables, if Cloud Provisioning and Governance Core plugin is installed, or depending on other combinations of Discovery/Service Mapping/CPG, and the plugin install/upgrade order. e.g. There may be no sys_choice record for table=discovery_schedule, element=discover, for value "Serverless". Find the list here:/sys_choice_list.do?sysparm_query=GOTOname%3Ddiscovery_schedule%5Eelement%3Ddiscover There are 10 common choices:- Configuration items- IP addresses- Networks- Web Service- Service- Serverless- Cloud Application- Cloud Resources- Certificates- Pattern Some of these, required by the plugins you have installed, may be missing. The problem also applies to the similar 'discover' field on discovery_status, and this problem is fixing that as well.Steps to Reproduce 1/ Install "Cloud Provisioning and Governance". You get 5 choices:- Configuration items- IP addresses- Networks- Web Service- Cloud Resources 2/ Install "Discovery"You now have 8 choices:- Configuration items- IP addresses- Networks- Service- Serverless- Cloud Application- Cloud Resources- Certificates "Web Service" is now missing. 3/ Install Service MappingYou now have 9 choices, with "Web Service" back again:- Configuration items- IP addresses- Networks- Web Service- Service- Serverless- Cloud Application- Cloud Resources- Certificates 4/ Repair Discovery Core "com.snc.discovery.core" pluginYou end up back on the original 5 CPG choices:- Configuration items- IP addresses- Networks- Web Service- Cloud Resources Service, Serverless, Cloud Application, Certificates are now missing. ===================================5/ Start again with a fresh clean instance.6/ Install Discovery You have 8:- Configuration items- IP addresses- Networks- Service- Serverless- Cloud Application- Cloud Resources- Certificates 7/ Install Service MappingYou have 9:- Configuration items- IP addresses- Networks- Web Service- Service- Serverless- Cloud Application- Cloud Resources- Certificates 8/ Repair discovery Corewhile this runs, "Pattern" gets added, so you have 10.- PatternBut by the time this finishes repairing, you are back to 5- Configuration items- IP addresses- Networks- Web Service- Cloud Resources If you do have all 9 (or 10) choices, then you are lucky, as this is all about the order in which plugins install or upgrade. "com.snc.discovery" and "com.snc.discovery.core" both have choice lists defined.If "com.snc.discovery" installs before "com.snc.discovery.core" then you end up with only 5 choices. Discovery, Discovery Core and Service Mapping all define different choice lists. If Cloud Provisioning and Governance is installed, that only modifies what Discovery Core choice list is. The order those are installed means the last to be installed "wins". Expected behaviour:We need to be clear about which choices there should be for each ITOM Visibility application, and make sure that all combinations of those plugins/apps end up with a combination of those choices, without one plugin taking over the list with just its choices.WorkaroundThis problem has been fixed in 'Utah', for both Discovery Schedule and Discovery Status. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. Possible workaround: This problem is usually due to one of the pair of choice lists defined in the "Discovery Core" [com.snc.discovery.core] Plugin being the one seen. It can be worked-around in some cases by repairing/reinstalling the "Discovery" [com.snc.discovery], or ideally "Service Mapping" [com.snc.service-mapping] plugin instead if you have that product. You will then have the 8 or 9 item choice lists from those plugins seen instead. To get the full list, you may need to import the choice list from a Utah instance, after installing your combination of ITOM plugins. Notes: Depending on the order in which plugins get upgraded the next time the instance is upgraded, this issue may re-occur. Upgrade to Utah as soon as you can for a proper solution. If you have previously customised the choicelist, repairing the plugin won't replace it. Please set Replace on upgrade=True on the sys_update_xml record for "sys_choice_discovery_schedule_discover" first, before upgrading to Utah or repairing the plugin. Related Problem: PRB1603579