Confiform - Hidden Field in "View/Edit Stored Data" View

[Andre T_]

I am using Confluence Cloud.  I am trying to edit fields that are hidden on the main form.  Unfortunately these fields don't seem to be editable as they were in the on-prem version.  When I click edit, I am still presented with the fields from the original form.  How do I workaround this issue?

I am trying to edit these via the Form Drop-Down (rather than the edit button under the Table View)

[Alex Medved _ConfiForms_ · Accepted solution]

Hi

Hidden fields (with a type hidden) are hidden no matter where you use them - on prem or on cloud.

This works absolutely the same way. This is the point of hidden fields - to have them hidden

Alex

[Andre T_]

@Alex Medved _ConfiForms_ , sorry I didn't explain correctly.  The field is a drop-down field (hidden by confiform rules).   It does show up under edit, but not editable. (when I click edit under the form drop-down ("View-Edit Stored Data")) I still get the same behavior as when you click edit from the Table View.  (it shows the the entire form without the other fields that I see before clicking "edit")

[Alex Medved _ConfiForms_]

Does it have edit restrictions configured? 

Or is it just hidden by the rules? The same rules are per form and applied everywhere - does not matter what you use to edit a record

[Andre T_]

Yes, only editable by admins (as defined).  But the behavior on how the data renders is different from the on-prem version where you are able to edit the raw data in-line.

[Andre T_]

(the cloud version renders the form again when you click edit from the form drop-down, which is not the behavior I am expecting)  I like to be able to edit the raw data stored.  Any other workaround to achieve updates to the raw data?  This needs to be achieved by another user at a later date.  As a result I cannot use IFTTT to achieve changes to each record when needed.

[Alex Medved _ConfiForms_]

I dont understand to be honest. What is different? May be a screenshot or something? I am totally lost here

True that due to the limitation of the editor in Confluence cloud you cannot use custom layouts for the edit forms and the whole form will be rendered

[Andre T_]

This is where I am trying to edit the raw data:

[Alex Medved _ConfiForms_]

OK, and what is not working for you? 

(it is absolutely the same form as if you create your own view with ConfiForms Edit Controls)

[Andre T_]

I clicked "edit" for the last entry "Thinkcell", this is what I see (the form) versus seeing the raw data in-line for editing. 

[Andre T_]

Before when this "edit" button was clicked, I could edit any raw fields from this page.  This is no longer the case.  I am getting same behavior as clicking edit from Table View (which doesn't show any of the additional fields that are hidden) It is just showing me the original form which is visible to the end-user.

[Alex Medved _ConfiForms_]

Ok, what do you expect to see?

(what you see is how the ConfiForms work on cloud and on prem)

[Alex Medved _ConfiForms_]

You can edit ANY fields that the form has and which you have edit permissions for and which are NOT hidden by form rules

[Andre T_]

No, previously on the on-prem version and cloud version, when the edit was clicked, it would be in-line and I could edit any of the fields under that row. (hidden or not, it looks like something changed in the versioning recently where this is now no longer possible)   Question is how can I update any of these raw fields now moving forward if not via this method?

[Andre T_]

I do see the fields I like to edit under the first screenshot, but unable to do so when I click edit, because only the original form is rendered versus the in-line edit capability.

[Alex Medved _ConfiForms_]

Always is/was a dialog, never "inline"

So, what fields you CANNOT edit, I dont understand... what do you mean by "raw fields"? There is was never a difference in how the form behaves - no matter WHERE you edit

[Andre T_]

The fields you see on the first screenshot "Sec1Res, Sec2Res, etc." is not editable because when the edit button is clicked, the original form is rendered and those fields are not visible in the form.

[Alex Medved _ConfiForms_]

Yes, form definition rules are applied, permissions are verified and you see only the fields that are visible to you and which you are allowed to edit

Always been this way - on prem and in cloud

[Andre T_]

so in order to edit the data, should I export, make changes and re-upload to the form? (via csv export?)

My question is now how to edit the data if not possible from the UI.  When I export, all the data does show up which I need to update.

[Alex Medved _ConfiForms_]

So, you need to adjust or remove the rules from the form if you want to edit it differently than normal edits (edits with the rules that you specified)

[Andre T_]

Some fields are considered "administrative" fields and shouldn't be displayed to the user.  They need to be filled after the form is submitted.  There has to be a way to be able to carry this fields and edit after the form submission.  This was possible until a few days ago.  Not sure what update was made to confluence in the past few days where this capability is no longer available.

[Alex Medved _ConfiForms_]

What makes the fields as “administrative”? How those are configured?

[Andre T_]

I have 2 drop-down type fields and 1 date field.  All 3 are hidden by confiform rules and displayed after submission.  Assessor needs to go in and input their feedback in those 3 fields after they have reviewed the form submission by an end-user.

[Alex Medved _ConfiForms_]

Either make the fields editable only by certain user groups (not using the rules to hide, as these does not make things secure anyway - userInSecurityGroup) or if you want to use the hide rules then make these rules to trigger only for users that are not in the certain user group or only to run for new records (not saved, easiest way to check the id:[empty] in the condition)

[Andre T_]

I used the editable only configuration for each field and removed rules to hide from those fields.  That worked and helped me achieve what I needed as a workaround.  Thank you so much for your help