How to provide rejection reason when HR want to reject candidate Application

Hello ! you can store the values of the dropdown box as a rule input (ri!selection) and then in a sectionLayout you can spectify the reason and then save on clicking the button (in sectionLayout specify the condition- showWhen: ri!selection="Reject" this will show the section layout only when the value in dropdown box is reject. Then you can create the process model and map the process variables and use write to dse service, your data will be saved to the database as reject.

a!sectionLayout(
  contents:{
    a!dropdownField(
      placeholder:"Choose application ",
      choiceLabels: {"Reject","Select"},
      choiceValues: {"Reject","Select"},
      value:ri!selection,
      saveInto: ri!selection
    ),
   a!sectionLayout(
     contents:{
       a!paragraphField(
         label:"Reason",
         instructions: "Add reason for application rejection",
         required: true,
         value:ri!reason,
         saveInto: ri!reason
       ),
       a!buttonLayout(
         primaryButtons: {
           a!buttonWidget(
             label: "SAVE",
             value: "SAVE",
             saveInto: ri!buttonAction,
             submit: true,
             style: "PRIMARY"
           )
         },
         secondaryButtons: {
           a!buttonWidget(
             label: "CANCEL",
             value: "CANCEL",
             saveInto: ri!buttonAction,
             submit: true,
             style: "NORMAL"
           )
         }
       )
     },
     showWhen: ri!selection="Reject"
   ) 
  }
)

I've used 3 rule inputs : ri!selection(for dropdown selection),   ri!reason(reason for rejection), ri!button(save values for button).

Hello ! you can store the values of the dropdown box as a rule input (ri!selection) and then in a sectionLayout you can spectify the reason and then save on clicking the button (in sectionLayout specify the condition- showWhen: ri!selection="Reject" this will show the section layout only when the value in dropdown box is reject. Then you can create the process model and map the process variables and use write to dse service, your data will be saved to the database as reject.

a!sectionLayout(
  contents:{
    a!dropdownField(
      placeholder:"Choose application ",
      choiceLabels: {"Reject","Select"},
      choiceValues: {"Reject","Select"},
      value:ri!selection,
      saveInto: ri!selection
    ),
   a!sectionLayout(
     contents:{
       a!paragraphField(
         label:"Reason",
         instructions: "Add reason for application rejection",
         required: true,
         value:ri!reason,
         saveInto: ri!reason
       ),
       a!buttonLayout(
         primaryButtons: {
           a!buttonWidget(
             label: "SAVE",
             value: "SAVE",
             saveInto: ri!buttonAction,
             submit: true,
             style: "PRIMARY"
           )
         },
         secondaryButtons: {
           a!buttonWidget(
             label: "CANCEL",
             value: "CANCEL",
             saveInto: ri!buttonAction,
             submit: true,
             style: "NORMAL"
           )
         }
       )
     },
     showWhen: ri!selection="Reject"
   ) 
  }
)

I've used 3 rule inputs : ri!selection(for dropdown selection),   ri!reason(reason for rejection), ri!button(save values for button).

Hi vibhutig004

can you please explain how to create process model in related action for this above code

You need to create a process model with the interface you're using for selection, then map the rule inputs as process variables. After, the start node use a XOR with condition: pv!selection="Reject" go to Write to DSE, with the variable configuring it, the use the send email smart service configuring it with from: process initiatior, to: the interviewee name or (emailid), add the subject:, then in message body in expression mode write the message & pv!reason and then the end node. In similar way you can do the required for the selection as Select.