Convert Business Service to Application Service

[JP-ODU]

Through some misadventure, earlier CMDB efforts have resulted in our original Business Service (cmdb_ci_service) table containing items that should be Application Services. The "Convert to Application Service" button is available, but in testing using it, there seem to be multiple issues:

1. The converted item is listed as a Calculated Application Service, but all our other Application Services are Mapped Application Services. Is there a way to convert a Business Service to a Mapped Application Service, instead of Calculated?

2. The converted item seems to "lose" all it's related items/children, and instead gains a number of "entry points" which seem to be generic listings of "manual Endpoint?" What are these manual endpoints, and where did the related items/children go?

3. If I hit the "List CIs" related link, this opens a list of cmdb_ci filtered for the SYS ID of the Application Service, and this has both the "missing" children/related items and the Manual Endpoints on it...

Am I doing Convert to Application Service wrong? What am I missing?

I was also wondering if I can manually re-create the erroneous Business Services as Mapped Application Services, then inactivate the old Business Service version, but...

1) I see no active/inactive check for Services

2) This requires swapping out the configuration item on each Incident, replacing the Business Service version with the Mapped Application Service version? But now there are two Services with the same name, one of which is "wrong?"

What's the right approach to take, here?

[Nikhil Kumar Sh]

Hi, Following your post.

I am curious to know that why do you want to move Application Services from Calculated to Mapped one?

Is there any impact or features miss out if you stay with Calculated AS.

[JP-ODU]

That may be my own misunderstanding. Right now, my supervisor objects to it being set as a Calculated Application Service because:

1. All our other Application Services are Mapped

2. It appears in a different table? cmdb_ci_service_calculated for Calculated vs cmdb_ci_service_discovered for Mapped

From what I've been able to read, my understanding is that there shouldn't really be a functional difference between Calculated Application Service and Mapped Application Service? They act the same and it's just a matter of denoting whether the relationships were manually setup (Mapped) vs automatically (Calculated)? Is that correct?

If we're just supposed to accept that it converts into a Calculated Application because that's how it works, I think I can accept that, but any idea what's going on with the lost children/relationships?

[Nikhil Kumar Sh]

Hi,

Event I am not sure about the impact of moving applications like this. But as far as the data is missing its probably due to different form layout for different tables. You probably have to add related list, relationship data widgets in the form layout, as I tested information remains there it just it gets hidden when you move across tables.

Keep us posted for further findings.

[Suzanne10]

I happen to be testing this right now and was trying to figure out why it is converting our Business Service (CMDB_CI_Service) to a Calculated Application Service vs the Mapped Application Service.  The documentation indicates it should be changing it to a Mapped Application Service.  

Did you ever get an answer on this or figure out how to get it to convert to the Mapped Application Service?