Skip to main content
July 10, 2025
Solved

Is this the correct format ?

  • July 10, 2025
  • 4 replies
  • 0 views

So in the above pic i have an interface where i gave the user an option where he can select or reject a candidate. And when he clicks select a candidate, a mail will be sent to the candidate saying he has been selected for the job and when the user hits reject, a mail will be sent to the candidate saying sorry you have been rejected.

So i created this process model and kept 2 emails for the both different mails.Is this the correct format or am i missing something. Can someone Please guide me through this.

Best answer by shubhama926776

Your process model structure is correct, but can be optimized using Appian best practices.
Instead of separate paths, use a linear flow: Start -> Call Write Records Subprocess -> Call Send Email Subprocess -> End.
The Write Records subprocess should capture both SELECT and REJECT decisions for complete audit trail.
The Send Email subprocess should use conditional logic (based on decision) to send the appropriate email template - selection confirmation or rejection notice.
This subprocess approach ensures reusability across multiple processes, centralizes maintenance, and follows Appian's recommended design patterns. Pass the decision type and candidate details as parameters to both subprocesses. This simplified design eliminates the decision gateway while maintaining the same functionality with better maintainability.

4 replies

shubhama926776
July 10, 2025

Your process model structure is correct, but can be optimized using Appian best practices.
Instead of separate paths, use a linear flow: Start -> Call Write Records Subprocess -> Call Send Email Subprocess -> End.
The Write Records subprocess should capture both SELECT and REJECT decisions for complete audit trail.
The Send Email subprocess should use conditional logic (based on decision) to send the appropriate email template - selection confirmation or rejection notice.
This subprocess approach ensures reusability across multiple processes, centralizes maintenance, and follows Appian's recommended design patterns. Pass the decision type and candidate details as parameters to both subprocesses. This simplified design eliminates the decision gateway while maintaining the same functionality with better maintainability.

July 10, 2025

Yes will apply that , thankyou for the guidance.

stefanhelzle0001
July 10, 2025

For such a simple process, I think the general style is good. I suggest to label the flows leaving the XOR, and also think about a more expressive label for the nodes.

July 10, 2025

Yes will do, thankyou very much for the info.