1.7 List of service template development features
The following table lists the features of JP1/AO that are used in the development of service templates.
Feature |
Description |
Refer to |
|
|---|---|---|---|
Creating and editing service templates |
Creating and editing definition information |
Users can create new original service templates. Users can also edit service templates and change information (such as, the service template names, descriptions, service properties, and custom files). |
2.2 Creating and changing the service template definition information |
Adding steps |
Users can add steps to a flow to place necessary processing in a task. Users can also edit the definition information of steps. |
||
Defining the execution order of steps |
Users can add steps and connect them by relational lines to define execution order of the processing. |
||
Setting step properties |
Users can dynamically or statically set the property values used when services are executed. |
||
Setting service properties |
Users can define the input items when setting or executing services, or the items displayed when checking the execution result. |
||
Managing the versions of components used as steps |
Users can check and change the version of the components used as steps. |
||
Setting display information of service templates |
Users can set the display information of service templates (such as service template names and descriptions) in resource files. Note that resource files can be set for each locale for the Web browser. |
2.3 Setting display information for service templates in resource files |
|
Managing service templates |
Viewing service templates |
Users can view the definition information and detailed processing of service templates. |
|
Copying service templates |
Users can copy service templates. Users can also edit the copied service templates and create new service templates. |
||
Deleting service templates |
Users can delete service templates. |
||
Releasing service templates |
Releasing validated service templates creates the packages of the service templates, and they are imported to the JP1/AO server. Service templates after being released, cannot be edited. To move service templates from the development environment to another environment, users must manually import the service templates. |
||
Exporting service templates |
Users can store service template files in any folder. |
||
Importing service templates |
Users can import service templates to the destination environment when moving the released service templates from the development environment to another environment. |
||
Creating and editing plug-ins |
Creating plug-ins |
Users can create new original plug-ins. |
6.2 Creating and editing plug-in definition information, 6.3 Setting plug-in properties, 6.4 Editing platforms |
Editing plug-ins |
Users can edit plug-ins, by setting the plug-in names, input properties, output properties, and remote commands. Note that users cannot edit plug-ins provided by JP1/AO. |
||
Setting display information of plug-ins |
Users can set the display information of plug-ins (such as, plug-in names and descriptions) in resource files. Note that users can set resource files for each locale of the Web browser. |
||
Managing plug-ins |
Copying plug-ins |
Users can copy development plug-ins and release plug-ins, and create new plug-ins by editing the copied plug-ins. |
|
Deleting plug-ins |
Users can delete development plug-ins and release plug-ins. |
||
Validating service templates |
Building service templates |
Building service templates creates packages for the service templates being developed, and then they are imported to the JP1/AO server. This processing is performed to validate service templates. |
|
Debugging service templates |
Users can check the behavior of service templates that were built, and find problems. If debugging finds a problem in flows or plug-ins, users can edit the service templates or plug-ins. |
||
Conducting operation tests for service templates |
Users can create and execute services from the service templates that were built, and find operational problems. If operational tests find a problem, users can edit the service templates or plug-ins. |
||