How are opendocument URL's within reports/documents handled during migration?

[#1]

This is a cross post from this post based on Tammy's suggestion.

How are opendocument = statements are typically handled during migration of documents? For example, in DEV, the URL for the target document is going something different from what it will be needed in QA to build the opendocument URL. To keep the conversation specific, I am thinking about the Design Studio use case, where the URL may be encoded in scripting or a button.

Does this require any manual changes to documents directly in the target system to "remap" to opendocument URL's or is there some migration tool? I would see this similar to connection aliasing, where on migration, the apps simply point at a generic connection like "HANA", but underneath in DEV/QA/PROD the actual connection hosts are different.

Regards,

Justin

[Former Member · Accepted solution]

Hello Justin,

you can use relative OpenDocument URL's in order to avoid manual remappings.

In Design Studio for example with a button containing a script like this:
APPLICATION.openNewWindow("/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=123");

Best regards,

Victor

[justin_molenaur2 · Accepted solution]

Perfect, exactly what I was looking for.

Many thanks,

Justin

[justin_molenaur2 · Accepted solution]

Gabriel, one further question. Relative mapping works fine, but the assumption is that the docid's will remain the same once migrated, is this correct?

Newbie question - are mostly all BO documents transportable, ie keep their docid's consistent in each system per above? I am concerned with Explorer, Webi, an Design Studio mostly.

Regards,

Justin

[Former Member · Accepted solution]

CUID's will remain constant after transporting, no need to worry about that. Just make sure that you use in the links the CUID and not the ID (which in turn will change after transport).

Not sure if Information spaces are transportable in all situations though.

Best regards,

Victor

[justin_molenaur2 · Accepted solution]

I guess I don't understand the difference on CUID and ID, what I planned on using was the link provided in Launchpad when you right click and choose "Document Link", it looks like it provides a DocID with type CUID.

Can you elaborate on the transportability of Explorer Information Spaces?

Regards,

Justin

[Former Member · Accepted solution]

If you take the Link from "Document Link" you are using the CUID and therefore you are on the safe side of the road. Just as an example, a CUID will look like Aek5Akivrj9EhSI.ZPl6eyY while an ID will look like 54612. I am not sure about information spaces, so hopefully someone else can comment on that.

Best regards,

Victor