New Features › CA Process Automation Release 04.2.00 › User Experience Improvements

User Experience Improvements

Summary

• Support for purging aged Reporting data.
  • Formerly, there was no easy way to purge reporting data. Any application that shared storage with the Reporting database could be affected if the database reached capacity.

    Note: We recommend that the Reporting database be located in a dedicated database instance.

  • Now, at the Domain level, you can schedule a daily purge of reporting data over a configured age. You can also purge on demand all reporting data started within a specified date range. See the Content Administrator Guide for details.

    Note: The default settings enable process reporting and enable operator reporting, but do not schedule purging.

• Support for deleting and purging checked-out objects.
  • Formerly, you had to check in an object before it could be deleted or purged.
  • Now, an administrator can delete and purge checked-out objects.
• Persist WSDL URL in SOAP operator wizard.
  • Formerly, entries for WSDL URLs were not saved.
  • Now, you can use the WSDL explorer to select a previous entry from a drop-down list.
• Install as Windows Service option is set as the default for Orchestrator installations on a Windows server. You can also start the caitpamserver service from the command line.

Details

You can now purge reporting data as you can purge archived instance data for the processes you run. Purging criteria is based on the start time of a process or operator. (This is different from the criteria used for purging archived processes, which uses the end time.)

Options include:

• Purge the Reporting data daily at the specified time; data that is older than the configured number of days is deleted.
• Do not schedule a purge of reporting data.
• Purge all reporting data within a specified date range on demand.

All Orchestrators in all environments in a Domain typically share a common Reporting database, by default. Purge settings apply only to this common Reporting database. An administrator can edit the OasisConfig.properties file to change the configuration of a selected Orchestrator to point to an external reporting database. The reporting data settings and actions that are configured through the UI apply only to the common Reporting database; they do not apply to external reporting databases.

To increase the control that authorized users have over the Library, administrators can delete objects that are in checked-out status. This ability extends to content designers who own the checked-out objects.

• Administrators can purge checked out objects from the Recycle Bin.
• To alert administrators when selected objects or folders include checked-out objects, the purge process lists any checked-out objects in the confirmation message. The administrator can then verify that the checked-out objects were not inadvertently deleted before confirming the purge.