Modernization of PSPA Error Handling

Today:

Online Edits to reduce transactional data entry errors – usually limited in scope to the current transaction.

Process Scheduler Message Log – cryptic messages, limited conditions/messages, doesn’t catch all exceptions, doesn’t provide enough details, incorrect message parameters, unactionable. Have to dig to find messages. Excludes process run outside of Process Scheduler – RemoteCall like Self-Service Estimates and common calculation automation customizations (also return code issues).

What if?

Critical messages were more in your face.

Used clearer (audience specific) language.

Provided actionable suggestions.

Provided automated options for implementing suggestions and automated reprocessing after data changes applied.

Track message occurrences and provide analytics dashboard/reports to identify commonly encountered errors allowing administrators to provide training, develop fixes, or take on mass data cleanup or configuration change projects.

Other Ideas:

Support RemoteCall message collection and viewing.

Disconnect process specific messages from EE level data issues.

Ability to configure custom error message conditions.

More transparency – display messages in calculation results or popup messages when process is run.

Collect Knowledge base of error message user experiences and resolutions.