How Do I Get ID of A Request Offering Before Published?

Chris_Keander

We are getting ready to go-live with our first Advanced Request Offering on the Self-Service Portal.

We have it ready in out test environment and can see the URL for direct-linking.  Since it hasn't been published to production yet, and we need to include the URL to it as part of our steps for our internal Change Request that will need to get approved, I'm looking to find a way to predict what the URL of the production ARO will be.

As an example, this is the edited URL of the test offering:

http//our.domain/SC/ServiceCatalog/RequestOffering/5491c71b-3ebf-297d-0ed7-c9395e78bded,808a3810-99dc-3ebb-5f5b-fc81a9497bf7

Tony_Collett

Request Offerings have the same ID in test environments as they do in production environments, as long as the management pack containing the RO is transferred from test to prod. 

Just make sure your domain is appropriate for prod (i.e. if test is testsvr001.local/... and prod is prodsvr001.local/... you will need to link directly to the prodsvr001 location or use local linking)

Tony_Collett

The way I would do it is a 2 step process - publish the RO, get the link and then update the required field. You could definitely look into the SQL in the ServiceManagement database, but you would still need to run the Cachebuilder at least once to get the RO into the Portal Database

Tony_Collett

http//our.domain/SC/ServiceCatalog/RequestOffering/5491c71b-3ebf-297d-0ed7-c9395e78bded,808a3810-99dc-3ebb-5f5b-fc81a9497bf7

There are 2 IDs in this link. The first is the Service Offering. If you already have this published, you can grab this ID from any other RO.as long as it's in the same SO
The second is brought in by the Cachebuilder from somewhere (unfortunately I'm not sure where) and it's the RO itself. It is not contained in the Management Pack (I checked)

sorry I can't give you a more definitive answer, maybe someone else has more information

Chris_Keander

I need to include the new URL in the CR implementation steps as it will involve teams doing a redirect from the old form (Jira) to the new.

Tony_Collett

Request Offerings have the same ID in test environments as they do in production environments, as long as the management pack containing the RO is transferred from test to prod. 

Just make sure your domain is appropriate for prod (i.e. if test is testsvr001.local/... and prod is prodsvr001.local/... you will need to link directly to the prodsvr001 location or use local linking)

Chris_Keander

What if we are running off of two different management packs?  (Don't hate me)  How would I get it then?  Some kind of SQL wizardry?

Tony_Collett

The way I would do it is a 2 step process - publish the RO, get the link and then update the required field. You could definitely look into the SQL in the ServiceManagement database, but you would still need to run the Cachebuilder at least once to get the RO into the Portal Database

Chris_Keander

There's no way of getting this from the ServiceManager DB?  I can't publish it because that would bypass our Change control processes.  This needs to be approved before publishing.  I'd like to have the URL handy to give to other stakeholders so they can upload any links on their pages.

Tony_Collett

http//our.domain/SC/ServiceCatalog/RequestOffering/5491c71b-3ebf-297d-0ed7-c9395e78bded,808a3810-99dc-3ebb-5f5b-fc81a9497bf7

There are 2 IDs in this link. The first is the Service Offering. If you already have this published, you can grab this ID from any other RO.as long as it's in the same SO
The second is brought in by the Cachebuilder from somewhere (unfortunately I'm not sure where) and it's the RO itself. It is not contained in the Management Pack (I checked)

sorry I can't give you a more definitive answer, maybe someone else has more information