Settings and activity
41 results found
- 
12 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
15 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
10 votesAn error occurred while saving the comment 
- 
4 votes Jonathan McIntire
    
 shared this idea
           · Jonathan McIntire
    
 shared this idea
           ·
- 
8 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
8 votes Jonathan McIntire
    
 shared this idea
           · Jonathan McIntire
    
 shared this idea
           ·
- 
4 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
7 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
17 votes
- 
28 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
11 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 shared this idea
         · Jonathan McIntire
    
 shared this idea
         ·
- 
3 votes Jonathan McIntire
    
 shared this idea
         · Jonathan McIntire
    
 shared this idea
         ·
- 
36 votesAn error occurred while saving the comment  Jonathan McIntire
    
 commented Jonathan McIntire
    
 commentedIn scenarios where there are multiple levels of approvers and each approver should not be able to alter the values entered by previous users, this is essential when paired with the IsInGroup function to determine which fields should edited by which individuals. Author Only doesn't work for more than one level of approver.  Jonathan McIntire
    
 shared this idea
         · Jonathan McIntire
    
 shared this idea
         ·
- 
5 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
73 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
18 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
9 votes
- 
34 votes
- 
5 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
- 
2 votes Jonathan McIntire
    
 supported this idea
           · Jonathan McIntire
    
 supported this idea
           ·
 
        
"Read Only" fields that are controllable via calculations are probably more flexible. That way the platform isn't limited to "Lock First Value" or "Author Only" use cases: https://portal.goformz.com/forums/937692-forms-templates-public-forms/suggestions/45006409-read-only-property-for-fields