Making Smart Components Public

Make Public creates a new Public Smart Component from a Private one. The Public component is listed in the component tray and the Smart Components Hub for every Creator. The Build Agent prefers it when it reuses components. Use Make Public when a component the Build Agent built for one module is worth reusing across the environment.

The Private component is not converted. It stays in its module unless you delete it in the same step. For how the two states differ, see Public and Private.

A Private component belongs to the module that owns it. That module can place it any number of times, and no other module can place it. Make Public is how a component becomes reusable across modules.

What Make Public Does

Confirming the Make Public dialog does the following:

• Creates a new Public component with its own name. The new component is published immediately.
• Copies the Private component's definition and tests to the new component.
• Switches the instances you select to the new component. The other instances keep the Private component.
• Deletes the Private component when every instance switches and Delete private component is on.
• Saves the module. Unsaved module changes are saved first.

A Public component cannot become Private again. Public Smart Components are not versioned, so the new component is available on every branch and version. The instance switches and the deletion are module changes, so they save to the branch you have open.

Before You Begin

Making a component Public edits its module. The following must be true:

• The module is open for editing and you hold its lock.
• In a versioned application, you are on a branch. A published version cannot change, and an application without a branch must have one created first.
• Your role grants Create on Smart Components (Public) and Update on Smart Components (Private).

Delete private component displays only when your role also grants Delete on Smart Components (Private). Without that grant, the Private component always stays in its module.

From Module Builder, Make Public displays only while the module is open for editing and your role grants the permissions above.

Make a Component Public

You can begin in Module Builder or in the Smart Components Hub. Both open the same dialog in the module that owns the component.

To begin in Module Builder:

1. Open the module that owns the Private component.
2. Select the component on the canvas to open the Focused Component View.
3. In the toolbar, click Make Public.

To begin in the Smart Components Hub:

1. Click Libraries in the global header, then select Smart Components Hub.
2. In the Explorer panel, select Dashboard.
3. Above the component list, select Private. Public and Private display only when your role grants View on both Smart Components (Public) and Smart Components (Private).
4. On the component's row, click (ellipsis) and select Make Public.
5. In the Leaving the Smart Components Hub dialog, click Continue. The owning module opens with the Make Public dialog. In a versioned application, the module opens on the branch you last used.

If the module is not locked, a message asks you to lock it. The dialog opens once you do.

Make Public Dialog

The dialog title asks whether to make the named component public. The dialog has sections for the public component, the instances that switch, and the private component.

A note at the bottom of the dialog states when the module has unsaved changes. Making the component Public saves those changes first.

Click Make Public to confirm. A message confirms that the component is now Public and in the component tray.

Outcomes

The sentence in the Private component section changes with your selections, as follows:

A deleted Private component can be brought back by restoring an earlier module revision. See Deleting Smart Components.

Troubleshooting

The first three messages display when you begin in the Smart Components Hub. The last three display from either starting point.