Service Builder stopped working after upgrade to 3.1.3

[Mikael Karlsson]

Anyone else failing to use Service Builder when installing: Service Builder 3.1.3 and DPM 6.0.8.

When opening a service which is operational and attempting to submit we get the error from a validation script: Status can only move forward to retiring or retired or obsolete from operational.

I suspect this is only a symptom of another issue since we also see the following in the application log when opening a service in SB:

[ASB] Error while setting draft prefix for record name: [Draft] <ServiceName>

There is a new feature in that version which renames the draft with a prefix, and for some reason that fails in our environments.

[Hugo Barros]

Hey there,
I am facing the same issue in a client instance. Could you get more information on this?

[Mikael Karlsson]

Hi @Hugo Barros, super we need the leverage! So far we have narrowed it down to that the CSDM Activation needs to be installed for it to fail. We have reproduced that in OOTB instance.

From DPM 5.0.3 they seem to have moved over to the "new" lifecycle standards IF CSDM Activation is enabled which it is in our case. Perhaps the customer base with that combination is still low because it took almost a week to get some traction on the case.

I'll share a PRB number once we get one created!

Version 5.0.3 - February 2024 (Washington DC)

• New:
• Use the CSDM lifecycle fields for services and offerings when the CSDM activation plugin is installed (com.snc.cmdb.csdm.activation). With the plugin installed, the Lifecycle Stage and Lifecycle Stage Status fields replace the Phase and Status fields for all services and offerings.

[Mikael Karlsson]

@Hugo Barros today i got information that the there will be a new PRB created for this issue. i didn't get the number but your support rep can likely find int.

[SunnyT]

We are running into the same issue.