How to Duplicate and Adapt Administration Building Blocks for Custom Applications

Learn step-by-step how to duplicate, adapt, and rename administration building blocks for different applications, including best practices for managing tags and avoiding errors in your simulation environment.

July 28, 2025 By Wilbert de Witte

In this guide, we'll learn how to duplicate and adapt an administration building block for a new use case. The goal is to reuse an existing setup, make changes such as renaming and updating tags, and ensure that each application is correctly identified in the simulation.

We will also look at how to avoid confusion and errors by updating all relevant tags and restoring the original application when needed.

Let's get started

Okay. This instruction is to manually duplicate and adapt those. The issue here is that we have a specific administration building block we want to reuse, but not exactly as it is.

Step #2: Double-click on "SC depot" — Double-click on "SC depot"

We want to adapt it and rename it. If we open the building block, we see a large list of resolved applications—hundreds of them.

Step #4: Click on "‣ ❤❤ dissolved" — Click on "‣ ❤❤ dissolved"

We want to do something similar, but with fewer applications and for a different molecule. We cannot multi-select and remove most of them. Instead, we duplicated this building block and removed the entire group. We have saved, for example, application one.

Step #6: Click on "Application_1" — Click on "Application_1"

Step #7: Right-click on "Application_1" — Right-click on "Application_1"

Step #8: Click on "Save As PKML" — Click on "Save As PKML"

Saved it as application one.

Add extra comments to help differentiate it from others. We have duplicated this building block by creating a new event group and loading this event twice.

10

Type "_repeat"

Step #11: Click on "Save" — Click on "Save"

Step #13: Double-click on "SC depot" — Double-click on "SC depot"

Step #14: Click on "▸ Administrations" — Click on "▸ Administrations"

Step #16: Click on "Application_1" — Click on "Application_1"

Here, we have renamed it to Application Two.

We have updated the relative container paths.

Step #19: Click on "ProtocolSchemaItem" — Click on "ProtocolSchemaItem"

We have adjusted application two here, and also here.

Step #20: Click on "Dissolved" — Click on "Dissolved"

Now, if we look at this in the simulation, there is a problem.

The problem is as follows.

Step #22: Double-click on "hepcludex SC reimplementation" — Double-click on "hepcludex SC reimplementation"

If we open the building block we created with events, application one looks fine.

Step #24: Click on "▸ Administrations" — Click on "▸ Administrations"

Step #26: Click on "Administrations" — Click on "Administrations"

Step #27: Click on "Administrations SC" — Click on "Administrations SC"

Step #28: Click on "Application_1" — Click on "Application_1"

Application two is not correct. In the list of tags, we see "application" and "application root," which is good, but "application one" also appears.

That should be application two. So far, there has been no impact because this application is named "application two." All administration transports use relative parameters and are only active during the application. It all seems to work out fine. I think this could cause errors or at least confusion.

We want to change this. If we look at the building block, it's not something we can change directly.

In application two, no tags are visible. This application does have a tag. It's only a problem because we can't change it. There is a way to solve this.

Step #30: Right-click on "Application_2" — Right-click on "Application_2"

First, we will remove the problematic simulation or application.

Step #31: Click on "Delete" — Click on "Delete"

We'll remove it. Yes.

Step #32: Click on "Yes" — Click on "Yes"

Now, we are going to rename this.

Step #33: Right-click on "Application_1" — Right-click on "Application_1"

Step #34: Click on "Rename" — Click on "Rename"

Rename it to Application Two.

Now we see a screen where we can update many tags.

Also, invisible tags. Previously, we could only change three tags and the name, for a total of four items. But here, there is much more. The first step is to tag application one to application two. This is for application one. That is the one we find most important.

Of course, we want to update all of them to prevent confusion and errors. All right, now click OK.

Now it's renamed. We can load our old application.

Step #38: Right-click on "SC" — Right-click on "SC"

Step #39: Click on "Load Application" — Click on "Load Application"

Load the application.

Step #41: Right-click on "SC" — Right-click on "SC"

Step #42: Click on "Load Application" — Click on "Load Application"

Application one, repeat.

Step #43: Click on "Application_1_repeat" — Click on "Application_1_repeat"

Step #44: Click on "Open" — Click on "Open"

Now we have our old application back.

That still has all the old tags.

Step #46: Click on "Dissolved" — Click on "Dissolved"

We cannot do it the other way around.

We cannot load application two directly.

Step #50: Right-click on "SC" — Right-click on "SC"

We can do that, of course. If we do it, we can rename it.

Step #51: Click on "Load Application" — Click on "Load Application"

Step #52: Click on "Application_1_repeat" — Click on "Application_1_repeat"

Step #53: Click on "Open" — Click on "Open"

Step #54: Click on "Please enter a new name" — Click on "Please enter a new name"

We can say three.

Step #55: Click on "Please enter a new name" — Click on "Please enter a new name"

The problem is that we have to manually update these tags. This is manageable, but it still requires some work. more problematic is that we cant update the invisible tags. See video for an illustration of what does not work.

For our application two, everything is done automatically.

We don't have to do any of that manually.

If we update our simulation using the building blocks, you can see that application one has the correct tag, application two has the correct tag.

In summary, what we need to to is: First, save the application, than rename (i.e. renumber) it. Then, upload the old application again. We have our two different applications.