A.2 Compatibility for service templates
This section describes the compatibility with earlier or later versions of JP1/AO.
- Organization of this subsection
(1) Compatibility for service templates and plug-ins created in the Service Builder window
The following describes the compatibility for service templates and plug-ins created in the Service Builder.
- Compatibility with later versions
Service templates are guaranteed to remain compatible with later versions. This means that you can work with service templates that meet the conditions below in the Service Builder window. However, some displayed items and operations might differ between versions.
Service template packages (*.st) created by users in earlier versions
Service templates and plug-ins imported to the JP1/AO server from an earlier version of JP1/AO
- Compatibility with earlier versions
Service templates are not guaranteed to be backwards compatible. If you attempt to apply a service template created in the Service Builder window to an earlier version of JP1/AO, an error might occur during the import process.
- Compatibility with JP1/AO servers with different operating systems
User-created service templates can be imported to JP1/AO servers with different operating systems. However, the following restrictions apply:
Only ASCII characters can be used for default values of input properties of plug-ins, and the values of input properties for plug-ins (or steps) in a flow.
Only service templates created in JP1/AO 10-10 or later can be imported to a JP1/AO server that is running Linux.
(2) Compatibility with steps in service templates created in earlier versions of JP1/AO
Some steps in service templates created in versions of JP1/AO earlier than 10-10 are not compatible with JP1/AO 10-10. This might prevent you from changing the processing in the step. The icon for steps that are incompatible with JP1/AO 10-10 is displayed in gray scale as shown below.
|
![[Figure]](GRAPHICS/F0000090.GIF)
You cannot change the processing defined in a step. You can only change the step ID, step name, and description.
The default step ID is compatible.step.
If there are multiple incompatible steps at the same hierarchical level, _n is appended to the end of the step ID (where _n is a unique integer greater than or equal to 2) to give a step ID in step-ID_n format. Step IDs are automatically assigned by the system. The value of _n has no relationship with the position of the step in the flow.
The description of a step is initially a null character.