Databases Reference
In-Depth Information
4.
Enter Test for the Name and Internal Name fields. Select “item” as the
type, and click the Create button to complete creating an empty plug-in,
as shown in Figure 2-3. All of the options will be discussed in the next part
of this chapter.
Figure 2-3. Creating a plug-in
Plug-In Components
It is important to have a good understanding of each of the options before building your first plug-in.
This section will cover all the available options or components involved in building a plug-in. If some
components seem a bit confusing, don't worry. They will all be used throughout the demos in this topic.
To help follow along, edit the Test“empty”plug-in that you created in the previous section.
Name
Like most APEX objects, the Name section allows you to define the name and type for the plug-in, as
shown in Figure 2-3
.
The following fields are required in the Name section:
Name
: This is the name that other developers will see when they use a plug-in
object. If developing plug-ins for the community, you may want to prefix the
name with your company name.
Internal Name
: This is a unique internal name that is not visible to APEX
developers. APEX uses the internal name to register your plug-in in an
application. It's recommended that you use the reverse DNS name of your
corporate website along with the plug-in name to help maintain uniqueness—
for example,
COM.CLARIFIT.FROMTODATEPICKER.
APEX uses the internal name to
determine if a plug-in is being installed or updated, so it's important not to
change it once it's been released. Once the plug-in has been used in an
application, the internal name cannot be changed.
