Monday, February 24, 2014

ADF Form as Email Notification From Human Task

This blog will show how to use an ADF form to send email notification from Human Task, when some action is taken on a task by the user or the task is assigned to a user.

As a prerequisite email configuration has to be done on the server using Enterprise Manager and ADF form needs to be attached to your Human Task.

Once email configuration is done, we have to set up the notification in Human Tasks and modify ADF form so that we can send it as Email.

Below are the steps for sending ADF Form as email notification in From Human Task:
1.     Open a .task file (e.g AccountDistributionHumanTask.task) for which email notification needs to be set.

2.     Click on notification and go to Advanced Tab as shown below:

3.     You can select from two options as shown below:
We selected send individual mails in our case.

4.     Now go to General Tab and click on add icon to add Task Status and Recipient as to when and to whom you want to send the email notification:

5.     If you want to add a custom message i.e notification header, on the General Tab click on pencil icon under Notification Header column as shown in the screenshot below:

6.     Write your message in Edit Notification Message window as shown below and click OK.

Above settings will pick up the corresponding email id of the user either from mail attribute of embedded LDAP or from the task payload(depends on the requirement and implementation). In our case we are sending a link to Worklist Application, details of which is being picked up from payload for different environment.

7.     Now open the .jspx file in your ADF project and add a af:switcher inside af:form and move the default facet(e.g f:facet-Worklist) inside the af:switcher. In the same af:switcher add another f:facet(e.g f:facet-Email) for creating email content to be sent in the Email, below screen shot shows the structure of components:

For creating email content you can use datacontrol and drag and drop attributes as af:outputText to Email Facet(e.g select invoiceNumber and drag and drop on to Email Facet) as shown below:

8.      Add the following condition to FacetName property of the af:switcher to let it decide which facet to display:
#{pageFlowScope.bpmClientType eq 'notificationClient' ? 'Email' : 'Worklist'} as shown in below screenshot:

Now when you run your application, above condition will decide whether bpmClientType is notificationClient or not. If it is, then it will execute the Email facet and the response will be based on whatever you put under the Email facet. When the ADF form is accessed though a worklist, it will execute the “Worklist” facet and display the complete form for user entry.

On the other hand if you are not using ADF form, then the content of email will go into Notification Header as shown earlier or you will have to use email component of BPEL, where a lot of work has to be done in formatting because both will use html tags to create the content.

So, using the same ADF form, that you associate to a human task, you can generate the email notification.

Much thanks to Siddhartha Agarwal for today's post!

Thursday, February 20, 2014

Keep Current! - WebCenter Patches as of 2014/02/19

Hey all, 

In an effort to help everyone stay current, we're going to post some preferred patches on a regular schedule. This way, you'll have a single place to find all of the updated cumulative patches (MLRs, ARUs, Bundle Patches, etc) for the month.

Please be sure to let me know if there's any other patches that should be included on this list. The current format has the support recommended installs in bold & underlined, but there are some other nice-to-know patches included as well. These nice-to-know patches may not be necessary for your particular installation.

The formatting may change over time, but hopefully this is helpful!

** As always, please be sure to do your own due diligence before applying any patch. This list is for reference only.

Oracle Patches[1]

·       14538406 – 2012/09/17 – ODC Patch 4 for (cumulative)
·       16312671 - 2013/02/15 – CPUAPR2013 Oracle Document Capture (ActiveX IE killbit to prevent certain ActiveX controls; verify before installing!)
WEC (Capture 11g)
·       17951545 – 2014/01/21 – Cumulative Capture Patch #3
·       13882540 – 2012/04 – Critical Patch Update
·       13548500 – 2011/12/30 – Registry fix for searching for vendors with identical addresses
·       11813845 – 2011/02 - OFR Patch 1 (not cumulative)
·       12692984 – 2011/06 – OFR Patch 2 (not cumulative)
·       12372094 – 2011/04/27 – (updated ODC macros)

WebCenter Content Patches

o    18088049 – 2014/02 – MLR03
o    18188143 - 2014/08 – OIT cumulative patch
o    17823870 – 2014/01 - MLR04
o    18188143 - 2014/08 – OIT cumulative patch
o    17925241 – 2014/02 – MLR18
o    18188143 - 2014/08 – OIT cumulative patch

WebCenter Content Imaging Patches
o    18172749 – 2014/02/03 - CUMULATIVE IPM/AXF PATCH NUMBER 10
o    17056936 – 2013/07/21 - CUMULATIVE EBS PATCH NUMBER 1
o    16403418 – 2013/03/12 - CUMULATIVE FUSION APPS PATCH NUMBER 1
o    17565125 – 2013/10/06 - CUMULATIVE IPMREPOSITORY PATCH NUMBER 1
o    18108746 – 2014/01/30 - CUMULATIVE IPM/AXF PATCH NUMBER 23
o    17057174 – 2013/07/05 - CUMULATIVE EBS PATCH NUMBER 5
o    16547732 – 2013/03/29 - CUMULATIVE FUSION APPS PATCH NUMBER 4
o    18157769 – 2014/01/30 - CUMULATIVE IPMREPOSITORY PATCH #3
BAM Patches
·       (No cumulative patch threads could be found, but many one-off patches exist)

·       (nine new one-off patches since last month)
·       14491485
o    Bug #14491485

SOA Manager Patches
·       (Note that there are many one-off patches available)

o    17014142 – 2013/11/15 – Bundle Patch

o    16702086 – 2013/11/05 – Bundle Patch

** Note that there are multiple “merge request” patches per SOA release; they do not appear to be cumulative; please research and download as applicable for your version
WLS Patches
·       10.3.6
o    17071663 – BYJ1 - 2013/10/15 – WLS Patch Set Update
* Note that WLS has many one-off patches and “merge request” patches; please research and download as applicable for your version
WebCenter Portal

o    17641297 – 2014/01/14 – WebCenter Portal Bundle Patch

o    16761779 – 2013/07/23 – WebCenter Portal Bundle Patch
o    16269470 – 2013/07/23 – WebCenter Portal Bundle Patch
o    14823234 – 2013/07/23 – WebCenter Portal Bundle Patch

o    17328920 – 2013/09/25 – Content Presenter throws stuck thread and OOM when UCM returns many profiles

** Note that there are many one-off and “merge request” patches per Portal release; they do not appear to be cumulative; please research and download as applicable for your version

[1] *requires a valid support agreement to download patches

Changing the default admin password within the imaging solution

This post covers some of the locations where the change of default admin password is impacted in the Oracle imaging environment. This is assumed that we have used this user for universal integration among servers (which we may not recommend for production environments).

1.1      CSF Key

To modify the value of the existing value, follow these steps.

1.       Login to enterprise manager http://{host}:7001/em/
2.       Use administrator credentials, e.g. Weblogic
3.       From left panel, expand “Weblogic Domain”
4.       Right click on domain e.g. wci_domain
5.       Traverse {ipm domain} -> “Security” -> “Credentials”
6.       This page will show available csf maps. keys
6.1.     From the list select “basic.credential” key and click on “Edit”. Fill in the proper values in the popup.
6.2.     Click on OK buttons

1.2      ODC commit profile

1.       Start ODC
2.       Go to Admin – File Cabinets
3.       In each file cabinet commit profile using the I/PM 11g Commit Driver, click 'Configure' to access the Commit Driver properties
4.       In the configuration details page for Commit Driver, update the password
5.       Click on Ok

1.3      EBS Adaptor Configuration

1.       Connect to APPS schema.
2.       Here we need to execute below commands.
3.       The SOAP store password is in the vault. It can be changed by executing the following command (with the updated credentials):
execute fnd_vault.put('AXF', '{USERNAME}', '{PASSWORD}');

1.4      Changing in (if used)

1.      Login to Bali server using putty or winscp.
2.      Go to directory- $DOMAIN_DIR/servers/AdminServer/security    
Where the boot. properties file is located for Admin Server (Weblogic)
3.      Edit the boot. properties file
a.      modify the file as follows, with the updated credentials:


b.      These credentials are encrypted on the next start of the server
4.      Restart the server to verify the changes
5.      Repeat for all servers using the file

Thanks to Vikrant Korde for today's post!