How to call REST API from JDeveloper 10g

20-Nov-2024
How to call RESTAPI from JDeveloper 10.1.3.5

Actionable Email Approvals not Reflected in Fusion Applications

Created: 05-Feb-2017

Purpose:
In this article we will see how to resolve issue with actionable email not reflected.

Steps to indentify the problem:
Email notification is sent to approver.
Approver clicked 'approve or reject' link and responded the notification.
Human task notification is still pending.

Go to EM and look for log message.

Module: Module oracle.sdp.messaging.driver.email

Message: Message An unexpected exception was caught.

Details:

java.lang.IllegalStateException: Not connected
at com.sun.mail.imap.IMAPStore.checkConnected(IMAPStore.java:1493)
at com.sun.mail.imap.IMAPStore.getFolder(IMAPStore.java:1324)
at oracle.sdpinternal.messaging.driver.email.EmailStore.openFolder(EmailStore.java:139)
at oracle.sdpinternal.messaging.driver.email.MailboxPollingWorker.getInitializedEmailStore(MailboxPollingWorker.java:107)
at oracle.sdpinternal.messaging.driver.email.MailboxPollingWorker.run(MailboxPollingWorker.java:47)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:95)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

If you notice above mentioned error then please follow steps to possibly solve the problem.

Solution:

The issue is email account was setup with upper and lower case but while entering email properties in UMS it was defined in lower case.

WebCenterWorkflow@Oracle.com
webcenterworkflow@oracle.com


When soa server is restarted the email entered in UMS proprty is set in message client application access point as shown below.

email account is k-sensitive. 

if you go to UMS property and correct the email and access point is not updated. 

so use 'De-register' option to remove existing email from access point.

Make sure valid email account is configured in UMS property 

Restart the soa server.

Retest actionable email and you should not see any error in the log.

For more details refer to:

Actionable Email Approvals not Reflected in Fusion Applications (Doc ID 1960637.1)

Thanks for visiting my blog.

xp20:compare function in BPEL

When you use xp20:compare function you get below error.

xp20:compare($in.payload/tns:taskAssignedMessage/task:task/task:sca/task:compositeName, 'HumantaskPJ1')

Non Recoverable System Fault :

ORAMED-01102:[Filter Expression Metadata Error]Error evaluating filter expression, "xp20:compare($in.payload/tns:taskAssignedMessage/task:task/task:sca/task:compositeName, 'HumantaskPJ1')".Root-cause: "java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement cannot be cast to java.lang.String". Possible Fix:Ensure that the filter expression metadata is valid, otherwise Contact Oracle Support Services.

to fix the problem use 

xp20:compare(string($in.payload/tns:taskAssignedMessage/task:task/task:sca/task:compositeName), 'HumantaskPJ1')

How to create BPEL flow with Business Rule

In this article we will see how to create simple BPEL process and use Business rule.

Use Case:

Payload has Employee name and Salary. Based on Salary want to return what type of rule Employee can be.

For instance 

if the employee salary is between 0 to 50 then their role would be JUNIOR

if the employee salary is between 50 to 100 then their role would be ANALYST

if the employee salary is greater than 100 then their role would be SENIOR

Below attached video show how to define simple BPEL process with Business rule which satisfies above mentioned use case.

Also attaching source code.

Download source code