Locking down the Change Form once it has been saved

It would be beneficial that once a change form or a release form has been submitted, that the form is locked down and no additional information can be entered.  This will stop the possibility of someone adding more information into the change request once it has been approved for deployment.

 

The other option is to allow changes to be made up until it is approved so once it has been peer reviewed or approved for implementation (workflow dependant).  Once it has been approved, no fields on the form can be changed unless done by the change manager.

  • Guest
  • Jan 2 2018
  • Reviewed by Alemba Product Manager
vFire v9 / Security
  • Attach files
  • Admin
    Dave Ball commented
    April 18, 2018 08:24

    This has now been reviewed by the Product Management Team and will monitor the number of votes this suggestion gets with other customers.

    Attachments Open full size
  • Deleted User commented
    January 24, 2018 14:30

    Technically - this is possible today.  To do this, simply follow these steps:

    • In Designer - Create your Request for Change screen set to meet your business requirements and save it.
    • Create a New Request Screen Set (Request for Change Locked) and clone the Request for Change Request Details screen
    • On the Request for Change Locked screens - change the pertinent fields to read only.  Save.
    • On your Change Workflow - add a conditional branch task immediate after your approval.  In the conditional branch - set the action to change the screen set from the Request for Change to the Request for Change Locked screen.

    This will automatically lock your fields down (make them read only) once the approvals have been completed.

    Attachments Open full size

Related Feature Suggestions