Upgrading the CloudBees Analytics server. Configuration settings preserved after an upgrade. Credentials and user impersonation. Credential management. Using credentials. Impersonation concepts. Use Case: using credentials in deployment automation. Cross-site request forgery protection. Changing the database password. Switching to an alternate database.
Switching to the built-in database. Maintaining CloudBees Analytics server data. Apache web server or agent certificates. Using chkconfig. Starting and stopping servers and agents manually. Web interface online help system. Windows PHP does not handle time zones correctly. The AES passkey was accidentally overwritten. Linux upgrade breaks symbolic links. Troubleshooting pipelines. Automation platform. Build-test automation. Getting started. Automation platform setup.
Automation platform objects. Using special characters in object names. Automation platform tasks. Artifact management. Database configuration. Defect tracking. Email configurations and notifiers. Event log. Plugin manager. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Important Whenever possible, you should first consider applying one of the several declarative options to define business logic.
Is this page helpful? Yes No. Any additional feedback? Skip Submit. Salesforce Sites. Support Classes. Territory Management 2. Integration and Apex Utilities. Debugging, Testing, and Deploying Apex. Apex Reference. Plugin Interface Process. Plugin is a built-in interface that allows you to pass data between your organization and a specified flow.
Once you implement the interface on a class, the class can be referenced only from flows. The annotation supports all data types and bulk operations. PluginDescribeResult Returns a Process. PluginDescribeResult object that describes this method call. PluginRequest Process. PluginResult Primary method that the system invokes when the class that implements the interface is instantiated. Example Implementation. The Flow calls this at runtime. PluginResult invoke Process. PluginDescribeResult ; result.
InputParameter 'subject' , Process. Test Class The following is a test class for the above class. PluginRequest inputParams ; plugin. Cookie Consent Manager. General Information. Required Cookies. Functional Cookies. Advertising Cookies. General Information We use three kinds of cookies on our websites: required, functional, and advertising. Streams produced by the plug-in to send to the browser are like normal-mode streams produced by the browser, but in reverse.
In the browser's normal-mode streams, the browser calls the plug-in to inform it that the stream was created and to push more data. In streams produced by the plug-in, by contrast, the plug-in calls Netscape functions to create a stream, push data into it, and delete it. For information about using these methods, see URLs. Starting in Gecko You can use these Netscape methods:. Functionally, your plug-in is seamlessly integrated into the browser and operates as an addition to current browser capabilities.
To make the user feel that the plug-in is part of the browser user interface, your plug-in can emulate the browser behavior by providing status line messages. Scriptable plug-ins are plug-ins that have been extended to provide methods that can be called from JavaScript and the DOM when accessed through the object or embed element. Consider the following example, where a media player plug-in can be controlled with an advanceToNextSong method called inside the script element:.
See the Wikipedia article for historical information. Both technologies are now obsolete for the purposes of plug-in scriptability, and the cross-browser npruntime API should be used instead. See the Scripting plugins section of this reference for the details. Once you have added the special code and additional files to make your plug-in scriptable as described in the previous section, the build process is quite straightforward.
In addition to the DLL that goes in the plugins folder, you must also place a type library and an extra header file in the appropriate places in your application directory.
This section describes those extra scriptability steps in more detail. Plug-ins should not be installed into the Firefox directory. The plug-in installer should either package the plug-in into an extension and install it using normal extension installation practices, or install the plug-in to the system standard install locations.
Then the following registry values should be added to the Windows registry the plug-in-identifier should follow the specification :.
0コメント