Life Cycle Stage and Life Cycle Status fields are not accepting values when typed

[SzTamas]

Hello everyone!

We encountered the following issue:

When a new Business Application is created, the Life Cycle Stage and Lifecycle Status reference fields do not behave as expected. If you select a value using the magnifying glass, it is accepted by the field. However, if you type the value in the field and try to save the entry, an error occurs - see screenshot.

The issue only appears when using German language and values.

Do you have any suggestions?

Many thanks in advance!

[shloke04]

Hi @SzTamas ,

This is an expected behavior. Reason being both of the attributes are Reference type which means you can't type in free form string values. 

If you need additional values , you would need to create them in those reference tables first and then only you will be able to select those while defining business applications.

Life Cycle Stage - Refers to the table "life_cycle_stage". Type in "life_cycle_stage.LIST" from application navigator search and then define your choices there first.

Similarly for Life cycle stage status - Refers to the table "life_cycle_stage_status". Type in "life_cycle_stage.LIST" from application navigator search and then define your choices there first.

While defining new values, you need to be careful on below aspects:

1. You would also need to define the mapping between both Life cycle stage and Life cycle stage status value using the module "Life Cycle Mappings"

You can directly use the below link as well - https://instance.service-now.com/life_cycle_mapping_list.do?sysparm_userpref_module=29cd26b473b21010... 

Replace "instance" with instance name

2. Reason being both the above attributes are dependent and a mapping would be required.

3. Also, these values would be available across the platform for selection so you need to be watchful on when you are creating new choices.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0999120

[SzTamas]

Thanks for the reply, shloke04!

I understand your points.
However, we are not typing "new" free form string values in the field that do not exist among the reference choices.

We are typing one of the valid options, but it is still not accepted this way.

For example: I type "Bereitstellen" in the field "Lebenszyklusphase" (life_cycle_stage), where "Funktionsfähig" is, and when I try to save the entry, it reverts back to "Funktionsfähig", stating there is no match with the available choices - even though the choice is there (see attached screenshot).

Any reasonable explanation for this kind of behavior?

Should I be able to find the reason for the error in some system log?

Thanks in advance!

[shloke04]

Hi @SzTamas ,

Looking at the screenshot attached, there are 2 things happening.

1. Please check for any business rule on business application table which is blocking this from happening and is reverting back to the previous value.

2. Try disabling all the custom BR on business application table and then try and see if this works.

3. Now to error out which is the culprit try enabling them one by one and keep checking when this fails and you will get an idea on the culprit BR responsible for this.

4. Also do check for any on change client script on business application table.

[SzTamas]

Hi again, shloke04!

Thanks for the guidance, I've checked all the business rules and client scripts that might come in question for the cmdb_ci_business_app table, and also all business rules that contain "Life Cycle" in their name - see screenshots.

I've tried disabling those that might influence the behavior of the life cycle fields, but sadly, there is no change.

Any other suggestions, or this seems to be an issue for HI Support as well?

Thanks a lot!