Transaction Feedback
When you select the Save, Validate, or Submit actions, CGI Advantage performs a series of edit checks on your transaction. If it encounters any issues or if the Validate or Save action is successful, details are displayed in the System Feedback ribbon that will appear beneath the Page Title Bar. On the far left is a box for each message severity proceeded by an ‘ALL’ box that gives the total count:
Successful (green check): Successful messages are issued, but then disappear as a means to relay your action succeeded.
Informational (blue box with an i): Informational messages, as the name suggests, are for informational purposes only and do not affect the determination of whether a transaction will be accepted to the next phase. All informational messages that occur during transaction processing are accumulated so the user can see all of the informational messages for that transaction version at one time.
Warning (red triangle with exclamation point): When warning messages are encountered, they are compared with the warning message from a previous validate or submit action. If there are any new warnings since the last time, the user is given the chance to review these warnings before the transaction is accepted to the next phase. The next time the transaction is submitted, the transaction is accepted to the next phase if there are no new warnings. All warning messages that occur during transaction processing are accumulated so the user can see all of the warning messages for that transaction version at one time.
Override and Rejection errors combined (red hexagon with x). When error messages are encountered, the transaction is rejected and any updates or changes made outside of the transaction are not committed. All error messages that occur during transaction processing are accumulated so the user can see all of the error messages for that transaction version at one time. In addition, the phase of the transaction remains at the Draft phase until the user fixes the transaction and validates or submits the transaction again. Override messages are called out with the word override in an oval.
Severe (red diamond with a lightning bolt): When severe messages are encountered during the processing of a transaction, the processing is terminated immediately at that point and control is returned back to the user. All updates or changes made to the transaction and made outside of the transaction are not committed. Only the messages that occurred before the severe message and the severe message itself are displayed to the user for review.
Not Displayed: When a message Severity level is set to Not Displayed on the Messages (MESG) page, system feedback is bypassed and not shown on the transaction. This message does not affect the determination of whether a transaction will be accepted to the next phase or not. It is recommended to set this option with caution especially when the original error severity is Error or Severe.
Initially all errors are presented in the horizontal bar that allows for one line of the short message to be displayed. The successive boxes filter the horizontal bar by severity. On the far right are a pair of icons (Previous and Next) for navigating within a group of short error messages. The last icon is the Show All Messages along with Details icon that opens a panel from the right that allows you to review all the details of a message and search across messages.
Overriding an Error Message
Those error messaged defined as an Override Error have an associated override level defined to them that requires a user to apply an override of that level or higher in order to get the transaction to proceed. System configuration for each transaction code can have three settings for applying overrides on transactions with workflow established:
Allowed only after reaching – The override action can be applied only after the transaction reaches Pending.
Required before reaching – The override action must be applied before the transaction reaches Pending.
Allowed before or after reaching – The override action can be applied before or after the transaction reaches Pending.
