Other Resolved Issues

This section lists the issues that were resolved in each release but were not part of the fixes listed in the previous section. A release is listed in this section only if changes occurred in that release.

Release 10.11

  • WTN-5248
    Adding a comment to a task instance using the Task Engine REST services in My webMethods Server fails with a "500 Internal Server Error".

    The issue is resolved.

  • WTN-5240
    When installing the Task Client package on Microservices Runtime, the required dependency to My webMethods Server Libraries does not get selected automatically and all Task Engine services, or attempts to modify the default configuration of the package fail with an error.

    The issue is resolved.

Release 10.7

  • WTN-5216
    Task Engine on Integration Server might not parse task schedule dates correctly and fail to queue task instances form a type. This issue occurs when selecting the schedule date from the calendar picker in the Task Engine UI.

    The issue is resolved.

Release 10.5

  • MWS-25765
    Task Engine might fail to fire scheduled events if the schedule coincides with redeployment of the task application.
    The issue is resolved.

Release 10.4

  • WTN-4370
    When you configure a JMS provider for the wmTaskEngine package using the Command Central web user interface, you cannot set the field back to an empty value.
    The issue is resolved.

Release 10.3

  • MWS-23917
    Task Engine might schedule and fire events at unexpected times.
    This issue occurs for the following task event configurations:

    • When you configure task events with binding expressions for schedule time offsets and the binding expressions do not resolve to a number. Task Engine schedules and fires the events immediately.

    • When you configure task events without business calendar, but a default business calendar is configured in My webMethods Server. Task Engine will comply to the default business calendar, regardless of the event configuration.
      The issue is resolved. Task Engine no longer schedules task events if the binding expression for date/time offset does not resolve to a numerical value.
      Tasks Engine no longer uses the default business calendar when calculating event schedules. You can control this behavior by adding the following system property to the custom_wrapper.conf file for My webMethods Server:
      -Dtask.events.use.default.calendar=true
      By default the property is set to false (not present) and Task Engine does not use the default business calendar of a user when scheduling task events, as documented.

Release 10.2

  • WTN-3733
    My webMethods does not display details about a step in a collaboration process.
    On the Collaboration Processes \> Process Details page, when you select a step in a collaboration process, the Step Info, Task Info, Task Audit, and Task Comments tabs on the Details panel do not
    display any information about the step. Only the Process Info tab contains any information.
    The issue is resolved.

Release 10.1

  • WTN-4000
    A security issue with password masking was discovered in the WmTaskClient package in Integration Server. 
    The issue is resolved.

Release 10.0

  • WTN-2749
    The WmTaskClient package does not support case-insensitive index searches.
    You cannot use WmTaskClient package services to perform an indexed task search with a search query term that is case-insensitive.
    The issue is resolved.

Release 9.12

  • WTN-3684
    On the Business Data page in My webMethods, the Intrinsic Task Metrics event maps are improperly set as user-defined.
    When you expand the Intrinsic Task Metrics node on the Administration \> Analytics \> KPIs \> Business Data page in My webMethods, the DEFINED BY column for the Intrinsic Task Metrics event maps displays the value of "User". However, intrinsic event map and KPI definitions should be system-defined to prevent users from deleting or modifying the definitions.
    The issue is resolved. The DEFINED BY column for the Intrinsic Task Metrics event maps now has a value of "System".