Feedback
Did this article resolve your question/issue?

   

Article

OE BPM Form type workstep raises errors when changed to Custom JSP

Information

 
TitleOE BPM Form type workstep raises errors when changed to Custom JSP
URL NameOE-BPM-Form-type-workstep-raises-errors-when-changed-to-Custom-JSP
Article Number000138447
EnvironmentProduct: OpenEdge
Version: 11.7
OS: Windows
Question/Problem Description
OE BPM Form type workstep raises errors when changed to Custom JSP

When migrating a process with worksteps using 'Form' presentation types from Savvion to OEBPM, in Developer Studio (PDSOE) when the presentation type is changed to Custom JSP, this raises errors related to BizManageBean in the JSP file.

In OpenEdge 11.7 the 'Form' presentation type has been depricated:

User-added image
User-added image
User-added image

After changing the presentation to use a Custom JSP file, if the Custom JSP file is opened, the editor shows errors related to:

com.savvion.sbm.bizmanage.api.BizManageBean

and

com.savvion.sbm.bpmportal.bizsite.api.BizSiteBean


User-added image

Steps to Reproduce
Clarifying Information
Hoverring over the error doesn't provide any error message detail.  
Error Message
Defect/Enhancement NumberDefect ADAS-12565
Cause
The exact cause is not known at this time.
Resolution
None at this time.
Workaround
The errors only affect Progress Developer Studio.  If the users do not plan to make any changes to the process after it has been migrated from the earlier version, then they should be able to publish it successfully. The errors only appear in Developer Studio. Therefore:
  • If you don't change the process (i.e leave the presentation type as 'Form') it should still publish successfully and run in OE 11.7.x.
  • If you plan to change the process you will need to update the presentation type, this will raise these errors in PDSOE. But the errors shouldn't affect the runtime, so it should still publish successfully.
Notes
Last Modified Date12/14/2018 9:07 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.