Make inline-repeat line readonly after saving

Client
1

redacted redacted redacted

2

I would make the whole table readonly add a separate, technical field to enter a new comment. Then you can use an event button to add a new row to the groups of comments (with a bit of custom code).

3

redacted redacted redacted

4

Hi @alicia-secure-haze,

you can model a workaround for this but it has its limitations. You can do this as follows:

  1. Model two Fields with the type “Confirm” in your repeat. (ConfirmA and ConfirmB)
  2. Make ConfirmA a required field
  3. Model a rule so that ConfirmB is set to the same value as ConfirmA
  4. Add ConfirmA to your inline repeat
  5. Model dependencies so that all the other fields in the repeat are dependent on ConfirmA. This means that when ConfirmA is true, the row is read-only.
  6. Model a further dependency so that ConfirmA is hidden when ConfirmB is true. This means that as soon as you set the ConfirmA to true, it is hidden and cannot be changed by the end user.

As ConfirmA is a required field, it must be set to true before you can save the form. Setting ConfirmA to true make the row read-only. This also hides ConfirmA (due to the calculation and dependency to ConfirmB) so that the user cannot change any values in this row.

You could create a different, admin screen where ConfirmA is not hidden to allow admins to make changes.

The downside here is that the user needs to check the confirm for each row of the repeat.