Hi.

You can go to Admin - Change Lifecycle and change all the types of changes you need to have this.

You may set the Transition to Awaiting Approval to have those fields mandatory:

You may need to play with the status.

Hope this helps.

If you need further clarification, please don’t hesitate to reply back.

Regards,

Thank you for your reply Elvis. I have those settings set, however there is nothing stopping an agent from requesting approval before those fields are filled out. If they request approval before filling out the planning form, the planning details don’t get carried over to the approval email and the approver doesn’t have the details necessary to make an informed approval (hope this makes sense). 

 

Ideally, it would be nice to have the system set up so that if they click on “Request for Approval”, it won’t let them request the approval until the Planning section is completely filled out first, then it will allow for them to request approval.

I figured it out! I had to create a Business Rule for Change Requests to only show the Request Approval Button when all the Planning fields are not empty.

Hi.

You actually went for my next suggestion, he he he.

I’m glad you figured it out and addressed it.

I’d now suggest to mark this Thread as Solved, so others with your same inquiry may find it.

Regards,

Hello @apassey, glad that there was a solution to make this work, but I am concerned that the Change Lifecycle method that @eeha0120 suggested wasn’t sufficient. I have tested this to see if we experience the same issue, might be worth taking to the product team as it did prevent me from progressing my change when I set the status to awaiting approval and clicked update while the planning fields were empty.

Locking transitions from being available based on failure to meet requirements is an important part of the process. Though business rules for forms is a great way to handle forms, handling the lifecycle of a change would be easier to maintain through the Change Lifecycle module. I’m curious what might be causing the failure of this piece of functionality for you. Take care!