| 2024 Q4 |
- A new menu item called Decision Tables has been implemented enabling users to create and manage rule sets. Users can now refer to inputs in the decision table by their names instead of variables for easier understanding.
Further improvement to Decision Tables includes importing/exporting table data group, as well as importing/exporting table data between the PO systems. The users will now be able to import and export table data group within a decision table, in the form of a CSV file. Also, the users can import and export decision tables, as a .json file.
In the decision table task template, there is new column called Default Value that lets users easily create decision tables with pre-populated values. The new field is only applicable to outputs and disabled for input types.
Another improvement to the feature is the ability to delete a decision table group from a decision table, as well as separate rows from a table group. More details about this feature can be found in the User Guide.
- A few improvements to the Process Orchestrator WiX Installer have been made. The users will now have the option to install the Worker Service component in the Admin Tool. In addition, the silent install option for the Worker Service is also available. Admin Tool now supports the SSL certificate option, so that users can determine what SSL certificate to use. In the Server Components section of the Admin Tool, fully qualified names of Service URLs are now shown. Lastly, if users want to uninstall Process Orchestrator, they can do so from Control Panel or choose the Remove option from the Process Data Setup. For more details, refer to the Process Orchestrator Installation Guide.
- Process Orchestrator is now available as an optional component in the Prophet Enterprise installer. For more information, check either Process Orchestrator or Prophet Enterprise Technical Guide.
- The users will now be able to delete a process definition only for process instances that are Aborted or Completed, so that the ongoing process flows are not interrupted.
- The IDR Direct Mode task template now supports Text Source. This means that the users will now be able to run IDR Direct mode with new parameters: Sourcetype (mandatory field), Parameters and FileNames. Furthermore, the users will now be directed to AgentAPI instead of ControlAPI in Admin Tool. For more information, please refer to the User Guide.
- The users will now be able to run the IDR Stream Mode task template with the new parameters: QConfigurationId, QConfigurationName, Queued, CheckAfter and Fragment.
- We have made some improvements to the Polling consumer. Prophet Enterprise, Assumptions Manager and IDR can now queue multiple queries for completed job. Only one query should be active at any time for any active job.
- The Individual Policy Results Definition and Aggregation Results Definitions fields have been moved from the PE task template to the Run Settings task template, so as to match the Flexible Results field in Prophet Enterprise, and thus include these options in a job run.
|
- When running a process, it would not always suspend if an error occurred, but instead it would keep initializing. The issue has been fixed, and the process will be suspended so that the user is allowed to retry the task.
- Tasks were not getting cancelled when a process terminated. It was showing ‘execution in progress’ instead. This is now fixed.
- When installing Process Orchestrator in PDAdmintool, the credentials vault section and service URLs would not save. This issue is now fixed.
- Prophet Enterprise jobs with dependencies would not return dependent job information. This issue is now fixed.
- Run External Program task template was not accepting program file location. This issue is now fixed.
- Once IIS is reset on a server, file watcher stopped working. The issue is now fixed.
- When leaving client variable value as blank from the UI when starting a process, the variable is not resolved to a blank value but retains the variable name as value. ex. [TheProcessID]. This issue is now fixed.
- The PE Task Template was not ignoring empty parameters (either Parameter or Category value). The process should not be failing if any of the values are blank. This issue is now fixed.
- On task failure, the task was retried repeatedly. This issue is now fixed.
- When multiple Prophet Enterprise jobs were submitted at once, the CPU on the worker server stayed at 99% as the worker was checking on the finished jobs. This issue is now fixed.
- Wording in the dialog box for importing a decision table has been corrected to show whether a user wants to overwrite existing data or merge data sets.
- PE Run Structures task template would fail each time it was run. This was due to the accumulations options being selected in Prophet Enterprise. This issue has been solved by adding value on the selectaccumulation column that clears out the selected accumulation values from the list.
- Approval and External tasks couldn’t be skipped with a conditional expression. If a conditional expression was assigned, it evaluated to false, the tasks were not skipped. This has now been fixed.
- Outputs were not getting retrieved from a decision table when conditions match. This issue is fixed.
- When viewing details for a worklist item, the tasks were shown with 0 or 1 ahead of the task name instead of the sequential/parallel indicator. This has been fixed.
- Output variable was incorrectly set from PowerShell script. This has been fixed.
- An approval task in a process could be deleted. This action should have been throwing an error each time a deletion is tried. This is now fixed.
|
| 2023 Q2 |
- Process Orchestrator now supports secured LDAP connection (LDAPS).
- Process Orchestrator now works with Prophet 2021 Q2 (9.3.0).
- The create new process wizard has been improved and now by default only contains blank process as an initial process template to start from.
- The dropdowns containing task templates can now be filtered when creating or updating process definitions.
- Users now can enter variables defined in sub-processes when a new process is started.
- Processes that fail due to system or service downtime are now recovered automatically by the workflow engine.
- When a user views the history details for a process instance, the process instance will automatically refresh every 30 seconds. Previously the history would have to be manually refreshed by the user.
- Output variables can now be set from external integration tasks.
- Users can now add parameters, key/value pairs into the external integration task template. When an external task retrieves the external integration task, the parameters included with the task. The parameters can reference variables or fixed values.
- The wording for task statuses has been improved to give the user clear understanding of the task status.
- When exporting and importing process definitions, variables referenced in the task templates are now imported and exported along with the process.
- Task template fields can now contain multiple variables. Previously only one variable was allowed per field.
- A new view was created to support Prophet domain reference. For each prophet domain reference, user specifies the Prophet domain url, version number, authentication mode and the server location.
- The columns in grids showing list of task templates, process definitions, process history and worklist can now be resized.
- When a new process instance is created, a process instance id is automatically assigned to the process. The format of the id is: PIDyyyymmddn, where yyyymmdd represents the current date and n is a numeric value that increments with each new process instance. Users can also submit their own process instance id, which replaces the automatically generated id. The process instance id is shown in the process history.
- The Process Orchestrator solution has been upgraded to run under .NET Core 6. The previous version used .NET Core 5, which has been deprecated.
- The Process Orchestrator grids that show the list of items (Process Overview, Worklist, Task Templates, Process Definitions) have been modified to use server side paging to improve performance and responsiveness of the user interface.
- Process Orchestrator supports Prophet versions 2022 Q2 and 2023 Q2. Previously only 2022 Q2 was supported.
- The Process Orchestrator Web API is not authorized by role.
- Process Instances can now be deleted from the process history view. A user with system administrator role can select one or more process instances and delete them. This will remove the process instance from the database audit trail permanently and remove all history related to the process instances.
- A user can now delete a process instance from the process overview.
- The Process Orchestrator logging has been enhanced and now the request and response objects for tasks that are executed are logged.
- When Process Orchestrator executes a DCS script, the resulting log file is returned to the process. In some cases, DCS generates very large log files, causing failure in Process Orchestrator to receive the entire content of the log file. Now the amount of data returned from the log file can be configured to avoid failures due to large log files. The default is 5000 characters and is set in the DCS service config file using the prophet.DCS. MaxMessageSize variable.
|
- When exporting a process definition, the roles used in the process were not exported correctly. The issue has been corrected.
- When an External Integration task failed, the user could not retry the task. The issue has been corrected.
- When a user logs in to Process Orchestrator for the first time, active directory roles associated with the user are saved in the database. When the user logged in again, the roles were not refreshed. The issue has been corrected and the user roles are now updated on each login.
- Process Orchestrator installation failed when user selected SQL server database with instance that is not the default instance. The issue has been corrected.
- When a user started creating a parameter in Prophet Enterprise Studio, but did not save the parameter, job submissions for Prophet Enterprise and Assumptions Manager jobs failed in Process Orchestrator due to the incomplete parameter. Incomplete parameters are now ignored, and jobs can be submitted.
- When users with limited privileges logged into Process Orchestrator, they could see menus that they did not have rights to access. The issue has been corrected.
- When a user navigated away from a screen with unsaved data, no warning was given to the user and the unsaved data was lost. Now, the user gets a warning and is prompted to either discard or save the data.
- When a Process Orchestrator workflow service is down due to misconfiguration, a confusing error message was shown. The error message has been improved allowing users to pinpoint the root cause of the issue.
- For Approval and External integration tasks, the performing user was not shown in the process history. The issue is corrected, and the user id is now shown.
- For client variables of type list, the options list could not be changed once the variable was created. The issue has been corrected.
- When submitting a Prophet Enterprise job with more than two levels of job dependencies, the job was not submitted correctly, and the parent job was not submitted. The issue has been corrected.
- The process overview contains icons that show process counts for various process states (active, completed, suspended and terminated). When the process counts where high, the numeric counts could not be read. The issue has been corrected.
- The start process trigger file format was modified to support format of a CSV file, where the first line is comma separated client variable names and the second line is comma separated values.
- When a user started a process from the application and chose a file to set client variables, variables of type list were not filled. The issue has been corrected.
- When opening an output variable for editing, the step and task for the variable were not displayed. The issue has been corrected.
- When creating a new variable of type List, the variable value did not allow a value used in another variable list. The issue has been corrected.
- If a process was started and an error occurred on startup of the process, no error was shown to the user. The issue has been corrected.
- In the process history view, the process description was shown instead of the process name. The issue has been corrected.
- In Process Overview, the created on field showed a UTC time instead of local time. The issue has been corrected.
- When a process containing Prophet Enterprise or Assumptions Manager task template was imported, the Parameter and Category names were altered by adding _Copy on the end of the name. The issue has been corrected.
- When executing an IDR task resulting in failure of the IDR execution, the error was not reported in the process history. Instead, a success message was shown. The issue has been corrected.
- When a step containing no task was added into a process, a random task template was added to the step. The issue has been corrected.
- When editing a system variable and changing the name, the change could not be saved. The issue has been corrected.
- When a File Transfer task failed due to invalid destination path, the retry button was not enabled in process history. The issue has been corrected.
- When creating system variables, duplicate variable names were allowed. The issue has been corrected.
- A DCS execution failed when a Run Parameter contained a blank value. The issue has been corrected and now blank Run Parameter values are allowed.
- The Worklist showing Approval and External integration tasks, did not show the creation date for the task. The issue has been corrected.
- An error was thrown when executing an IDR task with certain valid parameters. The issue has been corrected.
- A Prophet Enterprise or Assumption Manager job submission task failed if the workflow service was restarted while the job execution was in progress. The issue has been corrected.
- When adding a task to a step in a process, the list showing the available tasks was sorted by creation date instead of task name. The issue has been corrected.
- When creating an output variable, the list of steps showing the available steps was sorted by creation date instead of by name. The issue has been corrected.
- When a process definition was renamed and then deployed, both the original process name and the new process name were shown under startable processes. The issue has been corrected, now only the new process name is shown.
- When importing a process containing a DCS task template with format parameters, the format parameters were added to all task templates. The issue has been corrected.
- The views showing lists of task templates, process definitions and startable processes are now sorted by name instead of creation date.
- When process definition was deployed, the process name shown in the start process view showed the process name with all spaces removed. The issue has been corrected.
- In various task template fields, the browser would sometimes display unrelated suggestions for the field values. The issue has been corrected.
|
