The Outcomes class is used to store the outcomes of the decisions rendered by the decision matrix. A determination package can result in multiple decisions of different types with multiple outcomes if it has more than one decision matrix associated with it.
The start and end date attributes on the Outcome entity are used to filter which active outcomes are available for selection when editing decision matrix data. Once an outcome is added to a decision matrix, it stays in place regardless of its end date.
As with the DeterminationConfig class, name translations can be added for an outcome record. The locale of a user who logs in is read and matched with the appropriate translation and the outcome name will be displayed in the language appropriate to the user.
The following table describes the business processes that make up the Outcomes class:
| Business Process | Description |
|---|---|
| listActiveOutcomes | This method returns the list of active only outcome records on the system. |
| readOutcome | This method reads an outcome record. The difference between the read and view methods is that this method only returns the outcome details, not the name translation details. |
| readOutcomeNameTranslation | This method is to read an outcome name translation record. |
| viewOutcome | This method reads an outcome record, including outcome details and name translation details. |
| listOutcomeDetails | This method is intended to be used by users responsible for managing outcomes to list all the outcome records on the system irregardless of status. |