But, I think that the commit doesn't totally close this issue. This is for "Record Level ACL", so for example you can make an Invoice read-only once it has been set to "Completed", or an Opportunity if it gets set to "Closed Won" or "Closed Lost".
Presumably there will need to be some further code to actually implement the ability to change the Editability of a record on-the-fly? The commit above is at Profile level so will affect all records within a particular module surely?
@satish.dvnk Why have you closed this? This is for a new feature called "Record Level" Access Control which is not yet part of vtiger but is frequently requested.
"We are frequently asked by our customers for the ability to "lock" records based on the value of picklists etc..."
And
"It is very valuable for complex sale process. Especially when potential goes through several salesmen with different roles, for example company
replace windows in houses. First salesman "sell" free measurement, second measures and sign contract, and third works with customers who did not buy on second step. If second step failed, potential must go to thrid and never return to second-step salesman.
One more case. Courier have access to Sales Orders consigned to deliver today, only with Approved status. Closed orders should never been edited. Courier shouldn't see old orders.
This Issue is called "Record Level ACL". The discussion on those emails evolved from the original title but is not to do with splitting Edit and Create (which I know is now done).