Like program-based plug-ins, plug-in scripts:
- Run on the application server
- Have their API (input / output interface) defined by the plug-in
spot (i.e., plug-in scripts don't get to declare their own API)
- Can only be invoked by the "plug-in spot driver"
The best way to understand a plug-in script's API is to use the View Script Schema hyperlink to
view its parameters data area schema.
Notice the two groups: soft and hard. If you are familiar with
plug-in spots, you'll recognize these as the classic soft and hard
parameters:
- The soft parameters
are the values of the parameters defined on the algorithm. Notice
they are not named - if you want to reference them in your plug-in
script, you must do it by position (this is equivalent to what a Java
programmer does for plug-ins written in Java).
- The hard parameters
are controlled by the plug-in spot (i.e., the algorithm entity). Notice
that this plug-in spot has a single input parameter called " businessObject/id". Also notice the use= attribute - this shows that
this parameter is input-only (i.e., you can't change it in the plug-in
script).
Note:
XPath. You can click on an element name to see the
XPath used to reference the element in your script.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]