Discussion
Cognizant
IN
Last activity: 6 Apr 2018 19:26 EDT
Upgrading Activities built on JAVA API Version 02
Setting the context ...
We are upgrading from 6.2.1 to 7.1.9
In the 6.2.1 application we have an activity that was originally built in 5.X.X using JAVA API Version 02
This activity uses a function called sendData(String,String)
This function has been deprecated (OR) has been replace by another function with a similar name in JAVA API Version 03-02 , we know this because when we attempt to change the JAVA API Version from 02 (to) 03-02 in the concerned activity it throws an error. Such changes are possible in 6.2.1 because it provides a drop down to choose a JAVA API Version in all activity rule forms under the 'Steps' tab; this is only meant for backward compatibility with V5. No such option is available in 7.X.X
Questions I have are ...
- Is this going to be a problem post upgrade to 7.1.9 ?
- Will the upgrade script take care of function name changes between JAVA API versions (02 Vs 03-02) ?
- If the scripts do not take care of this then should we take care of the changes manually as part of pre-upgrade steps ?
- Is there a list somewhere in PDN (OR) with 'ECS Team' that has "all deprecated functions + all functions that have been renamed" in JAVA API 03-02 (Vs API 02)?
NOTEs #
- To know which JAVA API Version is being used by your activity; Actions >>> View XML >>> Pop-up >>> Lookup xml tag pyJavaGenerateAPIVersion
- By default any activity built in V6/V7 can only use JAVA API 03-02
REFERENCE #
- https://pdn.pega.com/forums/java-activities/api-02-03-02
- https://pdn.pega.com/forums/java-activities/api-20-32
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
Hi,
This version upgrade would be automatically taken care.
Ideally, it would not create any issue.
When you are trying to use the new APIs available or methods available in the latest version then this version should be the latest.
My understanding was that the update of this version would be done when you try to make changes to the rule itself.
Cognizant
IN
Yes, we attempted to update the API version when we tried to make changes to the activity rule itself in V6.2.1
The activity was originally built in V5.4.1 and at some point in time it was imported into V6.2.1
We faced the error when trying to edit the concerned activity in V6.2.1; this was part of our pre-upgrade rule remediation stage.
Pegasystems Inc.
IN
This is fixed in 7.2. Please refer the below article.
Updated: 26 Apr 2016 1:24 EDT
Cognizant
IN
@ Saikatc8
According to Chaitra 02 >>> 03-02 API conversions are automatically taken care during the upgrade for all concerned activities.
Article 1052051 talks about only one activity ExportToExcel that will not be addressed during the upgrade (it was a miss) hence it caused a SR A10178
Anyway thanks for mentioning this.