Skip to main content

Hello,

 

Question regarding App Param: FREEZE_REQUEST_STATUS on FSM M6u13]

 

Our goal is to “lock” or “freeze” a request when it has reached a status of ‘complete’ , ‘CO’ so that no one can edit details of the request.

 

We have set our >code table] to include the correct code

I believe we have set the App param correctly

 

Currently I can open a “completed” request on the UI, and change values on the request table (like request.payment_id) and save changes

 

Is there an additional step I need to take to “Lock” the records?

@MKNDANIEL 

Do you have the code(s) in the code table configured?

Can you please share the REQ_STATUS as a screenshot?

Cheers!

Here are the Codes in the Table.

 

Best Regards,

Another option

  • What functions in the role you have?
  • What version are you working with?

Cheers!

Version 6u13 

 

  • BPO_BLANKET_PO_DEF_SCREEN    (disable)
  • CODES
  • CUSTIOTACTION     (disable)
  • EDITPERSONANY
  • EDITROLEANY
  • EXECUTEDBEDIT
  • EXECUTEDBQUERY
  • FSMIOTACTION     (disable)
  • IMPORTEXPORTANY
  • IMPORTEXPORTMAP
  • IMPORTEXPORTWIZARD
  • IOTDEVICE    (read only) (no delete)
  • IOTOBSERRULE       (disable)
  • IS_ADMIN_ROLE    (disable) (allow global search)
  • MAK_CONTACTLOOKUP
  • MAK_REQUEST_VITALS_LOOKUP
  • ODATA
  • OVERRIDEFREEZEREQUEST
  • PRODUCTSTRUCTURE
  • REFRESHFULL
  • REQUESTCREATEUPDATE
  • TASKLOOKUP
  • TASKSTATUSANY (disable)
  • UITHEMES

 

 

 

The OVERRIDEFREEZEREQUEST function is the key.  You have it enabled.  If you disable it or remove it from your role, you will no longer be able to update the Request.

Brian,

 

You nailed it!  

 

-Is there a list of “Functions” and their definitions that I can request? 

 

Glad I could help!  Unfortunately, I’m not aware of any documentation with a consolidated list of Role Functions.  Maybe someone else has put something together?

Reply


Terms & ConditionsCookie settings