A new activity has been added to allow one to easily call REST endpoints.
The Integration activity has been improved to address both reported bugs as well as requests from the field. It is important to note that these improvements are not dependent upon any server changes, so it is possible to take advantage of this new functionality even if the server is not at the latest release level.
Previous releases have used custom code to generate the SOAP xml. There are some situations where the xml generated there was not 100% correct, so it had to be hand tweaked to provide the SOAP message that was expected by the server. For Designer 4.0.2, an option was added to utilize the SOAP UI code to generate the SOAP message. SOAP UI (www.soapui.org) is the leading open source SOAP tool. This generally results in less hand tweaking, as the SOAP message generated by SOAP UI has proved to be more accurate than the previous proprietary code. Utilizing this code is a matter of checking a checkbox on the import WSDL dialog, which is on by default.
As a direct side effect of this, it is now possible to map values directly to SOAP Header messages without resorting to modifing the Integration Activity's action model. This is required by some SOAP Services, Remedy SOAP integration is such an example.
Changing the SOAP endpoint URL (example: between test and production) used to involve having to go into the action model to update the expression inside the WS Interchange action. This has been simplified by exposing this expression right on the data item mapping panel. If the server level is 4.0 or higher, it is recommmended to use a GCV expression to simplify this even further.
Changing the SOAP endpoint userid and password (example: between test and production) used to involve having to go into the action model to update the connection information expressions inside the WS Interchange action. This has been simplified by exposing these expressions right on the data item mapping panel. If the server level is 4.0 or higher, it is recommmended to use a GCV expression to simplify this even further.
If a SOAP fault occurred during execution of the integration activity, details on the SOAP fault would be automatically be mapped to flowdata via hidden data item maps. These hidden maps are now exposed in the UI. This makes it possible to construct a workflow that has centralized error processing for all integration activities if that is desired. This could be accomplished by ensuring all integration activities map their faults to a common location in the flowdata document, and having all integration activity fault paths go to a common activity.
Utilizing the legacy way of creating the Integration activity required the system to preserve a copy of the WSDL embedded into the workflow, as it was required at runtime. This is no longer required if SOAP UI generation is used. This can significantly reduce the size of the workflow, especially if the WSDL is complex.
An important feature is the ability to animate the Integration Activity action model in design time to test the SOAP calls to the SOAP Service. There were problems in that area that have been addressed.
NOTE: There are a few bugs in the password CGV area that prevent it from working correctly. Please keep these in mind when using this feature in conjunction with password expressions.
Workaround: Ensure server is at 4.0.1, as otherwise password GCVs do not work at all
Workaround 1: Ensure the expression for the password-ref GCV is in the format of GCV.getValueForNamedPassword('password')
Workaround 2: In addition to defining the password-ref GCV, it is required that an additional GCV has been defined in order to enable it. (This was done as for security purposes). To do so, define a boolean GCV named "allow-fetch-named-passwords" on the driver and set it to true.
Workaround: Ensure all password GCVs are created on the driver, not the driver set.
Added an option not to import the roles and resources (excluding system roles)
Importing thousands of roles from the Identity Vault is painful and takes forever. User has no need to manage them using the Designer. So an option is provided to exclude roles and resources from being imported into Designer.
User can set the option using Window > Preferences > Novell > Provisioning > Import/Deploy > Role Catalog
In Designer 4.0.2, deletion of roles in the Provisioning view is more efficient than the previous versions of Designer. Instead of deleting a role, Designer sets the nrfStatus flag to DELETE_PENDING, which removes the role and hides it from the Provisioning view. When the User Application driver is deployed again, the role is set to delete pending status in the Identity Vault. The Roles driver processes these roles for deletion.
In this release, an option has been added to set the role revocation flag from the Role Editor in Designer. In the Role Approval tab, you can set and unset Revoke Approval Required flag. When the role object is deployed, if the Role Revoke Approval Required flag is set, it sets the PRD DN on nrfRevokeRequestDef attribute. On importing the role object, if the role edirectory object has a value set for nrfRevokeRequestDef attribute, it sets the Role Revoke Approval Required flag for the role object.
In this release, password-ref GCVs are added in the Ecma Expression Builder in workflows. Expressions generated using the Password-ref GCVs in the Ecma Expression Builder can fetch password at run time.
In Designer 4.0.2, the password-ref GCVs in Ecma Expression Builder generates expression in the form of GCV.getValueForNamedPassword('password-ref') instead of GCV.get('password-ref'). The resulted expression can be used to fetch the password at runtime.
NOTE: The GCV boolean value "allow-fetch-named-passwords" should be set to fetch the password at run time. If it is not set, the tool tip for password-ref GCVs warns you indicating the password will not be fetched at runtime.