A customer wants to automate a workflow for completing customer service cases. The high-level workflow involves multiple rounds of recording investigation results, uploading related documents, sending communications, and approving. Activities may need to be done at any time or out of order.
Which recommendation best utilizes the strengths of Appian out-of-the-box features to address this use case?
A records-centric design is the best approach to address this use case in Appian. This design allows users to interact with data through a central record type, with related actions enabling them to perform tasks like uploading documents, sending communications, and approving cases at any time or out of order.
Records-Centric Design:
This approach centralizes all related data and actions around a specific record type.
Users can trigger related actions such as document uploads or approvals directly from the record, ensuring flexibility and a user-friendly interface.
Why Not Other Options?:
A and B. Reports and dashboards are useful for visualizing data but are not as flexible for handling the ad-hoc and out-of-order activities described.
C . A sequential workflow is too rigid for a process where tasks need to be done out of order.
References:
Appian Documentation on Records: Records in Appian
Appian Community Success Guide: Designing Record-Centric Applications
A records-centric approach leverages Appian's strengths, providing a flexible and intuitive solution for complex workflows.
Garry
1 months agoEdmond
2 months agoDawne
2 months agoDorathy
3 days agoTom
10 days agoFreeman
23 days agoWillard
1 months agoAliza
2 months agoIsaac
2 months agoAllene
2 months agoAn
2 months agoAudrie
2 months agoReyes
2 months agoBok
2 months agoAllene
3 months ago