Fields: Read Only attribute exept API User is write allowed

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • macistda
    Member
    • Jul 2022
    • 76

    Fields: Read Only attribute exept API User is write allowed

    Suggestion: There should be an option for Fields (general) if selected "read only" (filled by formula is possible) except API User is writing.

    Workaround: Design two fields, one with read only (add in Layout) and one field (not in Layout) with same content - and fill in the read only field with formula.

    Negative with the workaround solution: Two fields with same content are saved unnecessary. (Double Data).

    For using area, e.g.: Workflow Espo - N8N - Jira and backwards (bidirectional) and some data is allowed be chanced at Jira only and not at Espo.

    Remarks:
    Jira is meant Jira from Atlassian, a Software for project management for software development. But usage Espo with N8N (a software for BPM workflow management) could be with much different other software, too.
  • yuri
    Member
    • Mar 2014
    • 8440

    #2
    Use Field Level Security in roles.

    We could come up with many such parameters: allowed for A, read-only for B and so no. That would be a mess.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    Working...