Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.
Using plug-in naming conventions
Plug-in names must be unique. The following is an example of a proper naming convention:
companyName.pluginType.uniquePluginIdentifierName
For example, if your company name is Apex Global, the type of plug-in is ARDBC, and the unique plug-in identifier is pluginexample1, your plug-in name could be the following:
APEXGLOBAL.ARDBC.pluginexample1
Plug-in names cannot include spaces or tab characters. In addition, uniquePluginIdentifierNamecannot contain the word AREA by itself because that word is reserved for AREA plug-ins. However, you can use AREA as the pluginTypevalue.
