Wanted to make reject reason as a mandatory field in mingle tasks

Hi,
We have workflow for Purchase Order, Requisition etc. The workflows are working fine and the users are able to approve and reject the tasks in mingle. I wanted to make reject reason parameter as a mandatory field in mingle tasks when user tries to reject the order. Can you help in doing this.
Please find the attached screenshot.
Thanks in advance.

Find more posts tagged with

ION Workflow

Accepted answers

Legacy Contributor

All input parameters in a Workflow that are selected to show in the Task are required. So the best way to accomplish a "reason for rejecting" is through Mike's suggestion of using a code list, using that code list in an input parameter, and making sure that parameter is shown in the Task

.

I will note that there is a popular enhancement request to be able to mark some parameters as optional. Feel free to use the ERS system if you need that feature.

All comments

Legacy Contributor

Hey there,

It looks like no screenshot was attached but it sounds like what you're looking for is a function called "Codes" in ION. In ION Desk, you can create a family of codes that you can re-use elsewhere like ION Connect (content-based routing, parallel flows, etc.) and ION Process - workflows, primarily.

From here, you can use a "Task Chain" step to generate and store the action into a workflow parameter (E.G. "StoredDecision") that can then be used in a workflow "Decision" activity. If the task was approved, notify the chain of the approval but if the task was rejected, you can add a "Set Parameter" activity that's tied to the ION Code family and then the user can select one of the reasons you've provided.

Legacy Contributor

Hi Mike,

When i tried using the "codes" function for requisition, it is throwing an error while activating the activation policy.

Can you me on which attibute has to be mapped for the parameter "rejectreason" in activation policy.

Please find the attached screenshot.

Legacy Contributor

Morning,

In your activation policy, can you go back to the Attributes tab and identify what data type "ReasonForRejection" is? It looks like you have a data type mismatch where ReasonForRejection is likely a string field but the workflow parameter is an Enumeration, thus causing the issue. You would need to harmonize these two data types.

Thanks

Legacy Contributor

Is this still a workable solution to make a field mandatory. I have an input parameter that is configured as a code list and displayed on a task. I clear the parameter before the task is presented so the code list is empty however the "Done" button closes the tasks without prompting to complete the input field.

Copyright © 2025 Infor. All rights reserved.