RTiS Link Converter

Convert old links from either legacy application into the correct new RTiS link. The environment (DEV / UAT / PROD) is always preserved. Pick the matching tab for your old link.

Copied ✓
Convert many links at once

Paste one old link per line.

Reference: tab & parameter mapping
Word in old linkBecomes in new link
(nothing)(default page — no tab param)
visualizationapp_model_tab=visualization
model-exportapp_model_tab=versions (exception — renamed)
contextapp_model_tab=json-ld-toolbox&app_model_toolbox_tab=context
payload-exampleapp_model_tab=json-ld-toolbox&app_model_toolbox_tab=payload-example
json-ld-validationapp_model_tab=json-ld-toolbox&app_model_toolbox_tab=json-ld-validation
version=app_model_version_date= (any page)
focus=model_visualization_focus= (visualization only)

The old link doesn't say what the ID points to, so choose its type. Master/Hosted Terminology share -terminology; both concept types share -concept.

Copied ✓
Reference: type → suffix mapping
Type of entrySuffix in new link
Master Terminology-terminology
Hosted Terminology-terminology (same as Master)
Master Terminology Concept-concept
Application Terminology Concept-concept (same — shared ID)
Application-application
Application Terminology-appterminology

The ID is the part after the last / in the resource address. The new ui app resolves the rest.

Enter one ID for an RTS Browser entry, or two (Application then Model) for a Model.

A bare ID carries no environment, so pick one. It is not guessed.

Copied ✓

One ID builds an /ui?entity=ID-suffix link (like the RTS Browser tab). Two IDs build a /ui/model?entity=appId-modelId-appModel… link (like the Model Browser tab). You can also paste a full resource address (http://ontology.roche.com/ROX…) — the ID is taken from the end.

Old links stay on the same environment (host is preserved). For bare IDs, the environment is chosen above. The identifying ID is always required; the new application resolves the rest.