OUAF Release 4.3.0.0.0

Bug: This change was made to pass down the action details to BusinessObjectEnterStatusAlgorithmSpot and BusinessObjectExitStatusAlgorithmSpot.

17230588 - EXPOSE ACTION IN BO STATUS PLUG-IN SPOTS

com.splwg.base.domain.common.businessObject. BusinessObjectEnterStatusAlgorithmSpot

New Method:

/**

* Set the Action of Business Object

*/

void setAction(BusinessObjectActionLookup boAction);

Change Description: The method is added to the plugin spot to pass down the action information to all implementation classes.

Note: As the spot is changed, all implementation classes should implement the method. Implementation can be left blank if the algorithm does not need the action information.

Code Example 1 (preferred):

//Before Code:

There was no setAction() method.

//After code:

public void setAction(BusinessObjectActionLookup boAction) {

// null

}

com.splwg.base.domain.common.businessObject. BusinessObjectExitStatusAlgorithmSpot

New Method:

/**

* Set the Action of Business Object

*/

void setAction(BusinessObjectActionLookup boAction);

Change Description: The method is added to the plugin spot to pass down the action information to all implementation classes.

Note: As the spot is changed, all implementation classes should implement the method. The implementation can be left blank if the algorithm does not need the action information.

Code Example 1 (preferred):

//Before Code:

There was no setAction() method.

//After code:

public void setAction(BusinessObjectActionLookup boAction) {

// null

}

Alta Look and Feel

As a part of the new user interface, OUAF now supports browsers in standards mode; for example, Microsoft Internet Explorer (MSIE) is supported in standards mode and not in compatibility mode. This may change the behavior of various UI elements such as HTML, JavaScript, and CSS, due to the underlying execution mode change in the browsers.

Previously, for example, firstChild on a certain DOM element would return the first child node of the element in the DOM but would ignore text nodes such as new lines, blank spaces, etc. Now, text nodes are no longer ignored, and firstChild will return the first child of the element in the DOM, which may be a text node.

For example, for the following XML snippet,

<root>

</root>

firstChild on the <root> node will return a text node in MSIE (running in standards mode) in the new OUAF version, while in earlier versions it would return <foo>.

OUAF provides a cross-browser API with abstract browser variations to return consistent objects. The API can be found in the OUAF source file, common.js; refer to the file for additional details.

Bug Fix: JS API - handleExpand/handleCollapse Methods in xslInclude.js

Bug: handleExpand() and handleCollapse() functions in xslInclude.js used to expand/collapse a zone. Prior to Framework 4.3, these functions expected one or two arguments to expand/collapse a zone. However, since the release of Framework 4.3, these functions do not work as expected with a single argument. They now accept only two arguments, e.g., sequence id of the zone, and user event object, to work as expected. The API change was a part of overall standardization and adoption of best practices for the JS layer to enable cross-browser support. Refer to patch 23745289 for details.