[QueenBee]

Any ideas on a clean way to capture a rejection reason when a user hits our custom rejection button?
This is a cached copy. Click here to see the original post.

[trimblee]

We use a custom field. When a record is rejected the value in that field is included in an email sent to the submitter. We don’t make it required, though you could do so with an action in the workflow.

---

QueenBee replied on 11/10/2015, 06:27 PM: The issue I had was that the record they are rejected they can not edit. I created a custom workflow history record and after they reject it create a new history record, redirect them to this record, and there they can enter the reason. Not the cleanest user experience but it works…

[Sireesha]

I have a very similar requirement. Any thoughts will be helpful. The REJECT button will be in view mode. However, on clicking the REJECT Button, the Status of the Bill changes to Rejected.

Only during Rejection, the Rejected Reason has to be entered.

I want the workflow to open the record and prompt the user to enter the Rejected Reason.

I am not able to achieve this… Any pointers would be helpful.

[QueenBee]

Originally posted by Sireesha

View Post

I have a very similar requirement. Any thoughts will be helpful. The REJECT button will be in view mode. However, on clicking the REJECT Button, the Status of the Bill changes to Rejected.

Only during Rejection, the Rejected Reason has to be entered.

So here is an outline of what I did:

Created a new custom record which has columns linking back to the invoice, who peformed the action, when, what the action was, and a text field.

In my invoice rejection workflow when they press the reject button:

-Update the invoice status to rejected,

-Create a new record of the type above and store the result

-Send an email notifying that the invoice has been rejected

-Go to the newly created record in edit mode

The form for this new custom record limits the user to just editing the reason field. When they save a new note it sends an email.

The major downsides to this approach are:

-The action of rejecting has already occured when the user is presented with the reason entry form, thus the reason is not actually required.

-This causes two emails to be sent. One saying the invoice has been rejected, and then a second one when the user enters a note.

-The UI is not nearly as clean as the new NetSuite delete a record reason UI.

[hendricksmd]

I have a similar solution that i’ve used at multiple businesses and it seems fairly seamless but requires two workflows.

1. Your approval workflow

2. a rejection workflow on a custom record that sends an email and redirects a user back to the transaction after saving.

first, create a custom record called “Rejection” with a long text field for the reject reason input. Create a second list/record field referencing transactions. and set the record as parent option here.

In your approval workflow, in the rejection state on entry

– use the go to record action and select your custom rejection record and set the custom transaction list field to the ID of the rejected transaction. This will guide the user to a new rejection record where they input the reason for rejection and attach the rejection record to the invoice/PO/salesorder in a sublist.

– When the user saves this, the second workflow sends the reject reason to the employee that created the transaction using the Send Email action

– Use the go to record action in this second workflow to redirect the user back to the transaction (stored in the custom field).

Its a little hard to describe this in a forum post but it takes very little time to set up and works like a charm. It also allows transactions to be rejected multiple times and adds a rejection record to the transaction each time.

Matthew

[Author]

Posts